← Back to Directory

Waymo interview notes, page 7 of 9

Large Enterprises

Most of these Waymo write-ups come from Software Engineers (46), then Machine Learning Engineers (23) and Data Scientists (10). The most reported rounds are the technical phone screen (58), the system design round (11), the behavioral / leadership round (6) and the hiring manager screen (4).

87 interview notes · updated Jul 2026

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo coding interview for a software engineer role, one algorithmic problem that looks straightforward until you read the O(n) constraint and realize sorting is off the table. The bucket approach isn't something most people reach for instinctively so it's worth knowing cold before you walk in.
  • Given an unsorted array of integers, find the largest gap between any two adjacent elements once the array is sorted. Must run in linear time without using a comparison-based sort.

“The problem reads like a basic sorting exercise until you hit the time complexity requirement.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo coding interview that started with a classic knight moves problem but pushed into the infinite board variant, which is where things got genuinely interesting. The bounded version felt manageable but the follow-up exposed some gaps in how I think about BFS on unbounded graphs.
  • On an infinite chessboard, a knight starts at (0, 0). Given a target coordinate (x, y), find the minimum number of moves for the knight to reach it.

“I jumped straight to BFS and it worked fine for small inputs.”

View Post

Waymo·Data Scientist·Technical Phone Screen

Jun 2026
Waymo data scientist interview with a pretty intense stats/ML evaluation question focused on rare-event detection. The whole thing was essentially one big case study about model comparison under class imbalance, which I was not fully prepared for.
  • When comparing two models for rare-event detection (like fraud or medical adverse events), which metrics would you use and why is accuracy or ROC-AUC not sufficient on its own?
  • How would you compare two models statistically when the number of positive examples is small? Walk through the distributions, confidence interval construction, and how you'd test for a significant difference.
  • If you only have a handful of aggregated numbers to work with (small sample, limited data), how do you make a responsible model selection decision? Consider threshold choice, calibration quality, and alert-budget constraints.

“I knew accuracy was wrong immediately because of class imbalance, said so right away.”

View Post

Waymo·Data Analyst·Technical Phone Screen

Jun 2026
Waymo data analyst interview with a SQL question that looked clean on the surface but had a few gotchas buried in the requirements. Single technical question, no behavioral stuff from what I could tell.
  • You have an autonomous vehicle fleet database with models, vehicles, trips, and maintenance records. Write a production-ready SQL query that returns the top 5 most efficient vehicle models by miles per kWh, but only for models whose total maintenance cost is under 5000. Models with no maintenance records count as zero cost and must be included. Models with zero or null total energy consumption should be excluded rather than treated as infinitely efficient.

“The fanout problem is what got me initially.”

View Post

Waymo·Software Engineer·Hiring Manager Screen

Jun 2026
Interviewed at Waymo for what seemed like an engineering manager or senior people manager role. Just the one question I can recall, focused on team performance dynamics. Pretty standard behavioral territory but it's the kind of thing that trips you up if you haven't thought through a real example beforehand.
  • How have you managed varying performance levels among your team members?

“I went straight to a story about a low performer and kind of forgot to mention the high end of the spectrum at all.”

View Post

Waymo·Data Analyst·Technical Phone Screen

Jun 2026
Interviewed at Waymo, got a geo/data problem that felt deceptively simple on the surface. Short round, one question, left feeling like I either nailed it or completely missed the point.
  • How would you calculate the average distance between cities?

“My first instinct was to just say 'sum all pairwise distances and divide' but then I started second-guessing myself on what 'average' even means here.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo software engineering interview with a coding problem centered on run-length encoded strings. Pretty algorithmic, felt like a classic phone screen but with enough depth to keep you on your toes if you only prepped the naive solution.
  • Given a run-length encoded string like 'B1A2E3C1' (which decodes to 'BAAEEEC'), implement a Find(int p) function that returns the character at position p in the decoded string without actually decoding the whole thing. Then discuss both an O(n) and an O(log n) approach, and handle edge cases like p being out of range or counts being multi-digit.

“I started with the linear scan pretty naturally, just walk the pairs and track a running total until you hit the segment containing p.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Phone screen for a software engineer role at Waymo. Hadn't touched leetcode in a while and it showed. The interviewer was pretty understanding about it, which honestly made it worse somehow.
  • Given a binary tree and an array, determine whether the array represents a valid root-to-leaf path in the tree.

“Blanked.”

View Post

Waymo·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Waymo for an ML engineer role, pretty much one question about mentorship and that was the bulk of it.
  • Tell me about a time you mentored other engineers.

“I had a story ready but fumbled the structure a bit.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo coding round with a string decoding problem that's basically a twist on a classic LeetCode problem. Nothing too wild but the nested case tripped me up a bit.
  • Given an encoded string like "abs(cs){3}g", decode it so that substrings inside parentheses are repeated by the number in the following curly braces. Handle nested cases like "a(b(c){2}){2}".

“It's a variant of that string decode problem on LeetCode but with different syntax.”

View Post