Staff Software Engineer, Billing

Docker builds developer tooling and infrastructure used to build, share, and run applications. The Staff Software Engineer, Billing will own and evolve the infrastructure supporting Billing Platform services, including AWS infrastructure, Terraform, CI/CD, observability, deployment safety, and incident response. The role will also partner with software engineers, drive systemic improvements, and mentor team members.

Responsibilities:

• Own and evolve the infrastructure supporting Billing Platform services: compute, storage, networking, CI/CD, and observability
• Design and maintain IaC (Terraform) for billing system infrastructure on AWS; set module patterns and standards for the team
• Build and own observability systems — metrics, logging, alerting — with a focus on billing accuracy and payment reliability
• Define deployment patterns and runbooks that work well in an AI-agent-assisted development workflow: clear rollback procedures, safe promotion gates, automated validation
• Partner with software engineers on service design — bringing infrastructure constraints and operational requirements into the conversation before code is written
• Identify systemic risks and drive improvements that span team or organizational boundaries
• Lead incident response for billing system issues. This role may require participation in an on-call rotation to provide support outside of standard business hours, including evenings, weekends, and holidays, as needed
• Mentor engineers across the team; your technical judgment should raise the floor for everyone

Requirements:

• 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
• 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