Waymo Data Scientist interview typically runs 5 rounds: recruiter screen, technical assessment, and 4 onsite rounds. It usually takes about 2-4 weeks and is highly role-specific, with a smooth, professional process.
$188K
Avg. Base Comp
$278K
Avg. Total Comp
4-5
Typical Rounds
3-5 weeks
Process Length
We've seen Waymo lean hard into real-world simulation and evaluation thinking rather than abstract interview puzzles. Multiple candidates reported that the questions were tightly tied to the team’s actual work, especially around scenario creation, dataset-driven problem solving, and how to reason about product or model behavior from imperfect data. That means the strongest signal here is not just whether you know the right terminology, but whether you can connect methods to a concrete autonomous-driving problem and explain why your approach fits the data you have.
A recurring theme is how much weight Waymo places on statistics and experimentation judgment. One candidate said the majority of the discussion centered on statistical tests, including assumptions and when to use each method, while another called out long-tail distributions, data imbalance, and evaluation tradeoffs. We also noticed a very practical streak in the technical bar: implementation details like sampling 3D bounding boxes in numpy, dynamic programming, and a quick transformer check all showed up in the same process. In other words, Waymo seems to value candidates who can move fluidly between theory and code, especially when the problem is grounded in simulation, metrics, or model evaluation.
The non-obvious make-or-break factor is comfort with ambiguity in a domain-specific setting. Our candidates report open-ended discussions about building features, plus questions that asked them to reason from a dataset alone, which suggests the interviewers are looking for people who can structure messy problems without overfitting to textbook answers. Strong candidates here tend to sound like product-minded scientists: precise about assumptions, careful about failure modes, and able to justify decisions in the context of autonomous systems rather than generic ML.
Synthetized from 2 candidates reports 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.
The process was pretty smooth and professional overall. It started with a recruiter screen, and after that I went into a loop that was about 45 minutes per interview with the hiring manager, an engineering manager, and data science partners. Everyone I spoke with was nice and informative, and the questions felt very tied to the role rather than generic interview trivia. I interviewed for a simulation team focused on scenario creation, so a lot of the discussion was about how I would think through real product and data problems in that space.
The first technical round I had was a programming interview, and it leaned heavily on dynamic programming. I was able to solve the question, but that still wasn’t enough to move forward in my case. Another round was more applied: they gave me a dataset and asked me to come up with a way to resolve a problem using only that data, which felt like a practical case study rather than a textbook exercise. I also had a round with some ML fundamentals, including a quick check on how a transformer works, plus questions about handling long-tail distributions and data imbalance. One of the more unusual things was being asked to sample 3D bounding boxes of different orientations in numpy, which was very specific and definitely tested comfort with implementation details. There was also a behavioral question about why I wanted to work at Waymo, and in the HM-style discussion I was asked to think through building a feature for creators, which was more open-ended and product-oriented. I didn’t get the offer, and my main takeaway was that strong stats/ML intuition and comfort with practical coding both seem important here.
Prep tip from this candidate
Be ready for a dynamic programming coding round, plus applied ML questions on transformers, long-tail imbalance, and working directly from a dataset to propose a solution. It would also help to practice numpy-style implementation questions like sampling 3D bounding boxes with different orientations.
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
Design an end-to-end ML system for personalized car recommendations at Cars.com, supporting real-time and batch inference, data distribution shift detection, and CI/CD for frequent model updates.
| Question | |
|---|---|
| Pathfinder in Maze | |
| Shortest Path Algorithms | |
| Statistically Significant Test | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| First Touch Attribution | |
| First to Six | |
| Merge Sorted Lists | |
| Experiment Validity | |
| String Shift | |
| 500 Cards | |
| Last Transaction | |
| Button AB Test | |
| Raining in Seattle | |
| Top 3 Users | |
| Job Recommendation | |
| Impression Reach | |
| Minimum Change | |
| Jars and Coins | |
| Lazy Raters | |
| WAU vs Open Rates | |
| Network Experiment Design | |
| Bucket Test Scores | |
| Complete Addresses | |
| Delivery Estimate Model | |
| Random Bucketing | |
| Find Bigrams | |
| RMS Error |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with a recruiter screen to discuss your background, interest in Waymo, and fit for the Data Scientist role. Candidates reported this as a smooth and professional first step.
Candidates then complete a technical assessment focused on practical problem-solving. In the experiences shared, this included applied data work, statistics and experimentation, and solving a problem using only the provided dataset.
The main interview loop consists of about four 45-minute rounds with the hiring manager, an engineering manager, and data science partners. Rounds are highly role-specific and can include programming with dynamic programming, ML fundamentals, statistical tests and experimentation, long-tail and imbalance handling, and implementation exercises such as sampling 3D bounding boxes in numpy.
One of the rounds is a more open-ended discussion with the hiring manager about how you would think through product and data problems. Candidates described questions about building features and explaining why they want to work at Waymo, with an emphasis on simulation, scenario creation, and real-world decision making.