Uber Interview Experiences

Overview

How Uber’s Software Engineer I loop actually runs for early-career candidates in India, based on aggregated reports from GeeksforGeeks, Blind, and IGotAnOffer - team and level change the exact mix.

One title, one city: Uber's actual India entry point

Nearly all of Uber’s India entry-level hiring funnels into a single title - Software Engineer I out of Bengaluru - filled through targeted application windows and referrals, not a blanket walk-in drive across colleges. No fixed CGPA cutoff is published anywhere. Before acting on a forwarded “Uber campus drive” notice, cross-check it against Uber’s careers page.

Community-reported total compensation for a Software Engineer I in India clusters roughly in the ₹20-36 LPA range (Levels.fyi, 2026), skewed by location, stock refresh, and level within the band - confirm the real number on your own offer letter, not a forwarded screenshot.

How to use this page

Read the round table first, then the experiences. Practise the coding and low-level-design patterns with edge cases, and keep one clear story each for ownership, grit, and a project decision you’d defend even if it hadn’t gone perfectly.

Round-wise process

Round	Duration	What it tests
Online Assessment	60-90 min	2-3 DSA coding problems
Technical Round 1	45-60 min	OS/networking/OOPs fundamentals + coding
Technical Round 2	45-60 min	Machine coding / low-level object-oriented design
System design (experienced / some loops)	45-60 min	Marketplace-scale design: dispatch, ETA, surge pricing
Hiring Manager / HR	30-45 min	Behavioural fit, project deep dive, cultural norms
Bar Raiser (select loops)	45-60 min	Independent check against Uber’s hiring bar and cultural norms

Real interview experiences

These are rewritten from public candidate write-ups, not invented composites. Details differ by campus and year.

Experience 1: Summer internship, on-campus (offer)

Source: Uber Interview Experience for Summer Internship (On-Campus) - GeeksforGeeks

Round 1 - Online assessment (CodeSignal, 60 min)

• Three problems: a base-conversion question, a bit-manipulation / substring question, and a DP variant modelled on a bowling game.
• The candidate finished two fully and scored partially on the third - and still cleared. Partial credit does count here.

Round 2 - Technical 1 (Zoom + CodeSignal, 45 min, two interviewers)

• Find the critical and pseudo-critical edges in a minimum spanning tree - a LeetCode Hard. Solved with Kruskal’s plus a hand-written DSU, comparing MST weights with each edge forced in or excluded.
• Implementation got messy mid-round; talking through it and recovering was enough.

Round 3 - Technical 2 (45 min, two interviewers)

• Explicitly about OOP and coding style, not time complexity: design a restaurant data structure answering queries about dishes, ingredients, and bill totals. A backtracking extension was discussed as a bonus.

Round 4 - Hiring manager (30 min)

• Intro, a computer-architecture project discussed in depth, and leadership / ownership questions.

Outcome: Offer extended.

Experience 2: SDE I, on-campus (rejected at round 2)

Source: Uber Interview Experience For SDE I (On-Campus) - GeeksforGeeks

Worth reading precisely because it did not end in an offer.

• Round 1 (HackerRank, 90 min, medium): Burst Balloons (interval DP) and a binary-search-on-answer question over a monotonic equation.
• Round 2 (video call, 60 min, medium): insertion at a given position in a doubly linked list, then a non-standard DP problem the candidate had not seen a template for.
• Outcome: Not shortlisted after round 2.

Takeaway: Uber’s full-time screen leans harder on DP and graphs than most fresher loops, and the questions are frequently non-standard - patterns you can adapt matter more than problems you have memorised. Note also that the OA platform varies by drive (CodeSignal and HackerRank both appear in write-ups, at 45-90 minutes), so confirm the format from your placement email rather than assuming.

Questions that come up often

Coding / technical

1. Array/string manipulation and linked-list problems (e.g. find the k-th node from the end)
2. Detect cycle in a directed graph - DFS colouring / topological sort
3. Process vs thread, TCP vs UDP, and other OS/networking basics
4. OOPs concepts explained with a real project example
5. Machine coding: design a small object-oriented system (remote control, vending machine) with extensible class boundaries

System design (experienced / some loops)

1. Design the rider-driver dispatch/matching system
2. Design ETA prediction for a trip in progress
3. Design a surge-pricing engine reacting to demand within about a minute
4. How would you keep a geospatial driver index fresh as locations update every few seconds?

HR / behavioural

1. Tell me about a time you owned a problem nobody assigned to you
2. A disagreement with a teammate and how you handled it
3. Why Uber, specifically?
4. Relocation preference and notice period

Practical tips for Uber

• Clear the online assessment first - all problems need to actually pass, not just look reasonable.
• For the machine-coding round, narrate your class design before typing; interviewers often probe how you’d extend it, not just whether it runs.
• OS, networking, and OOPs fundamentals still open a lot of Uber panels - do not skip them assuming only DSA matters.
• If you reach system design, explain dispatch/ETA/surge pricing in plain language: inputs, outputs, what breaks first at scale.
• HR/behavioural answers should be concrete. One story with a real result beats several slogans about “ownership.”

HR interview

After the technical rounds, Uber usually closes with a Hiring Manager or HR conversation: motivation, relocation, notice period, and a couple of behavioural stories checked against its cultural norms. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common Uber HR questions, sample answer frames, and STAR tips.

Similar companies

Google · Amazon · Microsoft · Ola · Swiggy · Zomato