Uber Software Engineer Interview
A graph-heavy coding loop, a CodeSignal assessment, a prominent marketplace-scale system-design round, and a values-driven behavioural round.
Start the Uber mock interview → See all boards
A free AI panel interview that questions you in Uber’s style, follows up when an answer is thin, and returns a scored, evidence-backed report — seeded from your own practice history on Wrexa Edge.
The Uber interview, in brief
Uber runs a consistent, rubric-driven interview loop that scores candidates uniformly across teams and locations, with a strong algorithm bar and a prominent marketplace-scale system-design component for experienced engineers. Each interviewer scores defined competencies — problem solving, engineering fundamentals, communication, and ownership.
A recruiter screen is followed by a CodeSignal General Coding Assessment, a technical phone screen, and an on-site loop of four to six rounds — coding, system design (for experienced roles), a collaboration/leadership behavioural round, and an independent bar-raiser. New grads see more coding and lighter design.
Interview rounds
-
1. Recruiter screen ~45–60 min
-
2. Online assessment (CodeSignal) ~70–90 min · 4 problems
-
3. Technical phone screen ~45–60 min
-
4. On-site loop 4–6 rounds · ~60 min each
-
5. Bar raiser Independent interviewer
Coding & DSA topics
System design
A distinct, prominent round for experienced engineers, mapping to Uber's marketplace scale — a ride/matching service, a feed, a messaging app, or a web crawler: clarify requirements, high-level design, components and data model, trade-offs, bottlenecks, and scaling. For new grads it is often replaced by an additional coding round or a lighter high-level system. There is no separate timed machine-coding round.
Behavioural round
The collaboration & leadership round is scored against Uber's cultural values — ownership, a bias to act, seeing both detail and the big picture, and building trust across teams. Interviewers probe collaboration, resolving disagreement, working under time pressure, and past impact. STAR structure is expected.
Representative question categories
Patterns in Uber’s style — not verbatim proprietary questions.
- Graphs — BFS/DFS, shortest path, or connected components on a grid or adjacency structure.
- Dynamic programming — Knapsack-style optimisation or subsequence/partition problems.
- Arrays & strings — Sliding window, two-pointer, substring/counting patterns.
- System design (experienced) — Design a ride/marketplace-matching service, a feed, a messaging app, or a web crawler.
- OO / entity modelling — A parking-lot-style object-oriented design.
- Behavioural — Resolving a disagreement, building trust, or delivering under deadline pressure.
How to prepare
Do
- Prioritise graph problems — Uber leans on traversal, shortest path, and connected components.
- On the CodeSignal OA, budget time for the hard question but bank the easy/medium ones first.
- For experienced design, use any scale figure given and reason explicitly about the bottleneck.
- Prepare STAR stories on ownership, resolving disagreement, and delivering under deadline pressure.
Avoid
- Neglecting graph patterns, Uber's strongest area.
- On the OA, spending so long on the hard problem that easier ones are left unfinished.
- A behavioural answer with no individual ownership or measurable impact.
Who can apply
Both new grads (university pipeline) and experienced engineers; the round mix depends on level — new grads see more coding and less deep design, senior candidates get the design and retrospective/bar-raiser emphasis.
Uber interview FAQ
- What is Uber's online assessment?
- A CodeSignal General Coding Assessment — typically four problems (one easy, two medium, one hard) in ~70–90 minutes, proctored, producing a completion-and-code-quality score. It is sometimes waived depending on the pipeline.
- Does Uber ask system design for new grads?
- Usually not deeply. The system-design round is prominent for experienced engineers (marketplace-scale). For new grads it is often replaced by an additional coding round or a lighter high-level system.
- What DSA topics does Uber focus on?
- Graphs are especially prominent (traversal, shortest path, connected components), alongside trees, arrays, strings, hashing, binary search, and dynamic programming — predominantly LeetCode medium.
- Does Uber have a bar raiser?
- Yes — an independent interviewer who protects the hiring bar. Naming varies across guides; for senior candidates the round is sometimes framed as a technical retrospective.
Practise now
Rehearse the full loop with an AI panel modelled on Uber’s process, in text, voice, or video.
Other company interviews
Verified from
Wrexa Edge is an independent exam-prep platform and is not affiliated with, authorised by, or endorsed by Uber. This guide is based on publicly documented interview practice; it does not reproduce any employer’s internal rubric or question bank, and it does not predict a hiring outcome.