About this role
Docker has been one of the most loved brands in developer tooling, trusted by more than 20 million monthly users and over 20 billion container image pulls. From solo founders to the world's largest companies, developers rely on Docker to build, share, and run their applications across our suite of products including Docker Desktop, Docker Hub, and Docker Scout.
We are a globally distributed, remote-first team building the tools that define how software gets built and delivered. As AI agents redefine software development, Docker is at the center of that shift, providing the sandboxed environments, verified images, and secure infrastructure that make autonomous workflows trustworthy by default.
The Secure Build team builds and operates the infrastructure behind Docker's container builds. The team owns and runs Docker Build Cloud and Docker's Hub build systems, which run millions of builds a year for hundreds of organisations, and is building the next generation of that: secure, sandboxed CI that isolates each build step and produces hardened images with strong, verifiable provenance, including for customers in regulated and air-gapped environments. A current focus is a hardened build runner that executes each workflow step inside its own micro-VM sandbox.
We're looking for an Engineering Manager to lead this team. It's a small, very senior group that recently came together, with strong technical leadership spread across it. You'll own the team's delivery, growth, and operational excellence, keep its high-scale production systems healthy, and be a real part of setting the team's technical direction alongside the engineers who lead on different parts of the system.
THE KIND OF PERSON WE'RE LOOKING FOR
The successful candidate leads first. They're an experienced engineering manager at their best turning a senior team into a high-performing, value-delivering part of the wider Docker org: getting the process and team mechanics right, partnering well with Product, and navigating the personalities on and around the team. What sets them apart is that they stay deep in the technical work rather than steering from a distance. They're active in technical design and in the PRs, they help shape the technical direction, and they're happy to pick up code where it moves things forward. We're not after a 50-50 player-coach, and we're not after someone who's left the engineering behind either; the balance tilts to leading, but they're hands-on enough to be properly in the detail with the team. The team has strong technical leadership across it, and direction is set together rather than by any one person, so this isn't about being the best engineer in the room or the deepest supply-chain-security expert. It's about being engaged and credible enough to be a real part of how the team sets its direction, not standing apart from it. They care about security broadly: how modern attacks actually work, the OWASP Top 10, and where a build pipeline is exposed. The