# Senior Software Engineer, Billing — Docker

- Location: Seattle, WA (remote)
- Posted pay: $161k–$261k/yr
- Posted: Apr 21, 2026
- Status: open (checked Nov 20, 2026)
- Apply (employer's site): https://jobs.ashbyhq.com/docker/f0f54bac-a23d-4643-98aa-e457b2f360fb
- 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
We're building AI-native development practices into how this team works at a foundational level. That means infrastructure design needs to account for a new kind of collaborator: AI agents that generate, deploy, and operate software. The Senior Software Engineer, Billing on this team will keep systems running, help define what safe, observable, AI-assisted infrastructure operations look like in practice, and model that standard for the rest of the team.
_______________________________________________________________________
What you'll work on
The Billing Platform Engineering team owns the systems that make Docker's commercial model real. You'll work on problems like:
How do we design infrastructure that makes AI-generated deployments safe to ship and easy to roll back?
How do we instrument billing systems so that failures — billing miscalculations, entitlement gaps, payment errors — are detected immediately and unambiguously?
How do we build infrastructure that scales with usage-based billing workloads without manual intervention?
How do we make the developer experience on this team faster and more reliable — local environments, CI/CD pipelines, deployment tooling?_______________________________________________________________________
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; contribute to module patterns and standards for the team
Build and own observability systems — metrics, logging, alerting — with a focus on billing accuracy and payment reliability
Implement 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 in the team's systems and drive improvements, including work that reaches into adjacent teams or services
Participate in 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 on the team; your technical judgment should help raise the bar for how the team builds and operates
_______________________________________________________________________
Qualifications
6+ years in platform, infrastructure, or SRE roles supporting production SaaS systems at scale
Strong AWS expertise: ECS or EKS, RDS (Postgres preferred), networking, IAM, cost management — you've operated these systems under real load and real incidents
Strong Terraform skills; you've built reusable module patterns and can improve the ones a team relies on
Experience building and owning observability stacks (Datadog, Grafana, or similar) for production services — not just using them
Strong familiarity with CI/CD systems — Jenkins, GitHub Actions, or equivalent — including pipeline design and developer experience
Kubernetes at an operational and architectural level
A track record of identifying systemic risks and driving improvements within your team and adjacent systems
Security-first mindset: threat modeling, blast radius analysis, least-privilege by default, audit trails as a design requirement
Strong written English; clear written communication is how you scale your work across the team
Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience
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.
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 the systems your team owns, and you know how to build alignment 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
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
You will have taken ownership of one or more infrastructure components and delivered an improvement from 

> 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
