Rust Engineer - Fintech/Crypto - $300k - On Site

Venchr; San Francisco (CA); On-site; USD 270,000 - 330,000; Full time

Job summary

Venchr, a San Francisco-based fintech startup, is seeking a Rust Engineer to own core backend services powering a real-time trading platform. You will design and ship high-performance components that process live market data, enforce risk logic, and maintain consistent state across asynchronous processes.

You will work on low-latency REST and WebSocket APIs, shape architecture and tooling, and collaborate with a small team to deliver reliable systems with millisecond responsiveness.

Qualifications

• Production Rust experience and familiarity with asynchronous programming.
• Experience in financial markets or markets data infrastructure.
• Startup experience preferred; willingness to own features end-to-end.
• Ability to reason about latency, correctness, and reliability.

Responsibilities

• Design and ship services that process live market data and manage risk.
• Deliver low-latency REST and WebSocket APIs.
• Own architecture and tooling decisions in a fast-moving startup.
• Coordinate state across asynchronous processes and ensure correctness.
• Collaborate to shape architecture and development practices.

Skills

Rust

Async programming

Concurrency

System performance

Job description

Rust Engineer - Fintech/Crypto - $300k - On Site

We are a small startup building the high-performance backend systems that power a real-time trading platform, and we are looking for a Rust Engineer who wants meaningful ownership from the start. You will design and ship services that process live market data, manage risk and settlement logic, maintain consistent state across asynchronous processes, and deliver low-latency REST and WebSocket APIs. The systems you build sit directly in the path of live trading activity, so the consequences of your decisions are immediate, measurable, and visible to the rest of the team. Because we are still early, you will also help shape architecture, tooling, and working practices rather than simply implement specifications written by someone else.

You will work across the full lifecycle of features that matter to capital efficiency and reliability. That includes building and refining risk and liquidation engines that respond correctly under volatile conditions, implementing state machines that coordinate trading, settlement, and risk operations, and creating services that keep distributed components consistent even when processes fail or networks behave unexpectedly. You will handle live data streams, coordinate actions across multiple venues, and construct high-performance APIs that the trading interface depends on for millisecond-level responsiveness. Debugging will often span multiple layers of the stack, and you will be expected to form clear opinions about trade-offs between latency, correctness, operational simplicity, and development speed.

We are looking for someone who already has production experience writing Rust and who is comfortable with asynchronous programming, concurrency, and the performance characteristics of systems languages. Experience in some form of financial markets is required. This could come from trading systems, market data infrastructure, risk engines, execution platforms, exchange connectivity, or other environments where correctness and speed have direct financial consequences. Startup experience is strongly preferred. We move quickly, prefer working software over lengthy planning cycles, and expect engineers to take ownership of problems from initial design through production monitoring and iteration. There is little process for its own sake, and the people closest to the work usually make the decisions that affect it.

The environment is flat and engineering-driven. Ideas are judged by how well they solve real problems rather than by where they originate, and individual contribution has an outsized effect on what the product becomes. You will collaborate closely with a small group of people who care about market structure, reliability, and the details of how systems behave under load. Feedback is direct, code review is thorough, and the expectation is that you will both give and receive clear technical opinions. Because the company is still early, priorities can shift as we learn more about users and markets, and we value people who can adapt without losing momentum or quality.