Real, anonymous reports from people who interviewed for Software Engineer at Uber, newest first and distilled into what to expect across the loop.
My first major step was an online coding exam. It came with medium-to-hard LeetCode-style questions, and the timer was tight: 45 minutes per question across three questions. I’d previously tested myself for a fresher-level setup, so the structure didn’t completely blindside me, but the time pressure still mattered a lot.
I went through an internal follow-up process tied to Uber’s she++ interviews, and the timeline moved fast. I had two DSA rounds, and after completing them, I got an offer within a couple of days.
Candidates typically start with an online assessment featuring 2-3 medium-to-hard LeetCode-style coding problems, which test data structures and algorithms (DSA) fundamentals under tight time constraints. Success in this round is crucial for moving forward in the interview process.
The interview loop generally includes multiple coding rounds focused on DSA problems, often requiring candidates to solve problems with follow-up questions that test their problem-solving depth and speed. Candidates noted that performance under time pressure is a significant factor in these rounds.
Candidates can expect one or more system design interviews, which may include low-level design (LLD) and high-level design (HLD) questions. These rounds assess the candidate's ability to translate coding skills into coherent design solutions and reasoning about trade-offs.
The interview process typically concludes with behavioral interviews aimed at assessing cultural fit and collaboration skills. Candidates should prepare to discuss their past experiences and how they align with Uber's values.
The overall interview process is structured and can span several weeks, often including a mix of coding, design, and behavioral rounds. Candidates noted that the timeline can move quickly, with some receiving offers shortly after completing the final interviews.
Candidates reported that the interview process is challenging, with high expectations for both coding and design tasks. Many felt that the bar was set particularly high for performance, especially in coding and optimization tasks.