Design the Uber Eats Restaurant Dashboard
A restaurant dashboard shows an owner how their restaurant is doing right now. How many orders came in, how much money they brought and which dishes are selling. Underneath, it's a streaming aggregation problem. Every order placed anywhere on Uber Eats has to land in the right restaurant's numbers within seconds, in three windows at once. Candidates report it as one of the most common prompts in Uber's high-level design round right now. It comes up from SDE-2 loops up to L5 (Senior), and in Data Engineer loops as a pipeline question. The details vary. One version asks for the top 3 dishes and the number of orders, another for the total value of all orders and a top-k list. The shape stays the same, with a firehose of orders coming in and a small live summary per restaurant going out.
UberPremium lesson · System design round
The Uber design, worked end to end.
- The API and data modelSystem design · Signature problem
- The design, drawn out2 diagrams
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
548 Uber interview reports · guide updated
Uber interview guideKnow what Uber asks before you walk in.
30 coding · 8 system design · 21 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.