Real, anonymous reports from people who interviewed for Software Engineer at Waymo, newest first and distilled into what to expect across the loop.
My journey started with a recruiter touchpoint, and then the first real interview felt unexpectedly different from what I was bracing for. I went into a technical round expecting a standard SWE-style coding problem, but I got an ML-related question almost immediately. I remember being caught off guard and not finishing in the way they seemed to want—there was an expectation to get to a completed or at least substantially complete solution rather than spending too long clarifying.
I had a pretty smooth early process that leaned heavily on fit and role alignment. My first conversations focused on the responsibilities and what I’d be expected to know, and I remember feeling like the interviewer understood what I brought to the table. The technical demand still showed up, but it felt more “measured” than chaotic—like they were trying to gauge whether I could operate in their environment.
The interview process typically begins with a recruiter call that focuses on the candidate's background and role alignment, often leading to a clear explanation of the next steps. However, experiences vary, with some candidates reporting delays or lack of communication from the recruiting team.
Candidates can expect multiple coding interviews that emphasize algorithmic fundamentals and core programming skills, often using languages like C++ or JavaScript. The focus is on writing clean, correct code under time pressure, with an emphasis on edge cases and problem-solving depth.
Interviews often include questions related to machine learning, simulation, and physics, requiring candidates to demonstrate their understanding of ML concepts and their application in real-world scenarios. This aspect can be challenging for those less familiar with ML fundamentals.
The interview process is generally structured with back-to-back technical discussions, but some candidates reported logistical issues and disorganization that affected their performance. The pace can be rapid, leaving little time to recover between rounds.
While technical skills are heavily emphasized, some rounds also assess cultural fit and behavioral aspects, though the focus on these can vary. Candidates should be prepared to discuss their past experiences and how they align with the company's values.
Candidates often express a desire for clearer feedback after interviews, as many leave without understanding what went wrong or how they might improve. The overall outcome can feel confusing, especially if candidates felt they performed well in technical rounds.
