InterviewLegend

Design the Uber Eats Restaurant Dashboard

Signature problem
Alex Chen50 min readAdded 548 real interview reports

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.

The Uber angle
On this prompt, Uber interviewers care most about the counting pipeline. Expect probes on windowed aggregation at 100,000 orders a second, sliding against tumbling windows, sketches against exact counts, and late events. Uber runs Kafka, Flink and Apache Pinot in production, so all three are fair names. Spend most of the hour there.

UberPremium lesson · System design round

The Uber design, worked end to end.

  1. The API and data modelSystem design · Signature problem
  2. The design, drawn out2 diagrams
  3. 5 deep divesWith the tradeoffs
Get the Uber questions

$49 a year · all 107 companies · instant access

548 Uber interview reports · guide updated

Uber interview guide

Know what Uber asks before you walk in.

30 coding · 8 system design · 21 behavioral questions

Get Premium$49 a year · Instant access
Or start freeNo card.

Get their questions first.

Had your Uber interview?How we research

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.