# Senior Software Engineer, Infrastructure — Docker

- Location: Seattle, WA (remote)
- Posted pay: $161k–$261k/yr
- Posted: Apr 3, 2026
- Status: open (checked Nov 20, 2026)
- Apply (employer's site): https://jobs.ashbyhq.com/docker/ae03031e-7080-472c-bcc6-207833a8d2f9
- Employer record: https://visajobs.io/company/docker.md

## Sponsorship history
- Tier: Good history
- Occupation (SOC): Software Developers (15-1252)
- Employer's certified LCAs for this occupation in WA, FY2024–FY2026: 5
- …in the whole US: 5
- With this exact title: 0
- Median DOL prevailing wage, level I / II: $111k / $137k

## Description
About Docker
Docker is the platform at the center of how intelligent software gets built. For more than a decade, Docker has helped millions of developers and thousands of organizations build, ship, and run software consistently across any environment. Today, Docker extends that same trust to the AI era. Docker Hardened Images form the foundation agentic code is built on, local and cloud Docker Sandboxes isolate where agents run, and Docker AI Governance sets enterprise-wide policy. Together, they give builders and organizations the confidence to adopt any model, tool, or agent without compromising security, governance, or control.
_______________________________________________________________________
The Role
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
6+ years of hands-on software engineering in backend, infrastructure, or platform engineering, though we weight real depth and impact more heavily than exact tenure.
Strong software engineering in Go or a similar language: design, testing, debugging, review, and long-term maintainability.
A track record of building, shipping, and operating cloud services or infrastructure in production.
Deep expertise in at least one of Kubernetes, networking, cloud platforms, reliability engineering, or developer platforms — plus solid Linux and production-ops fundamentals.
Experience shaping technical direction and working effectively across teams.
Clear written and verbal communication in a remote environment (RFCs, design docs, incident writeups).
Bachelor’s in CS/Engineering or equivalent practical experience.
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); driving migrations or adoption programs across teams.
You don’t need every item here. We value strong systems judgment, real depth in at least one area, and curiosity across the rest.
_______________________________________________________________________
What to Expect
First 30 days
Build context, meet partner teams, ship your first change, and shadow on-call.
First 90 days
Own a meaningful platform component or project with a clear plan and metrics, and take an improvement from design to production.
O

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
