Company interview guide
Uber interview process and practice questions
Uber's careers site describes a talent-team conversation, a chat with the hiring manager, a technical interview for tech roles, a job-related exercise for some roles, and a team interview. Candidates commonly report design questions built around real-time, location-based systems, and Uber says how you approach a problem matters as much as the solution.
As candidates commonly report it; it varies by team, level and year. Last reviewed 18 October 2026.
The interview process
- 1Recruiter screen
- 2Technical phone screen
- 3Onsite loop: coding, system design and a collaboration / behavioral interview
- 4Hiring manager interview
What interviewers listen for
- Problem solving at scale
- Ownership
- Collaboration
- Customer focus
- Clear communication of trade-offs
Behavioral questions
Tell me about a time you owned a problem outside your role.
A good answer covers
- The problem and why nobody else was fixing it
- What you did, including who you brought in
- The result and whether it stayed fixed
Tell me about a time you had to make a trade-off between speed and quality.
A good answer covers
- The deadline and the quality risk
- How you chose, and what you did to limit the downside
- What happened, and what you'd choose next time
Tell me about a time you used data to change someone's mind.
A good answer covers
- Their view and why it was reasonable
- The data you gathered and how you checked it
- How you presented it and what changed
Tell me about a time you worked with operations, support or another non-engineering team to fix a customer problem.
A good answer covers
- The customer problem and what each team could see of it
- How you worked together and kept everyone informed
- The fix and how you knew customers were better off
Tell me about a launch that didn't go as planned. What did you change afterwards?
A good answer covers
- What went wrong and how quickly it was caught
- Your part in the response
- The process change that followed
Role and technical questions
How would you design the matching of riders to drivers in a busy city?
A good answer covers
- What 'best match' means: pickup time, fairness to drivers, overall wait times
- Finding nearby drivers fast with a geographic index, updated as drivers move
- Handling peaks, drivers who decline, and two riders matched to one driver
How would you estimate a trip's arrival time, and how would you make the estimate better over time?
A good answer covers
- Routing on the road map with live and historical traffic
- Learning from past trips: time of day, weather, pickup delays
- Measuring error against actual arrival times and improving the worst cases
How would you design the live map that shows a rider where their driver is?
A good answer covers
- How often the driver's app sends location, balancing accuracy with battery and data
- Pushing updates to the rider over a persistent connection
- Smoothing GPS jumps and handling dropped connections
How would you design a food-delivery order flow so the restaurant, courier and customer all see the same status?
A good answer covers
- An order state machine with clear allowed transitions
- Events published to each party, with retries and duplicate handling
- What happens when a step fails: a restaurant doesn't confirm, a courier cancels
How would you store drivers' locations so you can quickly find the nearest available ones?
A good answer covers
- A spatial index, such as geohashes, a quadtree or hexagonal cells
- Frequent updates kept in memory, partitioned by region
- Filtering by availability and vehicle type, and expanding the search when none are close
Rider cancellations rose in one city last week. How would you find out why?
A good answer covers
- Checking the data first: a tracking change, a holiday, an app release
- Breaking it down by time, area, wait time, rider versus driver cancellations
- The most likely cause and how you'd confirm it
Why Uber? Fit and HR questions
Why Uber, and which part of the business interests you most?
A good answer covers
- A specific area, such as mobility, delivery or freight, and why
- A link to your skills or experience
- The problem there you'd most like to work on
Which Uber product would you improve for riders, drivers or merchants, and how would you measure the result?
A good answer covers
- One user group and a specific pain point
- The change and the trade-off it brings for the other sides of the marketplace
- A success metric and a guardrail
Tips
- Real-time, location-based systems are favourite design topics.
- Uber's hiring page suggests reading its newsroom for recent launches and priorities; mention one that connects to the team.
- In design rounds, talk about failure: lost connections, GPS errors, retries and duplicate requests.
- Prepare stories with numbers for the hiring manager chat, which goes deeper into your skills and decisions.
- For some roles, expect a job-related exercise; if you present it in the team interview, explain your choices, not just the results.
Practise it out loud
A mock interview asks the way Uber's interviewers are known to, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer.
About this guide
Written by Orbit from Uber's own public pages and what candidates commonly report. Orbit isn't affiliated with Uber. The questions are practice questions in the style of its interviews, not questions taken from them. Processes change, so check the job post and what your recruiter tells you.