← Back to Directory

Waymo interview notes, page 2 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·Onsite - Behavioral / Leadership

Apr 2026
Interviewed at Waymo for what seemed like an engineering manager or people lead role. Just one question shared here but it was the kind that makes you realize how differently you actually treat people on your team versus how you think you treat them.
  • How do you adjust your approach when working with junior versus senior individual contributors on your team?

“I started talking about feedback cadence and quickly realized I was basically describing the same approach for both groups with slightly different vocabulary.”

View Post

Waymo·Machine Learning Engineer·Onsite - System Design / Architecture

Apr 2026
Waymo ML engineer interview with a meaty autonomous vehicle system design question. The whole thing centered on one problem but it branched into a lot of directions fast, way more than I expected from a single prompt.
  • Design an ML system for an autonomous vehicle that selects the best drop-off location near a passenger's destination and plans the maneuver to reach it.

“This question sprawled in every direction.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Apr 2026
Waymo SRE interview with a geometry/interval-tracking coding problem that felt more like a systems puzzle than a typical algo question. Interesting problem but I wasn't sure what they were really testing until I was halfway through.
  • Design a function that takes a stream of real-valued points one at a time and returns whether a fixed segment from 0 to 50 is fully covered. Each incoming point contaminates a unit-wide interval centered on it, contamination is permanent, and you need to handle this efficiently with repeated updates.

“My first instinct was to just track a sorted list of intervals and merge them on each insert, which works but I fumbled explaining the merge logic under pressure.”

View Post

Waymo·Data Scientist·Technical Phone Screen

Apr 2026
Waymo data scientist interview that leaned way harder into probability theory than I expected. The whole session was basically one extended stats problem with a simulation layer bolted on, which was fine until the confidence interval follow-up made me realize I hadn't thought carefully enough about the variance.
  • In a best-of-5 table tennis match where player A wins each game with fixed probability p, derive the probability that the match goes to exactly 5 games.
  • How would you write a Monte Carlo simulation to estimate the probability that a best-of-5 match lasts exactly 5 games?
  • Given M simulated matches, how would you construct a confidence interval for the estimated probability?

“This took me longer to set up than it should have.”

View Post

Waymo·Software Engineer·Hiring Manager Screen

Apr 2026
Hiring manager round at Waymo for a software engineer role. Pretty standard behavioral format covering past projects, ownership, conflict, and motivation, plus time at the end for your own questions. Nothing too surprising but the reverse questions portion felt like it mattered more than usual.
  • Walk me through a past project you're proud of and the role you played in it.
  • Tell me about a time you took ownership of something outside your defined responsibilities.
  • Describe a conflict you had with a teammate or stakeholder and how you resolved it.
  • What motivates you in your work, and why are you interested in this team specifically?
  • What are the team's biggest technical challenges right now?
  • How does the team define success for someone in this role over the first six to twelve months?

“I went with a project that had a messy middle section, which I think was the right call.”

View Post

Waymo·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Waymo for a software engineering role. The whole thing was basically one long question about your career arc plus a deep dive into a past challenge, which sounds manageable until you're actually in it trying to pick the right story on the fly.
  • Walk me through your resume chronologically, covering the scope, your specific contributions, and the impact of each role.
  • Pick a significant challenge from your past, explain what made it hard, what you did, what happened, and how you'd approach it differently now with more experience.

“I prepped this but still rambled too much on my earlier jobs.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Apr 2026
Waymo software engineer interview with a graph shortest-path problem. Pretty classic Dijkstra setup but with multiple targets, which added a small wrinkle. Nothing too wild, but the constraints were large enough that you had to be careful about your implementation.
  • Given a weighted directed graph with n nodes and a list of edges, find the shortest distance from a given source node to each node in a list of target nodes. Return -1 for any target that is unreachable.

“Recognized Dijkstra pretty fast, which was good.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Apr 2026
Waymo SWE interview that didn't go great. Got a LeetCode problem I'd never seen before and it turned out to hinge on bucket sort, which I hadn't really prepped for.
  • Solve a LeetCode problem that requires bucket sort as the key algorithmic technique.

“I fumbled through it.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Apr 2026
Waymo SWE interview with an array problem that sounds trivial until you actually think about the constraints. Single round, coding focused, left me second-guessing my linear scan logic the whole way through.
  • Given an integer array with only the values 0, 1, and 2, find the minimum absolute difference |i - j| across all index pairs where one index holds a 1 and the other holds a 2. Return -1 if no such pair exists. You must solve it in a single linear pass.

“The single-pass constraint is what makes this non-trivial.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Apr 2026
Waymo SWE interview that came down to a DP/greedy problem on alternating subsequence sums. Not the hardest problem on paper but the two-state formulation takes a second to click if you haven't seen it before.
  • Given an integer array, find the maximum alternating subsequence sum, where the alternating sum of a subsequence is defined as the first element minus the second plus the third minus the fourth, and so on.

“Took me longer than I'd like to admit to see why this reduces to two states.”

View Post