DoorDash Interview Questions
Real questions reported from DoorDash Senior SWE loops - Code Craft aggregation and payout rounds, tree-diff and grid/BFS technical screens, a hierarchical key-value store design question, and 8 of the most commonly reported System Design prompts, each as its own writeup.
18 real interview questions reported from DoorDash E5 / Senior SWE interviews (Coding, System Design rounds): 7 medium, 11 hard. Each question shows its interview round and how often it was reported, and coding questions come with runnable tests.
DoorDash Coding round questions (10)
- Nearest DashMart - Medium, free preview
A domain reskin of "Walls and Gates" - reported for the DoorDash Senior SWE technical screen by multiple independent candidates. The trap is answering N separate queries with N separate BFS runs instead of one multi-source pass. - Dasher Pay Payout Calculator - Medium, free preview
DoorDash's flagship 'Code Craft' question, widely reported by candidates including at the Senior level. The trap is treating a peak overlap as all-or-nothing instead of prorating the overlapping minutes. - Consistent Hashing Ring - Hard
The redesign step of the DoorDash debugging round: candidates fix a broken round-robin dispatcher, then are asked to rebuild it with consistent hashing so node churn remaps a minimal fraction of keys. - Meeting Slot Generator - Medium
Produce every 5-minute check-in mark between two weekday timestamps, which may wrap around the end of the week - watch the off-by-one on which endpoints count. - Menu Tree Diff Counter - Medium
Merchants push a new menu tree every day - count how many nodes changed value, moved to a different parent, were added, or were deleted between the old and new menu trees. - Covered Service Zones - Medium
With one grid showing where drivers are available and another showing where deliveries are requested, count the connected demand regions in which every cell has driver coverage. - Peak Value Processing Order - Medium
Keep pulling out the smallest local peak - a value that beats every neighbor still in the list - and report the sequence in which the values disappear. - Directory Registry - Hard
Design a key-value store organized like UNIX file paths (a DoorDash Senior+ virtual onsite question) - the catch is that GetValue must climb toward the closest ancestor that has a value instead of only checking the exact path. - Ride Earnings Calculator - Hard
Parse a raw event log of ride starts/cancels/completions into active-time windows, then apply bonus-period doubling to compute total earnings - cancelled rides earn nothing. - Code Craft - Bootstrap API - Medium
DoorDash's "Code Craft" round: aggregate three upstream services (Consumer, Payment, Address) into one response, with an asymmetric partial-failure rule - Consumer failing is fatal, Payment/Address failing is not.
DoorDash System Design round questions (8)
- Design DoorDash From Scratch - Hard
The umbrella DoorDash System Design prompt: design the core three-sided marketplace end to end - customers, merchants, and dashers - before any single subsystem gets a deep dive. - Design the Dasher Dispatch / Matching System - Hard
Given a new order, find and assign the best available dasher - the reported focal point is geospatial indexing at scale rather than a naive nearest-neighbor scan. - Design Real-Time ETA Estimation - Hard
Predict and continuously refresh a delivery ETA using historical data, live prep-time and traffic signals, and dasher location - without recomputing everything on every update. - Design a Resilient Dasher Payment & Payout System - Hard
A system-design-scale version of the 'Dasher Pay' coding question: compute and disburse dasher earnings reliably, with idempotency so a retried payout is never duplicated or lost. - Design an Order Ratings & Reviews System - Hard
Customers rate orders, dashers, and merchants - design write-heavy rating ingestion and keep aggregate scores fresh without recomputing them from scratch on every read. - Design a Discounts / Promotions System - Hard
Apply promo codes plus merchant- and platform-funded discounts to an order - the reported crux is resolving conflicting/stacked promotions without over-spending a budget. - Design a Real-Time Order-Tracking System - Hard
Design the live map view showing order status and dasher location - the reported crux is fan-out cost: pushing frequent location updates cheaply to potentially many subscribers. - Design a Distributed Task Scheduler - Hard
A general infra prompt independent of the food-delivery domain: reliably schedule and run a large number of delayed/recurring jobs across a fleet of workers, at least once each.