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.
Our Infrastructure Engineering team builds and operates the cloud-native platform that powers Docker’s suite of products. We design resilient services, automate where it helps most, and measure what matters so hundreds of engineers can ship safely to millions of users every day.
A core focus is self-service. We build paved-road platform capabilities that let internal teams provision, deploy, observe, and operate services with minimal friction and strong guardrails. We treat the platform as a product with clear contracts, well-defined defaults, and great documentation. Success is measured by adoption and fewer support requests.
How We Work
-
Write it down, ship it, iterate: RFCs and design docs, code review, and small safe releases.
-
Sustainable reliability: we prioritize root-cause fixes, good alerts, and automation over heroics.
-
Cross-functional by default: we partner closely with product and security teams.
-
AI-accelerated execution: we build agentic workflows to reduce toil and improve incident response, with guardrails, auditability, and human review.
What You’ll Work On
- Reducing toil through automation, including AI-assisted and agentic operational workflows.
- Building self-service onboarding and deployment workflows that reduce tickets and speed delivery.
- Scaling Kubernetes foundations and evolving our traffic and ingress stack.
Responsibilities
1) Self-Service Platform Services
- Build and operate internal platform services and APIs in Go, including provisioning, quotas and policies, cost insights, and platform workflows.
- Deliver golden paths for self-serve onboarding and day-2 operations, including access, deployment setup, observability defaults, and governance guardrails.
- Partner with teams to drive adoption through clear docs, examples, and measurable outcomes.
2) Infrastructure as Code and Reliability
- Codify infrastructure with Terraform and GitOps practices, and contribute to platform tooling in Go.
- Define and improve SLOs, alerting, and operational readiness. Participate in incident response and preventive follow-ups.
- Help standardize safe delivery patterns, including testing gates, canaries, and rollback triggers, so deployments are routine and low-risk.
3) Kubernetes and Networking Foundations
- Operate and scale multi-tenant EKS clusters and traffic and ingress systems to deliver secure, reliable routing.
- Evaluate and adopt improvements with a bias toward incremental rollout and measurable impact.
4) AI and Agentic Workflows for Reliability
- Build and iterate on agentic workflows that reduce operational toil, including triage support, context gathering, safe runbook execution, and remediation suggestions.
- Integrate automation into delivery and operations in a way that is safe, observable, and auditable.
5) On-Call and Incident Response
Operational ownership is part of this role.
- 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.
- You’ll join an on-call rotation after onboarding and shadowing, and participate in incident response during your shifts.
- We aim for sustainable on-call through good alerting, automation, and blameless postmortems focused on prevention.
What to Expect
First 30 Days
- Ship your first change to a Terraform module or internal service and learn how we operate.
- Shadow on-call and build context on our platform and reliability priorities.
First 90 Days
- Own a component and deliver an improvement from design to production with measurable impact.
- Join the on-call rotation and contribute effectively during your shifts.
First Year
- Lead or co-lead a meaningful platform initiative, with scope that scales by level, and help reduce toil through automation.
- Become a trusted contributor in one or more areas such as platform services, Kubernetes and networking foundations, or reliability automation.