About us

At Flashbots, we're building the foundations of the future Internet and financial system. As an R&D organization, we focus on MEV through our dual engines of open research and breakthrough product development – like mev-geth, Flashbots Protect, MEV-Boost, MEV-Share, Flashblocks, and BuilderNet. Our vibe is accelerationist, exceptional, kind, and independent. We are explorers, innovators, builders, and thinkers. We thrive on action, curiosity, and impact - driving the future in an iterative way while keeping an eye towards the long term version we want to see in the world.

You’ll take end-to-end technical ownership of Flashbots’ auction sandbox. You’ll combine production operations, systems engineering, and strong documentation instincts to make the sandbox reliable, repeatable, and easy to use while working closely with searchers, TEE experts, and infrastructure partners.

What you’ll do

• Own reliability end-to-end

  for the auction sandbox and related services: deployment, upgrades, incident response, and operational hygiene.

• Audit and consolidate

  today’s scattered components into a coherent system with a clear roadmap, interfaces, and single DRI ownership.

• Build and automate

  containerized environments for latency-sensitive searcher workloads (e.g., atomic arbitrage), including reproducible builds and safe defaults.

• Create first-class operator + user docs

  : runbooks, examples, troubleshooting guides, and “known failure modes” playbooks that searchers can trust.

• Partner across teams

  (TEE, infra, product) to expand sandbox capability while tightening security, isolation, and developer experience.

What we look for

• You have operated Linux production systems with real ownership: on-call/incident responsibility, upgrades, and long-lived maintenance.
• Strong Linux + networking fundamentals; you debug below the dashboard (processes, sockets, filesystems, resource isolation).
• Hands-on containers experience (Docker/Podman, image/build workflows, debugging inside containers). Orchestration familiarity is a plus.
• A track record as a DRI for a complex service used by others (internal or external), including “boring” reliability work.
• You write excellent docs, not as an afterthought, but as part of how systems become scalable and trustworthy.