DoorDash End-to-End System Design

Design DoorDash end to end (functional/non-functional requirements, entities, data model, APIs, architecture)

Asked in the screen: system design stage. The interviewer kept adding requirements during a 45-minute discussion. Clarify the product scope and assumptions before designing. Address the end-to-end system, including where machine learning is appropriate, how online and batch components interact, and how the design handles reliability, latency, consistency, and operational failures.

Deliverables:

1. Define functional and non-functional requirements.
2. Identify core entities and data relationships.
3. Propose data models and APIs.
4. Design the service architecture and critical workflows.
5. Explain ML components, if applicable, including training, serving, evaluation, and monitoring.
6. Discuss scaling assumptions, tradeoffs, and failure modes.