CodeVotum

The role

We are not filling a headcount slot. We want the person to own the trading systems side of a young market data and trading infrastructure business, with the door open to becoming a partner.
 

We are building a Rust market data and trading infrastructure platform. Several venues are already live in the capture pipeline, across CEXs, DEXs and prediction markets, and expanding that coverage is the bulk of the near-term work. Full-depth order books and trades, normalised so one integration serves many venues, on columnar storage with an analytical query layer over it.
 

What you would own

Venue connectivity end to end, from feed through normalisation, gap detection and replay

The shared abstraction every venue fits behind, which will either hold or turn into a special case per venue

Correctness of the capture path, including the boring parts that decide whether a backtest is trustworthy

Execution components as they come online. Read-side today, but it is on the path.

Operability, since nobody hands off support to another team here

Technical direction in your area. You argue the trade-off, you make the call, you live with it.
 

Who we are looking for

We're looking for someone with a deep interest in trading and market dynamics. Proficiency in Rust, especially async and Tokio, is essential. You should be able to critically evaluate code changes and anticipate their long-term impact. Break down your own work into actionable tasks and prioritize them effectively. Experience in exchanges, market making, or AWS/Linux performance work is a plus.
 

Seniority and time

We are not labelling this junior or senior. What matters is whether you can carry a component without much direction.

Part-time works only if you are already experienced in the domain, since limited hours are only useful from someone who needs little context and little supervision. If you would be learning the domain here, that is fine, but it has to be full-time.

How we hire

Two short steps before we talk properly.

1. A logical reasoning test, around 40 minutes. Abstract pattern matching, no coding.
2. A code review. We give you access to a small repository with a pull request in it and you review it the way you would review a colleague's work. Budget about an hour.

Then we go through your review together on a call.
 

What we can offer

You would build the thing rather than maintain someone else's version of it. Venue connectivity, capture guarantees, ordering and state under failure, and execution once the read side is solid. Not many engineers get to work on a system like this, and the experience is hard to acquire any other way.

The data comes with it. Full depth across every venue we capture, yours to research against. Buying comparable history costs real money, and most engineers who want to test an idea properly never get near it.
For the right person, a partnership may follow, with a share of the revenue once there is any.