Senior Rust Engineer, Routing

The role

A campaign arrives as a target volume and a mint address. The router turns that into a sequence of swaps distributed across whichever venues actually hold liquidity for the token, re-weighted continuously as pool depth moves during the run. It is written in Rust, it runs against a live RPC fleet, and it is the difference between a campaign that books its target and one that burns fees on transactions that never confirm.

What you would own

• Own venue weighting: how depth, measured failure rate and fee tier combine into a routing decision
• Reduce the share of submitted transactions that fail, which is currently the largest source of wasted budget
• Build the replay harness that lets us test a routing change against recorded chain state before it ships
• Decide when a leg should be retried, resized, or abandoned

What we need

• Four or more years of production Rust, including async under sustained connection load
• Direct experience with Solana transaction construction: compute budget, priority fees, blockhash lifetime, versioned transactions
• Comfort reading a program you did not write and working out what its account layout implies
• Willingness to be paged when confirmation rates drop at an inconvenient hour

Nice to have

• Experience with Jito bundles or another private submission path
• Familiarity with at least one Solana AMM implementation at the account level

These are genuinely optional. Nobody has been turned down for missing all of them.

Terms

Hiring process

1. A written reply from someone who read your application, usually within a week.
2. A conversation about what you have built and what you would want to own here.
3. A technical session on a real problem from our backlog, not a puzzle. Around two hours, paid if it runs longer.
4. A call with the person you would work alongside, and an offer with the salary already stated above.

How to apply

Email support@solanavolumebotpro.com with Senior Rust Engineer, Routing in the subject line. Include your CV and a few sentences on what you would change first. A link to code, writing or a system you ran counts for more than a covering letter.

If you are unsure whether your background fits, apply and say so in the note. We would rather read an application that turns out to be a mismatch than miss one that was not.