Senior 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, and we’re investing heavily in the platform underneath all of it. That platform supports hundreds of engineers and carries high-scale production traffic every day — and it has grown faster than its foundations. This year is about closing that gap.

Right now, too much of that work leans on a handful of experts unblocking the same provisioning and operational workflows by hand. The top priority for this role is turning that into paved roads: self-service systems with clear ownership, safe defaults, strong guardrails, and adoption we can measure — a platform teams trust enough to stop thinking about, so they can focus on their products instead of ours.

The concrete goal is on this year’s roadmap: spinning up a new region or application environment should take hours, not days. Getting there means building real multi-region, cross-account networking and a 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 also being the safe path is high.

You’d join a team of four, growing to seven this year — this is one of those hires. We’re looking for a senior engineer who can own significant parts of this platform end to end, drive projects to real production adoption, and raise how the whole team builds.

Responsibilities

This is a senior, deeply hands-on role. You’ll own significant components, drive projects from design through production adoption, and shape the platform’s technical direction while helping teammates grow. Concretely, you will:

Turn ambiguous infrastructure problems into clear designs and working systems — contributing to RFCs and architecture reviews, and driving your projects to done.

Build 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.

Apply and help shape delivery standards with Terraform, GitOps on Argo CD, progressive rollout, and strong testing — including the continuous-deployment flow we’re missing today.

Strengthen the multi-tenant EKS foundations for reliability, security, scale, and cost: Envoy Gateway ingress, traffic routing, and multi-region, cross-account connectivity.

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

We measure 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 investing in AI-assisted and agentic workflows to cut operational toil, and we care that they stay safe, auditable, and human-reviewed. You’ll help shape where they earn their place and where they don’t. Early targets:

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, and help improve on-call itself: better alerts, stronger runbooks, less toil, and blameless postmortems aimed at prevention.

Qualifications