We use cookies to improve your experience and measure how our site is used. Learn more.
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.
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:
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.
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:
If you've built operational automation and have a healthy skepticism about where automation belongs, this is a place to put both to work.
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.
Nice to have: EKS and ingress/CNI/service-mesh experience; observability with OpenTelemetry/Prometheus/Grafana; CI/CD and progressive delivery (GitHub Actions, Argo CD, canaries); experience leading migrations or adoption programs across teams.
You don't need every item here. We value deep expertise in one area, strong systems judgment, and curiosity across the rest.
Lead a major cross-team initiative (for example, self-service provisioning of new regions and environments, or the multi-region networking and CD foundations behind it) and establish durable patterns that change how Docker engineers build and operate services.
Canada: CA$238,250 – CA$382,250 + equity
United States: $170,350 – $275,550 + equity
______________________________________________________________________
______________________________________________________________________
Docker is proud to be an equal opportunity employer. We are committed to building a team that reflects a broad range of backgrounds, experiences, and perspectives. We believe diverse teams build better products, make better decisions, and better serve our global community.
USD 170,350 - 275,550
Annually
Health Insurance
Dental Insurance
Vision Insurance
Mental Health Benefits
Disability Insurance
Life Insurance
401(k) / Retirement Plan
Equity / RSUs
Financial Planning
Unlimited PTO
Paid Holidays
Company Shutdown Days
Flexible Schedule
Home Office Stipend
Coworking Allowance
Company Offsites / Retreats
Parental Leave
Learning & Development Budget
Employee Resource Groups
Team Events & Social Budget
Docker hires by country or region rather than treating remote work as location unrestricted, so check each posting for its eligible location.
Distributed teams stay connected through hackathons, Lunch Roulette, offsites, and employee resource groups. Docker also schedules quarterly company-wide Whaleness Days and a year-end break as shared time away from work.
Docker lists fully paid medical, dental, and vision coverage for US employees, with localized benefits elsewhere. Other offerings include mental-health and retirement support, parental leave, equity, flexible PTO, home-office and coworking support, a monthly technology stipend, and annual learning support.
Docker uses location-based compensation. Its job postings may show different country-specific salary or OTE ranges for the same role, and Docker says final compensation considers experience, skills, qualifications, and location. Check the posting for the range that applies to your location and whether the offer includes equity.