Staff Software Engineer Infrastructure
Docker
Description
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.
Tags
dockerdevdesigngrafanainfoseceducationtechnicalcustomer supporttestingcloudexecopssys admingolangmedicalengineerlinuxbackendfull timedigital nomad
Apply for this Position
About Docker
Company scraped from remoteok
Job Stats
Hiring Across Borders?
Interview Prep Guide
Preparation Strategy
To prepare for this role, focus on reviewing your technical skills in Go, Terraform, and EKS. Practice designing self-service capabilities and platform APIs, and review system design principles. Additionally, prepare to discuss your experience with continuous-deployment flows and testing. It's also essential to practice answering behavioral questions and preparing to discuss your technical leadership and problem-solving skills.
Likely Interview Rounds
- 1. Technical~60 min
What to prep: Review Go programming language, Terraform, and EKS fundamentals. Practice designing self-service capabilities and platform APIs. Be prepared to discuss your experience with continuous-deployment flows and testing.
- How would you design a self-service platform for onboarding and provisioning?
- What are some best practices for implementing GitOps with Argo CD?
- How do you ensure reliability and security in a multi-tenant EKS environment?
- 2. System design~90 min
What to prep: Study system design principles, focusing on scalability, reliability, and security. Review case studies of large-scale infrastructure designs. Practice whiteboarding system design concepts.
- Design a multi-region, cross-account network architecture for a container company.
- How would you implement a testing and continuous-deployment flow for a self-service platform?
- What are some strategies for ensuring scalability and cost-effectiveness in a large-scale infrastructure?
- 3. Behavioral~60 min
What to prep: Review your past experiences and prepare to discuss specific examples of your technical leadership and problem-solving skills. Practice answering behavioral questions using the STAR method.
- Can you describe a time when you had to drive a technical proposal through RFCs and architecture reviews?
- How do you handle ambiguous infrastructure problems and turn them into actionable proposals?
- Tell me about a project where you had to set technical direction and lead a team to adoption.
Most Likely Questions
- What are your experiences with Go and Terraform?
- How do you stay up-to-date with the latest developments in containerization and cloud infrastructure?
- Can you describe your experience with EKS and multi-tenant environments?
- How do you approach testing and continuous-deployment in a large-scale infrastructure?
- What are some strategies for ensuring security and reliability in a self-service platform?
Common Pitfalls
- Lack of experience with Go and Terraform
- Insufficient understanding of system design principles and scalability
- Inability to communicate technical concepts effectively
- Lack of experience with cloud infrastructure and containerization
Free Prep Resources
- • LeetCode
- • System Design Primer (GitHub: donnemartin)
- • Terraform documentation
- • Go programming language documentation
- • EKS documentation