Uber Distributed Systems Interview Questions 2026

Published July 22, 2026 · Updated July 22, 2026

7 real Distributed Systems interview questions asked at Uber. Upvoted by engineers who cleared the loop. Covers System Design, Technical, Debugging rounds.

7 questions
320 engineers asked
423 upvotes
Company: Uber
Technology: Distributed Systems

All Distributed Systems Questions Asked at Uber

Uber Hard System Design round Distributed SystemsRedisKafka

Design Uber's driver-rider matching system. How do you match the nearest available driver to a rider within 200ms at global scale? Cover: geospatial indexing (H3/S2), the dispatch algorithm, how you handle supply-demand imbalances, and what happens when a matched driver rejects the trip.

↑ 99 upvotes · 98 engineers asked this · SDE2
Uber Hard System Design round KafkaRedisDistributed Systems

Design Uber's dynamic pricing (surge) system. When supply is low and demand is high in a geofenced zone, prices increase automatically. Explain the data pipeline, the pricing model, how you prevent oscillations (price going up → drivers rush in → price drops → drivers leave), and regulatory constraints.

↑ 75 upvotes · 74 engineers asked this · SDE2
Uber Hard System Design round Distributed SystemsRedisKafka

Design Uber Eats' order batching system. A single delivery partner picks up orders from multiple nearby restaurants and delivers to multiple customers in one trip. How do you optimise the route and assignment?

↑ 62 upvotes · 41 engineers asked this · SDE2
Uber Hard Technical round Distributed SystemsRedis

Uber uses H3 hexagonal geospatial indexing. Explain why hexagons are better than squares or lat/lng grids for proximity searches. How do you find all drivers within 2km of a rider using H3 resolution levels?

↑ 54 upvotes · 34 engineers asked this · SDE2
Uber Hard System Design round Distributed SystemsPostgreSQLKafka

Design Uber's payment reconciliation system. Uber collects payments in 70+ countries with different currencies, payment methods, and regulations. How do you reconcile driver payouts against rider charges and detect discrepancies?

↑ 60 upvotes · 38 engineers asked this · SDE2
Uber Hard System Design round 4-8 yearsSystem DesignDistributed Systems

Design the rider-driver matching system for a ride-hailing app. How would you balance minimizing rider wait time against fairness in driver earnings distribution?

↑ 46 upvotes · 23 engineers asked this · Senior SDE
Uber Hard Debugging round 3-7 yearsDistributed SystemsKafka

Trip fares are occasionally being calculated twice, double-charging riders. The fare calculation service is stateless and horizontally scaled behind a queue. Where would you look first, and what's the likely root cause?

↑ 27 upvotes · 12 engineers asked this · Senior SDE

Practice these questions with AI feedback

Get instant grading on your answers, identify your weak areas, and generate a personalised 14-day study plan — all free.

Build my study plan →

More Uber Questions

Uber Python Questions Uber Kafka Questions

Distributed Systems Questions at Other Companies

Meta Distributed Systems Questions

Browse by company

Amazon Google Microsoft Flipkart Swiggy Meta Apple Netflix Uber Airbnb Stripe Razorpay PhonePe Paytm Zomato Salesforce Oracle Adobe LinkedIn Atlassian Accenture Deloitte Wipro Infosys TCS Capgemini PayU General Anthropic OpenAI TikTok JPMorgan Walmart Spotify DoorDash Goldman Sachs Revolut Canva Capital One Lyft SAP Siemens Shopify Grab Cognizant LTIMindtree Myntra Hotstar Twitter Snowflake

Frequently asked questions

Design Uber's driver-rider matching system.
Design Uber's driver-rider matching system. How do you match the nearest available driver to a rider within 200ms at global scale? Cover: geospatial indexing (H3/S2), the dispatch algorithm, how you handle supply-demand imbalances, and what happens when a matched driver rejects the trip.
Design Uber's dynamic pricing (surge) system.
Design Uber's dynamic pricing (surge) system. When supply is low and demand is high in a geofenced zone, prices increase automatically. Explain the data pipeline, the pricing model, how you prevent oscillations (price going up → drivers rush in → price drops → drivers leave), and regulatory constraints.
Design Uber Eats' order batching system. A single delivery partner picks up orders from multiple nearby restaurants and delivers to multiple customers in one trip. How do you optimise the route and assignment?
Design Uber Eats' order batching system. A single delivery partner picks up orders from multiple nearby restaurants and delivers to multiple customers in one trip. How do you optimise the route and assignment?
Uber uses H3 hexagonal geospatial indexing. Explain why hexagons are better than squares or lat/lng grids for proximity searches. How do you find all drivers within 2km of a rider using H3 resolution levels?
Uber uses H3 hexagonal geospatial indexing. Explain why hexagons are better than squares or lat/lng grids for proximity searches. How do you find all drivers within 2km of a rider using H3 resolution levels?
Design Uber's payment reconciliation system. Uber collects payments in 70+ countries with different currencies, payment methods, and regulations. How do you reconcile driver payouts against rider charges and detect discrepancies?
Design Uber's payment reconciliation system. Uber collects payments in 70+ countries with different currencies, payment methods, and regulations. How do you reconcile driver payouts against rider charges and detect discrepancies?
Design the rider-driver matching system for a ride-hailing app. How would you balance minimizing rider wait time against fairness in driver earnings distribution?
Design the rider-driver matching system for a ride-hailing app. How would you balance minimizing rider wait time against fairness in driver earnings distribution?
Trip fares are occasionally being calculated twice, double-charging riders. The fare calculation service is stateless and horizontally scaled behind a queue. Where would you look first, and what's the likely root cause?
Trip fares are occasionally being calculated twice, double-charging riders. The fare calculation service is stateless and horizontally scaled behind a queue. Where would you look first, and what's the likely root cause?