What questions are asked in Uber interviews?

Uber interviews commonly cover DSA coding (Longest substring without repeating characters; Binary tree level order traversal), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as dispatch system, ETA prediction, geospatial indexing. Behavioural questions check ownership, teamwork, and why Uber.

How many rounds are there in the Uber interview?

Uber typically has 4 stages: Online Assessment (90–120 min), Technical Round 1 (45–60 min), Technical Round 2 (45–60 min), Hiring Manager / HR (30–45 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for Uber interviews?

For Uber, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on dispatch system and ETA prediction. Use STAR for behavioural answers and ask one thoughtful question at the end.

Uber Interview Experience 2025–2026 — Real Candidate Stories

Uber interview experience

These write-ups reflect how Uber fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

Uber placement process typically includes online assessment, technical interview, and HR interview rounds. See the placement process section for complete details.

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: Uber eligibility criteria for freshers include minimum percentage requirements, degree requirements, and other criteria. Check the eligibility section for detailed

Fresher offers (candidate-reported) often land around of August 2026): Software Engineer I: ₹18-25 LPA for new graduates, Software Engineer II: ₹25-35 LPA (1-2 ye. Treat numbers as directional — confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online Assessment	90–120 min	2–3 coding problems (DSA)
Technical Round 1	45–60 min	DSA + project deep dive
Technical Round 2	45–60 min	DSA / system design basics
Hiring Manager / HR	30–45 min	Behavioural + team fit

Real interview experiences

Experience 1: SDE / Software Engineer (2025)

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

Focus stayed on problem-solving speed and clean code, not trick questions.
Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

Coding: Longest substring without repeating characters — approach used: sliding window + hashmap. Interviewer cared about complexity and edge cases.
Follow-up coding: Binary tree level order traversal — BFS with queue.
Domain discussion around dispatch system and ETA prediction — they wanted practical trade-offs, not buzzwords.
Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

Why this company?
A time you disagreed with a teammate
Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to Uber’s domain (dispatch system).

Experience 2: SDE / Software Engineer (2024–2025)

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
Second technical leaned more into geospatial indexing and system design basics (APIs, DB choice, failure modes).
Coding warm-up: Detect cycle in a directed graph — DFS colouring / Kahn’s algo.

Mistakes to avoid

Jumping into code without clarifying constraints
Treating HR as a formality — Uber still filters on communication and intent
Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For Uber, consistent DSA plus a clear story on dispatch system beats a perfect CGPA with weak explanation.

Questions that come up often

Coding / technical

Longest substring without repeating characters — typically expects sliding window + hashmap
Binary tree level order traversal — typically expects BFS with queue
Detect cycle in a directed graph — typically expects DFS colouring / Kahn’s algo
Discussion on dispatch system and ETA prediction — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why this company?
A time you disagreed with a teammate
Ownership example from a project
Relocation to the hiring city?

Practical tips for Uber

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about dispatch system in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many Uber panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Uber HR Interview Questions — common HR questions and how to answer them
Uber Preparation Guide — round-wise prep plan
Uber Coding Questions — practice problems with approaches
Uber Previous Year Papers — past papers and patterns
Uber Placement Papers — company overview, eligibility, and process

Last updated: August 2026