Auto-apply is a Pro feature

Let Findyet apply to this job for you:

  • Your CV is tailored to this posting.
  • The application form's questions are answered from your profile.
  • You review everything and approve before anything is sent.
  • Findyet submits the application and adds it to your tracker.

Available on Greenhouse postings today, up to 3 applications a day on Pro.

The first 100 verified accounts get Pro free for 90 days.

See plans

Docker

Staff Software Engineer (Infrastructure)

Posted Updated
Discussion
  • 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
  • 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
  • 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. 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
  • First 30 days:
  • Build context, meet partner teams, ship your first change, shadow on-call
  • First 90 days:
  • Own a strategic platform problem with a clear plan and metrics; lead an improvement from design to production
  • One Year Outlook:
  • 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

Benefits

  • 100% company paid medical premiums for employees and dependents
  • Flexible Time Off Policy
  • Employer Paid Holidays
  • Generous Parental Leave (after 6 months of employment)
  • Home Office Set Up Budget
  • Monthly Technology Stipend
  • Training Allowances
  • Life and Disability Insurance
  • Retirement Plans
  • Virtual and In-Person Social Events
  • Docker Swag
  • Quarterly Hackathons
  • Deep expertise in at least one of: Kubernetes, networking, cloud platforms, reliability engineering, or developer platforms, plus solid Linux, networking, and production-ops fundamentals
  • 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
  • 8+ years of professional, hands-on, full-time software engineering experience in backend, infrastructure, or platform engineering
  • Strong software engineering in Go or a similar language: design, testing, debugging, review, long-term maintainability
  • Bachelor’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience
  • You don’t need every item here. We value deep expertise in one area, strong systems judgment, and curiosity across the rest
  • Experience setting technical direction and leading work that needs cross-team alignment
  • A track record designing, shipping, and operating cloud services or infrastructure platforms in production. We hire for skill and impact, not years
  • Clear written and verbal communication in a remote environment (RFCs, design docs, incident writeups)

Skills

What Staff Software Engineering jobs ask for — and how much of it you have →
Apply

See also

Software Engineering jobs by country — openings, pay and top skills →

Tailor your CV for this role?

We couldn't check your fit for this role — add a CV to your profile to see it next time.