Uber Software Engineer Interview Experience
Uber · Mid level
Interview process
The process was well-structured — it started with a recruiter screen, followed by a technical phone interview, and then a virtual onsite with 4–5 rounds covering coding, system design, and behavioral questions. What went well was that the interviewers were communicative and the scheduling was smooth. What didn't go well was that the system design round felt rushed — there wasn't much time to go deep into trade-offs before moving to the next topic. Feedback after each round was limited, which made it hard to gauge where I stood.
Interview rounds · 3
- 1
Online assessment
TechnicalCoding- Q1. DSA Medium - hard problem
- 2
Phone screen
CodingTechnical- Q1. LLD question of get nearby open restaurants
- 3
Technical round
- Q1. LLD Round question was first time visitors
Tips from the candidate
Grind LeetCode mediums and hards, especially around graphs, dynamic programming, and sliding window problems. For system design, practice designing large-scale distributed systems like ride-matching or surge pricing — Uber-specific scenarios came up. Make sure your behavioral answers are crisp, data-driven, and tied to measurable impact. Know Uber's Leadership Principles and be ready to talk about times you drove results under pressure or with incomplete information.
Company culture
The interviewers genuinely seemed passionate about solving hard, real-world problems at scale. There was a strong sense of ownership — people spoke about their work as if they personally cared about the outcome, not just shipping features. The team came across as fast-moving and high-accountability, which was energizing. There was also a noticeable emphasis on data-informed decision-making in every conversation, which suggests a culture that values evidence over gut feeling.