DoorDash Interview Questions — Page 23

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

DoorDash system design round focused entirely on a cache debugging scenario. Pretty intense for a single question but it covered a lot of ground, from initial triage all the way through post-incident process.

You get paged for elevated latency and a spike in cache misses. Walk through your full debugging plan: what you ask the on-call partner, which metrics you check, how you form and test hypotheses, what mitigations you propose, and what post-incident steps you take.

“This one sprawled in a way I wasn't fully ready for.”

View Post

DoorDash·Software Engineer·Onsite - Coding / Algorithms

May 2026

DoorDash coding round where the whole point was using AI tools to fill in missing node implementations in a workflow engine codebase. Less about raw algorithmic chops and more about how fast you can read unfamiliar code, prompt well, and validate the output.

You're given a partial codebase for a workflow engine that reads rules from a file and runs nodes. The node implementations are missing. Using AI coding tools, implement the missing pieces so all existing tests pass, then write additional tests yourself.
What do you normally do before opening a pull request when the code was largely written by an AI tool?

“The velocity angle is what threw me a bit.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

DoorDash system design round for a software engineer role, and the problem was a full payout engine for gig workers. Way more surface area than I expected for a single session.

Design a payout calculator for gig workers like delivery drivers. Given completed orders with timestamps, distances, and tips, plus policy tables covering base pay, distance and time multipliers, surge pricing, batching rules, cancellations, and minimum guarantees, how would you compute per-order pay, per-shift summaries, and weekly statements?
How would you handle partial cancellations and stacked deliveries in the payout model, and what does that do to your schema?
How do you handle negative adjustments and chargebacks without corrupting a driver's already-issued pay statement?
Walk through how rounding and currency precision should be handled across per-order, per-shift, and weekly aggregations to avoid accumulated drift.
How do you handle events that arrive late and cross timezone or shift boundaries, especially for idempotent reprocessing?
What tests would you write to cover both typical and extreme scenarios for this payout system?

“I started with the schema because it felt like the safest entry point, orders table, policy tables, adjustments.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at DoorDash that was basically a product sense exercise disguised as a customer complaint session. You pick one of three companies, trash-talk their worst user experience, then pivot to metrics and an MVP. Felt more open-ended than I expected.

Describe the worst possible customer experience with Ticketmaster, Turo, or a major hotel chain. From there, define a north-star metric and propose an MVP to address it.

“I went with Turo because I figured fewer candidates would pick it and I'd stand out.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

DoorDash PM interview with a product sense question about improving a music app. Pretty standard stuff but it pushed me to think about user segments more carefully than I expected.

How would you improve your favorite music application?

“I picked Spotify because I use it every day, which I thought would help.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

Did a product sense round for a PM role at DoorDash. One question, focused on post-booking airline experience. Pretty open-ended and I wasn't totally sure where they wanted me to land.

How would you improve the worst post-booking experience at an airline?

“I spent too long trying to pick the 'right' pain point instead of just committing to one and going deep.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at DoorDash where they basically handed me a distributed cache problem and said go. It was one of the more exhausting design sessions I've had, lots of follow-ups and they kept pushing on trade-offs every time I thought I was done.

How would you scale a local LRU cache into a fully distributed caching system? Walk through sharding, consistent hashing with virtual nodes, rebalancing during node joins and leaves, and how you'd handle hot keys.
What replication strategy would you use for this distributed cache, and how would you handle failure detection and request routing?
Describe the read and write paths for your distributed cache design.
How would you handle cache consistency? Talk through TTL-based expiry, write-through vs write-back strategies, and cache invalidation.
How does your design hold up under network partitions, and what fault tolerance guarantees can you make?
How would you monitor this system and plan capacity for it?

“This was the core of the whole session.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

DoorDash on-call simulation for a payment service memory spike. Pretty intense for a system design round, they put you in a real incident scenario and expected you to walk through the whole thing from triage to postmortem.

You're the on-call engineer and the Payment Card Integration Service is showing abnormally high memory utilization during peak hours. Walk through how you'd handle the entire incident from start to finish, covering severity assessment, what you'd look at first, likely root causes, mitigation, communication, and long-term fixes.

“This is basically a full incident commander sim packed into one question.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at DoorDash, one question about diagnosing a drop in iOS app installs. Short and focused, but the kind of question that opens up fast if you're not careful about structure.

iOS app installs for DoorDash are down 35%. How do you investigate and respond?

“My first instinct was to jump straight to fixes, which was the wrong move.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at DoorDash focused entirely on payment reliability for the dasher payout flow. Pretty deep dive, lots of follow-ups, felt more like a distributed systems exam than a typical interview.

Your service processes real payouts to dashers. Walk through how you'd handle a payment that fails mid-flight due to a timeout, partial failure, or a downstream provider error without losing money or double-paying anyone.

“This question sprawled fast.”

View Post