Docker - Staff Software Engineer, Billing

• 8+ years in platform, infrastructure, or SRE roles supporting production SaaS systems at scale • Deep AWS expertise: ECS or EKS, RDS (Postgres preferred), networking, IAM, cost management — you've operated these systems under real load and real incidents • Expert-level Terraform; you've designed reusable module patterns and set standards others follow • Experience building and owning observability stacks (Datadog, Grafana, or similar) at an organizational level — not just using them • Strong familiarity with CI/CD systems — Jenkins, GitHub Actions, or equivalent — including pipeline design and developer experience ownership • Kubernetes at an operational and architectural level • A track record of identifying systemic risks and driving improvements that span team or organizational boundaries • Security-first mindset: threat modeling, blast radius analysis, least-privilege by default, audit trails as a design requirement • Strong written English; at Staff level, written communication is how you scale your influence across teams • Bachelor’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience • What sets you apart • What sets you apart • You don't wait for problems to be handed to you — you find them, frame them, and drive the solution. You've operated at a scope where your decisions affected multiple teams or systems, and you know how to build consensus and move work forward without direct authority. You've thought seriously about what infrastructure needs to look like when AI agents are generating and shipping code — safe deployment patterns, strong observability, clean rollback — and you want to help define that standard here. Experience with billing, payments, or financial systems infrastructure is a meaningful plus. • What to Expect • What to Expect • First 30 Days • First 30 Days • You will ship code in your first week. We run an agent-first development workflow — infrastructure changes start with a plan, specifications are written before generation, and every change is reviewed before it merges — and onboarding is no exception. You will get hands-on with the infrastructure supporting Billing Platform services early, shadow on-call, and build a clear picture of the system before you start making bigger changes. By the end of 30 days you will have shipped real work and know where the most important problems are. • First 90 Days • First 90 Days • You will have taken ownership of one or more infrastructure components and delivered an improvement from design to production with measurable impact. You will be an active participant in deployment and reliability discussions, bringing infrastructure constraints and operational requirements into the conversation early — before code is written. You will be a full participant in the on-call rotation and have begun shaping the team's technical direction. • One Year Outlook • One Year • You will be the team's trusted authority on billing infrastructure. You will have driven meaningful improvements to observability, deployment safety, or platform reliability — and your work will be directly visible in the resilience and correctness of systems that handle real financial transactions for millions of Docker users. You will have helped define what AI-agent-assisted infrastructure operations look like done right, and that standard will be visible beyond this team. • Docker considers sponsorship on a case-by-case basis based on business needs.