Real, anonymous reports from people who interviewed for Software Engineer at Uber Drivers, newest first and distilled into what to expect across the loop.
I went through an online coding exam. The questions were medium to hard LeetCode-style, and the format was very time-boxed: 45 minutes for each question, with three questions total. It felt like a real test of both DSA fluency and time management.
I did essentially the full process and ended up not passing. The timeline stretched to almost a month, which felt reasonably fast to me even though it was definitely challenging.
The interview process typically begins with a recruiter screen focused on assessing background, experience, and fit for the role, which is crucial for moving forward in the process.
Candidates can expect multiple coding assessments, often using platforms like HackerRank, with a focus on data structures and algorithms (DSA), where problems can range from medium to hard difficulty and may include follow-up questions to deepen the evaluation.
The onsite loop generally includes several technical interviews that cover coding, system design, and sometimes low-level design, requiring candidates to articulate their thought processes and architectural decisions clearly.
Behavioral interviews are integrated into the process, focusing on cultural fit, teamwork, and decision-making, which are evaluated alongside technical skills to gauge overall candidate suitability.
The overall interview structure is typically well-organized, with a timeline that can stretch over several weeks, including multiple rounds of interviews that can feel intense due to their back-to-back nature.
Candidates often reflect on the need for clarity in communication and the importance of demonstrating a strong understanding of both coding and system design concepts, as well as managing performance throughout the process.