Waymo AI Research Scientist interview typically runs 4 rounds: 2 coding rounds, 1 ML design round, and 1 ML basics/research round. The process takes about one virtual onsite and is research-heavy, with an informal first chat.
$185K
Avg. Base Comp
$261K
Avg. Total Comp
4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Waymo is looking for researchers who can defend their work, not just describe it. The most revealing pattern is how much time gets spent on papers and prior projects: one interviewer reportedly walked through a candidate’s paper from motivation to implementation details, while another spent the bulk of the conversation on background and published work. That tells us the bar is less about polished talking points and more about whether you can explain why your approach made sense, what tradeoffs you made, and how you would justify those choices under scrutiny.
A second theme is that Waymo seems to value applied mathematical reasoning with an efficiency mindset. The standout coding problem wasn’t a generic algorithm exercise; it centered on a 2D trajectory with time-indexed motion, then quickly escalated into shortest-path geometry and how to reduce computation as the number of segments grows. That combination is telling: they care about candidates who can move from a clean answer to a scalable one without losing the thread. In the ML portion, the questions stayed foundational but were used as a filter for depth, not memorization. We’ve seen that the non-obvious make-or-break factor here is the ability to connect research intuition, geometric problem-solving, and basic ML theory into one coherent technical narrative.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Waymo process.
I went through five interviews for this AI Research Scientist role at Waymo. The process started with an intro call from HR, followed by a hiring manager conversation that was mostly high-level — no coding, just a 30-minute discussion about my AI research projects and whether I had behavior modeling experience. That set the tone for what felt like a heavy emphasis on research background and domain expertise.
The bulk of the process consisted of a mix of coding and ML-focused interviews. One of the most frustrating rounds was a 45-minute coding interview where I tackled a dynamic programming problem. I solved it using a mathematically equivalent approach, but the interviewer insisted I reimplement it to match their specific solution structure — essentially rewriting the recursion to use a list of lists instead of a more elegant caching approach. They wouldn't accept my lru_cache optimization or let me refactor it into a simpler form. That rigidity around implementation style was surprising and added real tension to an already tense technical discussion.
Beyond the DP problem, I was asked about zero-shot learning, ML fundamentals more broadly, and attention mechanisms — specifically KV caching implementation, which required both mathematical understanding and coding ability. There was also a research presentation component where I walked through my own work. The whole thing stretched over four months with slow communication from HR between rounds, which added to the overall fatigue.
I didn't get an offer. Looking back, they seemed to want very specific implementation choices on algorithmic problems, even when the core logic was sound, and they weighted both deep ML knowledge and strict coding style heavily. It's a rigorous process, but the inflexibility on how solutions had to be structured stood out as the hardest part to navigate.
Prep tip from this candidate
Prepare for dynamic programming problems with a focus on their exact implementation style — be ready to rewrite solutions multiple ways even if your approach is mathematically correct. Also brush up on attention mechanisms with KV caching and be prepared to implement ML algorithms from scratch, not just explain them.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Waymo
Write a function to return the value of the nearest node that is a parent to both nodes.
| Question | |
|---|---|
| Car Recommendation Architecture | |
| Location Frequency | |
| Pathfinder in Maze | |
| Minimum Days for Scheduling All Meetings | |
| Shortest Path Algorithms | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Experiment Validity | |
| Merge Sorted Lists | |
| Normal Distribution Sample | |
| First to Six | |
| Fair Coin | |
| Button AB Test | |
| P-value to a Layman | |
| Get Top N Frequent Words | |
| String Shift | |
| 500 Cards | |
| Find Bigrams | |
| Friendship Timeline | |
| Weighted Keys | |
| Youtube Recommendations | |
| N-gram Dictionary | |
| Network Experiment Design | |
| Raining in Seattle | |
| Assumptions of Linear Regression | |
| Reducing Error Margin | |
| Hurdles In Data Projects | |
| Type-ahead Search | |
| Pre-Launching Shows |
Synthesized from candidate reports. Individual experiences may vary.
The first conversation felt like an informal discussion with a research scientist rather than a strict screen. The interviewer introduced the team’s work and Waymo’s broader research direction, then spent most of the time asking about the candidate’s background and papers.
This round focused on a geometry and efficiency problem involving a 2D trajectory represented by (x, y, t) tuples with monotonically increasing time. The candidate first had to return the coordinates at a given time, then extend the solution to find the shortest path from an arbitrary point to the trajectory and discuss how to reduce computation cost for many segments.
This round was part of the virtual onsite and was described as one of the more serious interviews. It likely centered on machine learning system or research design, though the experience specifically emphasized that the overall onsite included an ML design round.
The interviewer spent about half the time digging into the candidate’s paper, from motivation and high-level ideas down to implementation details. The other half covered ML fundamentals such as dropout, training versus testing behavior, overfitting and underfitting, and possibly an ensemble-related question.
