Uber system design interview questions
5 questions on this site are reported in Uber software engineer interviews. Each is a guided run through requirements, back-of-envelope numbers, an interactive design, user flows and deep dives with interviewer follow-ups. Patterns covered: consistency, idempotency, ledger, fintech, geospatial, routing, graphs, cdn, matching, streaming, marketplace, fan-out, multi-channel, rate-limiting, priority-queues, algorithms, counters, redis, edge.
Attribution comes from public interview guides and candidate reports, not from Uber. It indicates where a question has been asked, nothing more.
Design a Payment System
Accept card payments for an e-commerce platform, move money correctly exactly once, and be able to prove it.
Design Google Maps
Map tiles, place search, turn-by-turn routing with live traffic, and ETAs for a billion users.
Design Uber
Match riders with nearby drivers in seconds, track trips live, and price them, for millions of concurrent users worldwide.
Design a Notification System
Deliver push, email, SMS and in-app notifications to hundreds of millions of users: the right channel, once, on time, and never at 3 a.m.
How to prepare for a Uber system design interview
Large-company loops run 45 to 60 minutes, expect numbers, and spend most of the time on deep dives. Work each question above in practice mode until you can produce the requirements, the estimates and the flows without looking, then read the interview framework guide for how to structure the hour. The other questions on the site teach patterns that show up in Uber interviews under different names.
- Design a URL Shortenerkey-generation · caching · cdn
- Design Slackreal-time · websockets · fan-out
- Design a News Feedfan-out · ranking · caching
- Design YouTubetranscoding · cdn · adaptive-bitrate
- Design a Matchmaking Systemqueues · scheduling · latency
- Design a Web Crawlerfrontier · politeness · dedupe