Jobs / United States / Doordash INC
Software Engineer, Storage - Distributed Caching
Doordash INC · 🇺🇸 San Francisco, CA; Seattle, WA; 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 Storage organization builds and operates the online stateful systems and abstractions that DoorDash Engineering depends on: reliable, efficient, secure, and easy to use. Within Storage, the Distributed Caching team owns every caching offering at DoorDash end to end, including ElastiCache (Redis/Valkey), Boulder (our KVRocks-based key-value store for high-QPS feature serving), Entity Cache (read Bill Shen’s engineering blog post, “ High-Performance Proxy Cache for DoorDash Services ”), and the Distributed Lock Service, plus the smart clients (asgard-redis, valkey-go) that sit in front of them. These systems back critical product surfaces across DoorDash, Wolt, and Deliveroo: the team runs roughly 400 ElastiCache clusters serving hundreds of millions of GET requests per second in aggregate, and Boulder, our offline-to-online feature store, serves billions of feature lookups per second at peak. About the Role The team owns provisioning of clusters and the smart clients that sit in front of them, baking in sensible defaults so that other engineering teams get a turnkey caching solution instead of having to run their own. You'll help drive Boulder's evolution to scale further, improve cost efficiency, enhance performance, and support real-time updates; re-platform the Distributed Lock Service onto a strongly consistent backend; and build the self-serve tooling and recommendation engine that let customers describe a workload (QPS, TTL, payload size, latency profile) and get the right backend without talking to a human. You'll go deep on cache invalidation, replication, sharding, compaction, and failover, while shipping the guardrails, automation, and observability that keep this scale operable by a small team. You must be located in San Francisco, Seattle, or the New York Metro Area for this hybrid position. You will report to the Engineering Manager on the Distributed Caching team within the Storage organization. You’re excited about this opportunity because you will… • Own high-leverage caching and locking services with direct, measurable customer impact: cost, latency, and reliability at multi million QPS scale. • Build and scale Boulder, our KVRocks backed key-value store, including compaction, sharding, and domain isolation. • Re-platform the Distributed Lock Service onto a strongly consistent backend with sharding • Contribute to the standardized smart caching client that bakes in failover, retry, and observability defaults so customers don't have to think about them. • Diagnose and resolve production issues that span cache invalidation storms, replication lag, hot shards, and noisy-neighbor contention, then turn each one into a durable guardrail rather than a one-off fix. • Collaborate closely with the teams that build on top of caching, including Taulu, ML Platform, and product engineering across DoorDash, Wolt, and Deliveroo. We’re excited about you because… • You have 6+ years of full-time experience designing, building, and operating distributed, stateful systems in production, at least 2 of which involved caching or key-value storage at meaningful scale. • You are proficient in Go, or Java/Kotlin with deep expertise in concurrency, distributed systems, and production-grade backend services. • You have hands-on experience with distributed caching technologies (Redis/Valkey, Memcached, or similar) and understand their failure modes: replication lag, failover, hot keys, and cache invalidation. • You understand distributed systems fundamentals: consistency models, sharding and partitioning, replication, and consensus, and can reason about their trade-offs from first principles. • You have built or operated systems that require careful capacity planning and cost discipline at scale, and you de