Real, anonymous reports from people who interviewed for Software Engineer at Uber, newest first and distilled into what to expect across the loop.
I completed an interview loop for an SDE2 backend role at Uber India and went into the process expecting the recruiter to wrap it up with a debrief decision. After the loop finished, I was informed that the role I’d been interviewing for was closed and that there weren’t any other openings available at the moment.
My process started after I applied—within about a month I got an OA link. I completed it and then moved to an interview that immediately combined a coding problem with system design, plus behavioral questions at the start. The mix felt intense, and overall it was pretty hard.
The interview process typically begins with a recruiter screen, followed by an online assessment (OA) and multiple coding and design rounds, often culminating in a behavioral interview. The overall timeline can span from a few weeks to a couple of months, with varying degrees of communication throughout.
Candidates can expect a mix of LeetCode-style coding problems that focus on data structures and algorithms (DSA), with an emphasis on problem-solving speed and accuracy. The difficulty of these problems can range from medium to hard, and candidates should be prepared for tight timing and edge case considerations.
Interviews often include system design components, such as low-level design (LLD) and high-level design (HLD) discussions, where candidates must demonstrate their ability to think critically about architecture and trade-offs. These rounds require candidates to articulate their reasoning and approach clearly.
Behavioral rounds typically focus on assessing cultural fit and past experiences, often using structured questions to evaluate candidates' problem-solving approaches and teamwork. Candidates should prepare to discuss their previous projects and how they align with Uber's values.
The overall difficulty of the interview process is noted to be high, with candidates feeling challenged by the technical depth and breadth required across rounds. Many candidates reported feeling that their performance did not always align with the final outcomes, leading to mixed feelings about the process.
Candidates often wish they had focused more on specific areas like system design and the integration of coding with design discussions. Practicing under timed conditions and familiarizing themselves with the types of questions asked can help improve performance.