How Uber Interviews in 2026: Process, Questions & What They Score

1. 01

   Count the number of vowel substrings in a string that contain all five vowels

   Tests sliding-window counting on strings under the all-five-vowels constraint.

2. 02

   Given a 2D binary matrix with exactly two islands, find the minimum number of 0s that must be flipped to 1 to connect them into one island

   Tests multi-source BFS: collect one island, then expand outward to reach the other in fewest flips.

3. 03

   Implement an LRU Cache

   Tests O(1) LRU design; hash map plus doubly linked list is the expected structure.

4. 04

   Design a Hit Counter / rate limiter using a sliding-window approach

   Tests sliding-window state design for counting or limiting events over a moving time window.

5. 05

   Alien Dictionary: derive character ordering from a sorted word list (topological sort)

   Tests topological sort: derive ordering constraints from adjacent word pairs and detect cycles.

6. 06

   Bus Routes: minimum number of buses to get from source to target (BFS/graph); widely reported as one of Uber's most-repeated interview questions

   Tests BFS over routes rather than stops; modeling routes as graph nodes is the key insight.

7. 07

   Solve a 0/1 knapsack-style maximization or word-break dynamic programming problem

   Tests dynamic programming: 0/1 knapsack state design or word-break substring decomposition.

8. 08

   Design a simplified Twitter-like feed supporting post, like, and dislike operations (OOP + coding)

   Tests object-oriented design of a feed with post, like, and dislike, balancing clean classes with working code.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

1. 01

   Design a ride-matching/dispatch system (pair riders with nearby drivers at low latency and scale)

   System design: they probe geo-indexing, low-latency matching, and scaling rider-driver dispatch.

2. 02

   Design a real-time surge-pricing engine that ingests live location/demand data and recalculates multipliers

   System design: tests streaming demand and supply signals into a real-time pricing recalculation loop.

3. 03

   Design a real-time driver/vehicle location-tracking system ingesting millions of GPS pings per second

   System design: they probe ingesting millions of GPS pings per second: partitioning, storage, freshness.

4. 04

   Design an ETA-prediction service

   System design: tests serving ETA predictions at scale: features, model serving, and latency budgets.

5. 05

   Design a notification delivery system at global scale

   System design: they probe global fan-out, channel routing, retries, and delivery guarantees.

6. 06

   Design a payment-processing system for a marketplace like Uber

   System design: tests marketplace payment flow: charging riders, paying drivers, ledgers, idempotency.

7. 07

   Design Dropbox or WhatsApp (generic large-scale system, used to gauge fundamentals)

   System design: a generic large-scale prompt used to gauge storage, sync, and messaging fundamentals.

8. 08

   Design a ride-sharing app end-to-end (a generic version of Uber's own product)

   System design: tests decomposing the full ride flow into services, from request through payment.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

1. 01

   Tell me about yourself / walk me through your background

2. 02

   Tell me about a time you disagreed with a coworker or teammate. How did you resolve it?

3. 03

   Describe a time you took ownership of a problem beyond your defined scope

4. 04

   How do you earn the trust of a new team you've just joined?

5. 05

   Tell me about a time you had to make a decision with incomplete information or high ambiguity

6. 06

   Describe a time you advocated for the end user/customer in a product or engineering decision

7. 07

   Tell me about a time you failed. What happened and what did you learn?

8. 08

   Describe how you managed a project with a tight timeline and limited context

1. 01

   Walk me through the most technically challenging project you've shipped, from start to finish

   Bar-raiser deep dive; tests genuine ownership and technical depth on your hardest shipped project.

2. 02

   What was the system architecture, and what specific tradeoffs did you make and why?

   Tests architectural reasoning; expect the specific tradeoffs you made and alternatives you rejected.

3. 03

   How did you quantify the impact or success of this project?

   Tests impact measurement: concrete metrics tying the project to user or business outcomes.

4. 04

   What would you do differently if you rebuilt this project today?

   Tests reflective engineering judgment: what the design got wrong and how you would rebuild it now.

5. 05

   Describe a technical decision you made that other stakeholders disagreed with. How did you handle it?

6. 06

   What was your specific individual contribution versus the team's, on this project?

   Tests honest attribution; interviewers separate your specific contribution from the team's work.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.