What you'll do

• Write and maintain substantial production code in the most complex, high-risk, and business-critical areas of the platform.
• Take end-to-end ownership for system behavior in production, especially during failures, stress, or adversarial conditions.
• Operate confidently in ambiguous problem spaces: define constraints, evaluate risks, and choose execution paths when clarity is limited.
• Identify and mitigate systemic technical, operational, and product risks through careful design, strong invariants, and operational discipline.
• Reduce accidental complexity by eliminating unsafe patterns and brittle abstractions.
• Set technical direction via reference implementations, durable abstractions, and sustained ownership of core systems.
• Serve as a technical coach through high-signal code reviews, thoughtful design discussions, and strong example-setting.
• Inform product and technical decisions by deeply understanding system behavior, user incentives, and long-term trade-offs.
• Participate actively in incident response and drive durable improvements through thorough root-cause analysis and follow-through.
• Raise the bar for correctness, reliability, and operability by making safe, reliable designs and behaviors the default for others.

What were looking for
We seek exceptional individual contributors who consistently deliver strong results across core engineering competencies and provide outsized leverage through a few exceptional strengths. Specifically, you should have:

• More than 5 years Rust, Go or Solidity experience.
• A proven track record of owning and evolving complex, production-critical systems.
• Exceptional engineering judgment in ambiguous, high-risk, or adversarial environments.
• Comfort reasoning about failure modes, edge cases, and second- and third-order effects.
• Strong operational ownership, including designing for observability, safe failure modes, and recoverability.
• A demonstrated ability to simplify complex systems while preserving correctness and safety.
• Influence earned through code quality, design clarity, and technical credibility.
• Clear, precise communication—particularly when articulating risks, trade-offs, and system behavior.

Nice to have

• Deep domain expertise in trading systems, exchange mechanics, or financial infrastructure.
• Expertise in one or more high-leverage areas, such as:
  • Reliability and operational excellence
  • Adversarial or incentive-aware system design
  • Architectural simplification and technical leverage
  • Deterministic, performance-sensitive, or event-driven systems