This was for a web-based role.
It started with an introductory call with a recruiter, covering basic behavioral and "why Waymo" style questions.
The next round was a CoderPad interview. This consisted of reviewing a design doc by adding details/leaving comments and working on a small JavaScript codebase to build out a few new features.
I didn’t personally have a phone interview after this.
The final round was an on-site, where I met with four would-be direct teammates. I was given the option to work on the interview questions beforehand, so I did that. During the interviews, we discussed my solutions and made a few changes/extensions to what I had written based on follow-up questions. There were no LeetCode-style questions; all were more web-oriented. All interviewers were kind, and I thought the conversations were enjoyable.
Overall, I thought the interview process itself was great, but I was ghosted by my recruiter after the on-site. It’s a simple courtesy to let a candidate know one way or another, especially after they’ve spent hours going through the interview process. It was a huge letdown to see Waymo represented as such. I followed up with my recruiter, including letting them know I had competing offers, but still never got a response. Very disappointing.
Web development oriented questions:
The following metrics were computed from 2 interview experiences for the Waymo Software Engineer role in San Francisco, California.
Waymo's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Waymo's Software Engineer interview process in San Francisco, California.