Manager of Engineering (Secure Build)

Join Docker as the Manager of Engineering for the Secure Build team. In this role, you will lead a small, senior group responsible for building and operating the infrastructure behind Docker's container builds. You will own the team's delivery, growth, and operational excellence, and be a key part of setting the team's technical direction. This position requires a strong background in software engineering, experience managing high-performing engineering teams, and a passion for security.

• Lead a team of senior engineers in operating Docker Build Cloud and Hub's build systems, and building Docker's next generation of secure build infrastructure.
• Own the delivery of the team's roadmap, turning ambiguous commitments into a concrete plan that the team can execute predictably.
• Be actively involved in technical design discussions and code reviews, and hands-on in the code where it helps, while also setting the team's technical direction.
• They lead through judgement, unblocking, and direction-setting rather than process for its own sake, because that's what a senior, autonomy-heavy team responds to
• What sets them apart is that they stay deep in the technical work rather than steering from a distance
• They care about security broadly: how modern attacks actually work, the OWASP Top 10, and where a build pipeline is exposed
• 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
• 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
• 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
• The successful candidate leads first
• 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
• 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
• They're comfortable owning the operational reality of production systems and on-call, and they're energised rather than thrown by ambiguity
• Above all they care about growing the engineers around them and shipping something customers actually trust
• A strong interest in security: how recent attacks have actually worked, the OWASP Top 10, and the build threat model. Familiarity with software supply chain security (SLSA, in-toto, provenance, signing such as cosign, SBOMs, vulnerability scanning) is valued, but we care more about security instinct and appetite than a checklist of tools
• Bachelor’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience
• Understanding of CI/CD and build-system internals, container images and image hardening, and OCI registry mechanics
• Technically deep and still hands-on: recent enough engineering chops to be active in design and code review, be a real part of setting technical direction with the team, and write code where it helps. Not the best engineer in the room or the deepest domain expert, but not a manager who's left the technical detail behind either
• Strong written and verbal communication, and a habit of staying close to customers
• A leader first: strong on team process and mechanics, on partnering with Product, and on reading and navigating the personalities on and around a team to make it more than the sum of its parts
• Hands-on familiarity with Go is a plus; it's the team's primary language
• Comfortable inheriting a team they didn't build: earning the trust of experienced engineers, and owning the full range of performance conversations, including the difficult ones, fairly and directly
• 8+ years of professional, hands-on, full-time software engineering experience in backend, infrastructure, or platform engineering
• 5+ years managing high-performing engineering teams, including engineers at or above their own level of technical seniority, with a track record of growing and retaining senior individual contributors
• Experience operating production infrastructure: on-call, incident response, SLOs, and the realities of keeping high-traffic services healthy
• Comfortable leading a distributed, remote-first team across European and US time zones, with a high degree of autonomy