Summary

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

1. Own reliability end-to-end for the auction sandbox and related services: deployment, upgrades, incident response, and operational hygiene.
2. Audit and consolidate today’s scattered components into a coherent system with a clear roadmap, interfaces, and single DRI ownership.
3. Build and automate containerized environments for latency-sensitive searcher workloads (e.g., atomic arbitrage), including reproducible builds and safe defaults.
4. Create first-class operator + user docs: runbooks, examples, troubleshooting guides, and “known failure modes” playbooks that searchers can trust.
5. Partner across teams (TEE, infra, product) to expand sandbox capability while tightening security, isolation, and developer experience.

What we look for

1. You have operated Linux production systems with real ownership: on-call/incident responsibility, upgrades, and long-lived maintenance.
2. Strong Linux + networking fundamentals; you debug below the dashboard (processes, sockets, filesystems, resource isolation).
3. Hands-on containers experience (Docker/Podman, image/build workflows, debugging inside containers). Ochestration familiarity is a plus.
4. A track record as a DRI for a complex service used by others (internal or external), including “boring” reliability work.
5. You write excellent docs, not as an afterthought, but as part of how systems become scalable and trustworthy.
6. User empathy: you ask about constraints, workflows, and success metrics before shipping changes that break someone’s setup.

Who you are

1. You enjoy being the person who makes systems dependable. Specifically with runbooks, automation, alerts, and a clear mental model of failure cases.
2. You prefer ownership over handoffs and can drive a roadmap while collaborating effectively with domain experts.
3. You can learn quickly in unfamiliar domains (MEV/searcher workflows/TEE concepts) without needing prior crypto experience.

Nice-to-haves

1. Exposure to confidential computing / TEEs (e.g., Intel TDX/SGX) or adjacent isolation tech (microVMs, sandboxing, attestation).
2. Experience with reproducible build pipelines or hardened execution environments (e.g., Nix, Bazel, hermetic builds, OCI hardening).
3. History of maintaining open-source infra/tooling or running a serious homelab/bare-metal setup.

Skills

• Communications Skills
• Team Collaboration