Staff Software Engineer, Chainguard

• 5+ years building and operating software that paying customers use, including leading at least one multi-engineer project end to end, preferably at a startup or a company in hyper-growth
• High agency and urgency. You find a way, you do not wait to be unblocked, and you unblock others
• Judgment on trade-offs at the system level. You have made calls that moved a roadmap, and you can show what you gave up and why
• A systems thinker who designs for the whole path: build pipeline, registry, distribution, and the customer's runtime, and who sees second-order effects before they land
• AI-native in how you build and lead. You use agentic coding tools daily and you have changed how a team works because of them
• Comfortable with ambiguity. You can turn a half-defined product goal into a concrete technical plan, and pivot when priorities shift
• Architectural depth in Go: you can design a Go service from scratch, not only contribute to one, plus strong API design, databases and caching, and cloud infrastructure on GCP or AWS
• Deep knowledge of containers, container registries, the OCI image format (Open Container Initiative, the standard for container images and registries), and Kubernetes
• A track record of mentoring engineers and raising technical practices across a team
• Low ego. You do what you say and say what you do, and you communicate early when the news is bad
• Excellent written English and experience working on a distributed, remote-first team
• If your experience is close but doesn't fulfill all requirements, please apply. We're building the best team in technology and are focused on hiring "Chainguardians" with unique backgrounds, perspectives, and experiences

Desirable

• Chainguard Containers is our core product, and this team builds it. As a Staff Software Engineer in Container Product Engineering you will design and ship the features, services, and build systems behind Chainguard Containers, and you will lead the small sub-teams of two to four engineers that own them
• Chainguard is growing explosively. Every line of code is now written with AI in the loop, which means the foundation it runs on has to be secure by default. You will build that foundation: the hardened container images, the registry that serves them, and the tooling that lets engineers and AI agents adopt them
• This is a product role with technical ownership. You will set direction for major new capabilities, make the architectural calls that affect the team and the teams next to it, and multiply the output of the engineers around you. You will stay hands-on: most of your week is still building
• What the team owns
• Product features for Chainguard Containers. Letting customers push their own images to our registry, Custom Assembly (customers compose images from our hardened packages), Helm charts, notifications, and compliance views such as STIG dashboards (STIG is the US government's hardening standard)
• The image build pipeline. The systems that turn packages from Wolfi, our Linux distribution, into signed and attested container images at scale, including moving image builds onto our own runner infrastructure
• Registry performance and distribution. Work such as lazy loading, so a container starts before its whole image has downloaded, and image signing with Sigstore
• Adoption tooling for engineers and AI agents. Migration tools that convert existing Dockerfiles to Chainguard Containers, and MCP servers (Model Context Protocol, the standard that lets AI agents call tools) so agents can discover and pull our images directly
• Architect and drive the delivery of major new features and services for Chainguard Containers, often spanning several engineers or teams, from concept through production and the first weeks of customer use
• Make and own the high-leverage trade-offs: which capability to build first, what to defer, when to re-platform and when not to. Write the decision down and bring dissenting engineers along
• Work with AI coding agents as part of how you build, review, and operate, and set the standard for how the team uses them safely as volume grows
• Follow a problem wherever it goes: into another team's service, a customer call, a support ticket, or go-to-market data, and work across team boundaries to get ahead of planning cycles
• Mentor and level up other engineers through design review and pair work, and set the standard for how the team designs, builds, and ships
• Partner with Product and engineering leadership on roadmap, bringing a technical point of view to what we build, not only how
• Keep the systems you own healthy: observability, on-call, and the fixes that stop the same page from coming back
• Write clearly and often. Design notes, decision records, and status updates are how a remote team moves fast together