ScaleCrafts

Design Uber

Match riders with nearby drivers in real time, track trips live and handle payments, like Uber or Lyft.

Functional requirements

  • Riders request a ride and see an ETA
  • Drivers share their location and the nearest available one is matched
  • Both see the trip live on a map

Non-functional requirements

  • Match within seconds
  • Location updates every few seconds
  • A driver is never matched to two riders

Scale

  • 20M trips per day
  • 5M active drivers sending location every 4 seconds
  • About 1.25M location updates per second

How you’ll be scored

10 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 Uber”, that starts with: Riders request a ride and see an ETA; Drivers share their location and the nearest available one is matched; Both see the trip live on a map. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (20M trips per day; 5M active drivers sending location every 4 seconds; About 1.25M location updates per second) 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: Match within seconds; Location updates every few seconds; A driver is never matched to two riders. 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 geospatial, real-time and matching 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.

Related problems

Loading your workspace…