Manager, Engineering, Secure Build

Responsibilities

• Lead a team of senior engineers operating Docker Build Cloud and Hub's build systems and building Docker's next generation of secure build infrastructure.
• Own delivery: turn an ambiguous, high-stakes roadmap, including time-bound commitments to regulated and federal customers, into a concrete plan the team can execute predictably.
• Get the team's process and mechanics right, and partner closely with Product to turn strategy into a roadmap the team believes in.
• Stay deep in the technical work: active in design discussions and code review, hands-on in the code where it helps, rather than steering from a distance.
• Be a real part of setting the team's technical direction, working with the engineers who lead on different parts of the system, while giving the whole team room to own technical decisions.
• This role may require participation in an on-call rotation to provide support outside of standard business hours, including evenings, weekends, and holidays, as needed.
• Own the growth, development, and performance of each engineer on the team, and hire to strengthen it.
• Work across the wider org - Product, sales, commercial and legal, the Hub/registry team, and security - to align the team and shield it from churn.
• Hold a high bar for engineering excellence and raise the team's security hygiene.

Qualifications

• 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.
• 8+ years of professional, hands-on, full-time software engineering experience in backend, infrastructure, or platform engineering.
• Bachelor’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience.
• 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.
• 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.
• Techically 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.
• 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.
• Understanding of CI/CD and build-system internals, container images and image hardening, and OCI registry mechanics.
• 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.
• Strong written and verbal communication, and a habit of staying close to customers.
• Hands-on familiarity with Go is a plus; it's the team's primary language.