These are LLD questions of the kind Uber actually asks — the patterns reported from Uber's AI-engineering rounds, where design trade-offs, scale and failure modes matter as much as definitions. Treat this page as a mock interview: say every answer out loud before revealing it. If one surprises you, the lesson behind it is linked at the bottom.
Uber LLD concept questions
Uber's LLD rounds often ask: design a simplified ride-matching system that assigns the nearest available driver to a rider's request.
Asked in
A ride goes through REQUESTED → DRIVER_ASSIGNED → IN_PROGRESS → COMPLETED (or CANCELLED at various points). What pattern models this cleanly, and why not just a status string with if/else checks everywhere?
Asked in
Uber's fare depends on distance, time, and surge multiplier, and the formula changes by city and by season. What pattern fits the fare calculation itself?
Asked in
How to use this page: Uber rarely asks something you've never seen — they ask a standard LLD concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the LLD course lessons, and the follow-up stops being scary.
Keep practising: SOLID Principles, Strategy Pattern, Design a Parking Lot and UML Diagrams cover what most Uber LLD rounds test.