Interview Questions / Uber
Uber Interview Questions & Process
Software Engineering · Product
Updated July 2026Uber's core business runs on real-time spatial indexing, graph routing and highly concurrent distributed processing, and its interviews reflect that more directly than most. Applied graph theory dominates: BFS, DFS, Dijkstra and Union-Find account for over a quarter of reported coding questions, because dispatch, mapping and routing are literally graph problems.
The sequence starts with a recruiter screen, then a CodeSignal online assessment of roughly 70 to 90 minutes across four coding challenges. The Business Phone Screen follows, a 45 to 60 minute live coding round on a shared editor that works as a genuine elimination gate, usually on graph or array manipulation. The onsite runs four to six rounds of 45 to 60 minutes: two algorithm rounds, a low-level design session, a high-level design session and a culture round built around the Go Get It value, which tests bias for action and whether you can make calculated, data-backed decisions with incomplete information. A hiring committee then reviews every scorecard independently before the offer discussion.
One rule is worth taking seriously: pseudocode is not accepted. Interviewers explicitly assess readability and whether the code compiles, so it needs to be runnable and edge-case aware in a shared editor without IDE support.
Efficiency is scored as well as correctness. A naive depth-first search from every node re-explores overlapping paths and fails at Uber's scale, where the memoised version is the expected answer.
The cost of walking in unprepared
Uber's process spans 6 distinct stages, often compressed into a single high-pressure loop. Most candidates only find out they weren't ready once the result lands.
Merra: run the Uber interview before it counts
Hope, Merra’s AI interviewer, runs a Uber-style mock out loud — the same question styles, real follow-ups — then scores you on the five dimensions real interviewers use, with a recording and transcript.
- 1Sign up free — no card, 5 full interviews available until used.
- 2Take the diagnostic — 15 minutes with Hope, get your baseline score.
- 3Practise Uber-style — company-tuned questions, honest feedback, watch your score climb.
No card details required. Your first 2 interviews are free.
Practise the Uber interview now
2 free interviews. Instant scored feedback. Know where you stand before Uber decides for you.
Start your free interviews2 free interviews · no card needed · no subscriptionThe Uber interview process
- 1Recruiter Screen. A 30-to-45 minute introductory call assessing basic experience, interest in spatial mobility/gig economy challenges, and logistical details.
- 2Online Assessment (OA). A 70-to-90 minute CodeSignal exam featuring 4 algorithmic coding challenges.
- 3Business Phone Screen (BPS). A 45-to-60 minute live coding elimination screen on a shared editor focusing on interactive graph-theory or array manipulation problems.
- 4Onsite / Virtual Loop. 4 to 6 rounds of 45 to 60 minutes each, including two algorithm coding rounds, one Low-Level Design (LLD) session, one High-Level Design (HLD) session, and a cultural fit round evaluating the "Go Get It" leadership value.
- 5Hiring Committee Review. An independent panel reviews all interviewer scorecards to determine the final selection.
- 6Offer Discussion. Negotiation and final compensation details.
Real Uber interview questions
As reported by recent candidates. The same styles Hope asks in a Uber-style mock.
Graphs
SWE · Algorithms
SWE · Algorithms
Trees
System Design
SWE · Algorithms
Prepping alone vs with Merra
Without Merra
- ✕Read questions, rehearse answers in your head
- ✕First time answering out loud is the real interview
- ✕No structured feedback on how you actually come across
- ✕Find out you weren’t ready from a rejection email
With Merra
- ✓Practise out loud before the real interview
- ✓Structured evaluation and feedback after every session
- ✓Review your session history and track improvement
- ✓Personalise practice by role, company, and focus areas
Pricing
- ✓No card needed · 2 free interviews available until used
- ✓Full scored feedback on every interview
- ✓Company-tuned mocks for Uber and others
- ✓Recording and transcript included
- ✓Cancel anytime
Uber interview FAQs
Why is a standard DFS algorithm discouraged for directed itinerary optimization in Uber's BPS?
A naive DFS executed from every node leads to redundant exploration of overlapping paths, resulting in a quadratic time complexity of O(N squared), which fails Uber's production scale requirements. Uber expects an optimized DFS with memoization (Dynamic Programming on Graphs), which reduces the worst-case time complexity to a linear scale of O(V + E).
Is pseudocode acceptable during Uber's coding rounds?
No. Uber interviewers explicitly evaluate code readability and compilation. Candidates must write fully runnable, edge-case-aware, and syntactically correct code in a shared editor.
How graph-heavy are Uber's software engineering interviews?
Extremely heavy. BFS, DFS, Dijkstra, and Union-Find (DSU) represent over 28% of all reported coding questions because Uber's core dispatch, mapping, and routing services operate on mathematical graphs.
What does the cultural value "Go Get It" test in the behavioral round?
It tests a candidate's bias for action, direct ownership, and comfort with making calculated, data-backed decisions when faced with incomplete information or high levels of operational ambiguity.
Related interview guides
Merra is an independent interview practice platform and is not affiliated with Uber. Interview formats vary by role, region, and year.
Know where you stand
Your first interview with Hope takes 15 minutes and gives you a baseline score. Free, no card, instant feedback.
Start your free interviews2 free interviews · no card needed · no subscription