Uber logo
UberSoftware Engineer
Updated Sep 14, 2026

Uber Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Uber, newest first and distilled into what to expect across the loop.

Get your personalized Uber Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
1 month ago

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.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your 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.

Low-level designPractical implementationReal-world scenarios

Behavioral and Cultural Fit

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.

Time managementPacingAssessment pressure