Mobility · San Francisco, California

Uber.

Ride-hailing, Uber Eats food delivery and freight, matching riders, drivers and couriers in real time.

its questions lean on

geo matching and location
machine coding with concurrency
real-time notifications
queues and schedulers
feeds

The rounds, as candidates describe them

Online assessment and phone screenAn online assessment, then a technical phone screen.source ↗
OnsiteFour rounds, DSA, LLD (machine coding), HLD and hiring manager.source ↗

Reported by candidates

From public interview write-ups; each links its source.

Design a Ride-Hailing ServiceSystem design
SQ-09 · Uber →IP-13 · Design a Proximity Service →W01 · DAY 04 · Hot Keys and Skew →reported in:LeetCode Discuss · Google, Microsoft, Uber and Atlassian experiences, "Design Uber" (2021) ↗
Design a Chat SystemSystem design
IP-08 · Design a Chat System →SQ-02 · WhatsApp Messaging →reported in:LeetCode Discuss · Uber SDE 2 interview experience (2024) ↗LeetCode Discuss · Uber SDE2 Bengaluru, WhatsApp group chat (2022) ↗
Design a Restaurant Discovery FeedSystem design
SQ-17 · Swiggy Food Delivery →IP-13 · Design a Proximity Service →W04 · DAY 04 · Feed Caching →reported in:LeetCode Discuss · Uber SDE2 in-office, Uber Eats restaurant feed backend (2024) ↗LeetCode Discuss · Uber L4 Bangalore, restaurants delivering in an area (2021) ↗
Design a Stock Price Alert SystemSystem design
IP-06 · Design a Notification System →W03 · DAY 01 · Queue vs Stream →W06 · DAY 03 · Advanced Features →reported in:LeetCode Discuss · Uber L4 Bangalore, offer (2024) ↗LeetCode Discuss · Uber SDE2 in-office, offer (2024) ↗
Design Webhook DeliverySystem design
W02 · DAY 04 · Webhook Delivery System →W02 · DAY 02 · Idempotency in Practice →reported in:LeetCode Discuss · Uber SDE-2 (2024) ↗
Design a Proximity ServiceSystem design
IP-13 · Design a Proximity Service →W01 · DAY 01 · Partitioning Deep-Dive →reported in:LeetCode Discuss · Uber L4 India, Yelp-like service (2020) ↗
Design a Parking LotLow-level design
LLD-01 · Design a Parking Lot →reported in:LeetCode Discuss · Uber SDE2 in-office, multi-floor lot for cars and bikes (2024) ↗LeetCode Discuss · Uber SDE-2 (2024) ↗
Design an In-Memory Message QueueLow-level design
LLD-08 · Design a Logging Framework (Pub-Sub) →IP-18 · Design a Distributed Message Queue →reported in:LeetCode Discuss · Uber L4 Bangalore, pull-based queue with TTL (2021) ↗LeetCode Discuss · Uber SDE2 hiring drive, Kafka-like with concurrency (2024) ↗
Design a Multithreaded Job SchedulerLow-level design
IP-17 · Design a Distributed Job Scheduler →W02 · DAY 05 · Distributed Cron & Job Scheduling →reported in:LeetCode Discuss · Uber SDE2 Bengaluru, tasks with prerequisites (2022) ↗LeetCode Discuss · Uber L4 Bangalore (2020) ↗
Design a Leaderboard (LLD)Low-level design
IP-14 · Design a Real-Time Leaderboard →reported in:LeetCode Discuss · Uber SDE2 in-office, offer (2024) ↗
Design a Logging FrameworkLow-level design
LLD-08 · Design a Logging Framework (Pub-Sub) →reported in:LeetCode Discuss · Uber SDE 2 Bangalore, offer (2024) ↗
Design a Key-Value Store with TransactionsLow-level design
IP-03 · Design a Distributed Key-Value Store →W05 · DAY 01 · Consistency Models →reported in:LeetCode Discuss · Uber onsite (2022) ↗

Likely, from what they build

Our pick, not a report: questions that fit Uber's products.

Design a Food Delivery SystemSystem design
SQ-17 · Swiggy Food Delivery →W03 · BOSS · Event-Driven Food Delivery Order System →
Design a Payment SystemSystem design
IP-20 · Design a Payment System →W05 · DAY 02 · Distributed Transactions — The Saga Pattern →

Study path

Every lesson the questions above point to, once, in order.

Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.