UBER · SYSTEM DESIGN
Uber system design interview questions
L4 candidates get one standard HLD round. At L5A and above, design weighs more and is checked again by the Bar Raiser through a deep dive on your own past systems.
Which levels get a design round
| Level | Uber title | Design round | Low-level design |
|---|---|---|---|
| SDE 1 | L3 Software Engineer I | Usually not | Yes |
| SDE 2 | L4 Software Engineer II | Yes | Yes |
| Senior Software Engineer (SDE 3) | L5A Senior Software Engineer | Yes | Yes |
| Staff Software Engineer | L5B Staff, L6 Senior Staff | Yes | – |
Design questions candidates report
-
Design Splitwise
Design a wallet app where a hundred million people top up, send money to friends and pay shops. Requirements and scale, the wallet API and ledger data model, then the hard parts: atomic same-shard transfers that never go negative, cross-shard transfers with a saga and a clearing account, single-writer event sourcing for very high throughput, hot merchant accounts, holds, limits and reconciliation with the bank.
Full walkthrough: Digital wallet -
Show every driver on a map in real time
A senior-level design for a ride-hailing app like Uber: requirements, the math for half a million location updates a second, rider and driver APIs, a sharded in-memory supply index on hexagon cells, nearest-driver search by ETA rather than distance, matching that never double books a driver, batched matching, surge pricing per cell, a trip state machine, cell-based isolation, and trade-offs at 10x.
Full walkthrough: Uber -
Design Dropbox
How to design a cloud file storage and sync service like Google Drive or Dropbox: requirements, storage and traffic math, splitting files into content-addressed blocks, resumable uploads and deduplication, separating metadata from blobs, a change journal with cursors so every device syncs, push notifications, conflict handling and version history, sharing permissions, and the trade-offs.
Full walkthrough: Google Drive Practise on the design board -
Design Messenger
A LADDER walkthrough of a mobile chat system: requirements, scale math for 20 billion messages a day and 200 million open connections, the WebSocket and REST API, a message store partitioned by conversation, then the deep dives: routing between chat servers, offline delivery and push, sent-delivered-read receipts, per-conversation ordering, group fan-out, presence, media and end-to-end encryption.
Full walkthrough: WhatsApp Practise on the design board
How to answer any design question: the LADDER method · How the design round is scored by level · Low-level design and machine coding
Questions people ask
When does Uber ask system design?
A design round is part of the loop for SDE 1 (L3 Software Engineer I), SDE 2 (L4 Software Engineer II), Senior Software Engineer (SDE 3) (L5A Senior Software Engineer), Staff Software Engineer (L5B Staff, L6 Senior Staff). L4 candidates get one standard HLD round. At L5A and above, design weighs more and is checked again by the Bar Raiser through a deep dive on your own past systems.
What system design questions does Uber ask?
Candidates report: Design Splitwise; Show every driver on a map in real time; Design Dropbox; Design Messenger.
System design questions at other companies
- Amazon
- Microsoft
- Meta
- Apple
- Netflix
- Airbnb
- Stripe
- Atlassian
- Goldman Sachs
- Salesforce
- Oracle
- Adobe
- Flipkart
- Walmart Global Tech
- PhonePe
- Swiggy
- Razorpay
System design questions across all companies · Behavioral questions