Solana Protocol Engineer

The role

We route across a large set of exchanges and launchpads. Each one is a program with its own account layout, its own instruction set and its own failure modes, and any of them can change without an announcement. This role owns the integration layer: adding venues that matter, removing venues whose liquidity has gone, and catching breaking changes before a customer campaign does.

What you would own

• Integrate new venues from program source and on-chain account inspection rather than from documentation alone
• Maintain the program identifier registry that the measurement engine and the router both read
• Build regression checks that fail loudly when a venue changes its account layout
• Remove venues that no longer hold usable liquidity, rather than leaving them in a list to inflate a number

What we need

• Working knowledge of the Solana account model, PDAs, CPI and Anchor instruction encoding
• Ability to decode an unfamiliar program from its IDL, or from bytes when no IDL exists
• Rust or TypeScript to a production standard

Nice to have

• Prior work on a DEX aggregator, indexer or MEV-adjacent system
• Experience with Token-2022 extensions and how they change transfer behaviour

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 Solana Protocol Engineer 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.