Jobs / United States / Doordash INC
Senior Software Engineer, Build Systems & CI
Doordash INC · 🇺🇸 Bay Area, CA; Seattle, WA; Los Angeles, CA; New York, NY
Sponsorship verdict
Sponsorship possible
One solid signal, not two — worth applying, and worth asking about sponsorship early.
- Employer is on a government sponsor recordThe US Department of Labor certified 396 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. USCIS also records 147 H-1B approvals in FY2023. Source: LCA disclosure data (US Department of Labor (OFLC)).
- The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
- No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- What Doordash INC paid sponsored hires in similar roles88 certified filings for “Software Engineer” (Software Developers) in CA: $154k–$188k, median $188k. Most were filed at wage level I (41%) — 1 lottery entry, ≈15% projected selection odds for cap-subject employers. Source: US Department of Labor LCA disclosure data (Oct 2025 – Jun 2026).
- Confirmed live todayWhen a source last listed this job as open.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence; it is not legal advice and never a guarantee — the employer and the immigration authority decide. Sign in to factor in where you can already work.
Or apply yourself on the official page →
Sponsor Radar — Doordash INC
The US Department of Labor certified 396 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. USCIS also records 147 H-1B approvals in FY2023. Source: LCA disclosure data (US Department of Labor (OFLC)).
Past sponsorship or register membership never guarantees sponsorship for this vacancy or for you. Full Sponsor Radar for Doordash INC →
About the role
About the Team The Code Scalability team owns build systems and continuous integration across DoorDash. When a shared dependency changes or more teams contribute to a monorepo, the cost of building software can grow for everyone. We tackle that challenge with Bazel, Buildkite, and infrastructure that keeps everyday development efficient. Our work gives teams a dependable path from a code change to a completed build, with fewer delays and less infrastructure troubleshooting. About the Role As a Senior Software Engineer on Code Scalability, you will solve the engineering problems behind building software at DoorDash’s scale. A change deep in a monorepo can trigger work across many projects; your job is to make that work efficient, predictable, and easy to investigate when something goes wrong. Projects span Bazel configuration and tooling, Buildkite orchestration, build execution and caching, and the services that support them. You will identify where improvements matter most, make the technical decisions, and work with teams across DoorDash to put those changes into practice. The impact of this role extends to every team that depends on our platform. Shorter queues give engineers more time to iterate, dependable pipelines prevent interruptions, and useful diagnostics help them get back to their work. You will measure progress through those outcomes, alongside the cost and maintainability of the infrastructure you own. You’re excited about this opportunity because you will… • Evolve build and CI workflows for large monorepos, keeping feedback fast and changes manageable as dependencies, code volume, and the number of contributing teams grow. • Develop Bazel rules, toolchains, and integrations that keep builds reproducible and make shared build infrastructure easier for teams to adopt across large monorepos. • Improve Buildkite pipeline throughput and reliability by reducing queue times, addressing build bottlenecks, and making better use of CI compute capacity. • Reduce redundant build work through dependency analysis, incremental builds, caching, and parallel execution, balancing developer feedback speed with infrastructure cost. • Build developer tools that explain build failures and help engineers reproduce CI behavior locally, making troubleshooting faster and reducing support overhead. • Rethink what a build and CI platform can do with AI: move beyond reporting failures toward intelligent diagnosis, PR triage, automated recovery, and guidance that helps developers move forward. • Instrument and operate build and CI infrastructure. Use metrics and developer feedback to track latency, reliability, and resource usage, then address recurring infrastructure problems. • Lead platform improvements from design through rollout, partner with engineering teams on migrations, and mentor teammates through technical decisions and code reviews. We’re excited about you because… • You have 5+ years of software engineering experience, including building developer infrastructure, build systems, or CI platforms. • You write maintainable production software in a language such as Go, Java, Kotlin, or Python, and bring strong debugging and software design skills. • You have experience with build or CI systems at scale and can reason about dependencies, incremental builds, caching, and distributed execution. Experience with Bazel, Buildkite, or large monorepos is especially relevant; comparable tools and environments count too. • You have led technical projects across teams, made practical design tradeoffs, and carried changes through rollout and operational ownership. • You approach internal platforms as products: you listen to developers, make workflows easier to adopt, and judge success by the problems you solve for them. • You c