I did a phone screen for a New Grad Software Engineer role at Uber. The recruiter call led pretty directly into a single technical question, and it felt very similar to a LeetCode-style problem—specifically “First Unique Number.” The whole screen centered on getting a correct, efficient approach and then walking through the reasoning clearly as I built the solution.
Overall it was a straightforward setup: one technical prompt rather than a long series of problems, and my main focus was making the logic clean and easy to follow. I didn’t move forward from that stage, but the experience was useful because it highlighted exactly what kind of coding question they expected for new-grad hiring.
2 months ago
My Uber process for an SDE-II role included an in-person LLD round that felt more practical than the typical system-design style exercise. The prompt was to design Uber Black, and the emphasis was on cab allocation logic rather than drawing boxes and arrows.
I worked through the flow of registering drivers, handling ride requests, and deciding how to allocate the nearest available driver. What stood out was how much they cared about having clean, running code-level thinking—making sure the logic could actually be implemented end to end.
2 months ago
For an SDE-II interview at Uber (level L4), my first round was an in-person BPS-style screening. The question came from a grid pathing vibe: there was…
3 months ago
Average Positive India
I had an online coding exam for a fresher-level role at Uber. It was moderately challenging—somewhere between medium and hard LeetCode-style questions…
3 months ago
Easy Positive India
My Uber interview experience was tied to an internal interview process and followed a pretty direct path: after the earlier Uber She++ internal interv…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Screening
The initial phone screen typically includes a single coding question, often resembling LeetCode-style problems, where candidates must demonstrate a clear and efficient approach to solving the problem. Candidates should prepare for algorithmic questions and be ready to explain their thought process clearly.
LeetCodeAlgorithmClear reasoning
Coding Interviews
Candidates can expect multiple coding interviews that focus on data structures and algorithms (DSA), often with follow-up questions that require extending initial solutions. It's crucial to be prepared for both solving the problem and discussing optimizations and trade-offs.
DSAFollow-up questionsOptimization
System Design Rounds
For mid to senior-level roles, system design interviews are common and emphasize practical, low-level design rather than high-level architecture. Candidates should be ready to discuss real-world implementation details and the logic behind their designs.
Behavioral questions are integrated into the interview process, often at the beginning of technical interviews, to assess cultural fit and collaboration skills. Candidates should prepare to discuss past experiences and how they align with Uber's values.
Behavioral questionsCultural fitCollaboration
Interview Structure and Timeline
The interview process can vary in length but often includes a series of technical rounds followed by a hiring manager conversation. Candidates should expect a structured timeline with clear communication throughout the process.
Interview structureTimelineClear communication
Pacing and Time Management
Candidates often report challenges with time management during coding assessments, where strict time limits can impact performance. Practicing pacing and managing time across multiple questions is essential for success.