Staff Software Engineer, Infrastructure

About Docker

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.

_______________________________________________________________________

Docker is shipping a wave of new products this year, with R&D initiatives likely to lead to more, and we're investing heavily in the platform underneath all of it. That platform supports hundreds of engineers across many development teams and carries high-scale production traffic and data transfer every day. It has grown faster than its foundations, and this year is about closing that gap.

Today, much of that work still leans on a handful of experts unblocking the same provisioning and operational workflows by hand. The top priority for this role is moving that work from expert-driven support to paved roads : self-service systems with clear ownership, safe defaults, strong guardrails, and adoption we can measure. The goal is a platform teams trust enough to stop thinking about it, one that just works, so they can focus on their own products instead of ours.

The concrete version sits on this year's roadmap: spinning up a new global region or application environment should take hours, not days. Right now it takes days. Getting there means building the foundations underneath it. We need a real multi-region, cross-account network architecture and a testing and continuous-deployment flow teams can trust, then a self-service layer on top.

We're the container company building our own internal platform, so the bar for "the easy path is also the safe path" is high. You'd be joining a team of four, growing to seven this year (this is one of those hires), and we're looking for a Staff engineer to set technical direction and lead it through real production adoption.

Responsibilities

This is a Staff-level role, so success is measured by leverage rather than just your own commits. On a team this size you'll stay hands-on in the codebase while also setting direction, aligning teams on pragmatic standards, and carrying platform investments through to adoption. Concretely, you will:

Take ambiguous infrastructure problems and turn them into proposals the org can rally around, then drive them through RFCs and architecture reviews across teams.

Design self-service capabilities and platform APIs (primarily in Go ) for onboarding, provisioning, deployment, observability defaults, and day-2 operations, with contracts and docs teams actually use.

Set delivery standards using Terraform , GitOps with Argo CD , progressive rollout, and good testing, including building the continuous-deployment flow we're missing today.

Evolve the multi-tenant EKS foundations toward better reliability, security, scale, and cost: Envoy Gateway ingress, traffic routing, and the multi-region, cross-account connectivity we need.

Improve SLOs, alerting, and incident follow-up on Grafana Cloud so production gets safer and less dependent on heroics.

We judge this work by outcomes the consuming teams feel: how fast they can provision and ship, how much they can do without us, and how reliably it all runs.

AI-assisted operations

We're actively investing in AI-assisted and agentic workflows to cut operational toil. We care that they stay safe, auditable, and human-reviewed. You'll help shape where these earn their place and where they don't. Early targets include:

Alert enrichment and incident context-gathering : assembling the relevant signals, history, and runbook so the on-call engineer starts with context instead of a blank page.

Runbook-assisted diagnosis and remediation recommendations , with a human in the loop on anything that changes production.

Onboarding and readiness assistants that answer the questions our experts answer today.

If you've built operational automation and have a healthy skepticism about where automation belongs, this is a place to put both to work.

On-call

Operational ownership is part of the job. You'll join the rotation after onboarding and shadowing. As a Staff engineer, you'll also improve the health of on-call itself, with better alerts, stronger runbooks, less toil, and blameless postmortems aimed at prevention.

Qualifications