Design DoorDash
Let customers order from local restaurants and send couriers to deliver it, with live tracking, like DoorDash.
Functional requirements
- Browse nearby restaurants and menus
- Place and pay for an order
- Assign a courier and track the delivery live
Non-functional requirements
- Orders are never lost or double-charged
- Courier assigned within a minute
- Live location within seconds
Scale
- 5M orders per day
- 500K active couriers sending location
- Lunch and dinner peaks at 5 times the average
How you’ll be scored
11 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design DoorDash”, that starts with: Browse nearby restaurants and menus; Place and pay for an order; Assign a courier and track the delivery live. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (5M orders per day; 500K active couriers sending location; Lunch and dinner peaks at 5 times the average) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Orders are never lost or double-charged; Courier assigned within a minute; Live location within seconds. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe dispatch, geospatial and real-time here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.