Principal Software Engineer, Containers

Responsibilities

• Set the technical direction for Chainguard Containers: the architecture of the build pipeline, the registry, and the adoption tooling over the next one to three years, written down and defended in the open.
• Form the roadmap with engineering and product leaders, then execute it. Turn ambiguous business goals into sequenced, staffed technical plans, and own the delivery of the largest multi-team projects from concept through production and adoption.
• Make and own the trade-offs that shape the product: build versus buy, when to re-platform and when not to, what to cut to hit a date. Write the decision down and bring dissenting engineers along.
• Lead through other engineers.
• Set the design bar, review the designs and code that matter most, and grow the Staff and Senior engineers around you into the next generation of technical leaders.
• Work with AI coding agents as part of how you build, review, and operate, and set the standard for how the whole team uses them safely as volume grows.
• Follow a problem wherever it goes: another team's service, a customer escalation, a support ticket, or go-to-market data, and work across team and company boundaries to get ahead of planning cycles.
• Represent Chainguard in the container and open source ecosystem: upstream work, standards conversations, talks, and the customer conversations where credibility is the product.
• Keep the systems you own healthy: observability, on-call, and the structural fixes that stop whole classes of incidents.

Languages