← Back to Directory

Waymo

Large Enterprises

Most of these Waymo write-ups come from Software Engineers (38), then Machine Learning Engineers (14) and Mobile Engineers (1). The most reported rounds are the technical phone screen (36), the system design round (7), the hiring manager screen (3) and the behavioral / leadership round (3).

53 interview notes · updated Jun 2026

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo software engineer interview with a tree serialization problem that I just could not crack in time. Left feeling pretty rough about it.
  • Given a syntax tree where each node is either a variable or an operator (plus, minus, multiply, divide), serialize the tree into a string using the minimum number of parentheses.

“Never really practiced this kind of problem and it showed badly.”

View Post

Waymo·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Waymo system design round, one big open-ended question about building an evaluation platform from scratch. Dense problem with a lot of moving parts and I felt like I was constantly choosing which thread to pull on.
  • Design an evaluation platform that supports both human reviewers and LLM-based judges. Your design should cover how tasks get ingested and routed, how you manage a mixed pool of human and automated evaluators, quality control mechanisms like gold tasks and inter-annotator agreement, how you aggregate results into a consensus, throughput and SLA guarantees, cost trade-offs between human and LLM evaluation, and what APIs you expose to customers.

“This is a beast of a question.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo SWE interview with a graph/routing question that felt pretty applied given what the company actually builds. One question, clean setup, but the follow-ups are where things get interesting.
  • You have a graph of map nodes connected by weighted undirected edges representing travel times. Given a source node and a destination node, compute the estimated travel time between them.

“Pretty much a Dijkstra question dressed up in autonomous vehicle clothing.”

View Post

Waymo·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Waymo SWE interview, coding round. One meaty in-place matrix copy problem that seemed straightforward until the overlap case came up and I realized I hadn't thought it through.
  • Given a 2D matrix and two rectangular regions (each defined by a top-left corner, height, and width), copy the source rectangle into the destination rectangle in-place using O(1) extra memory. The rectangles may overlap. How do you handle the iteration order to avoid corrupting source data before it's been read, and what do you do about out-of-bounds destinations?

“My first instinct was just nested loops top-to-bottom, left-to-right and I coded it up pretty confidently.”

View Post

Waymo·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Waymo ML Engineer interview had me coding up logistic regression from scratch using only NumPy, then defending the math and design choices out loud. Pretty rigorous for a coding screen, they clearly wanted to see if you actually understood what's happening under the hood.
  • Implement binary logistic regression from scratch using only NumPy, including forward pass, loss computation, gradient derivation, and a fit method with gradient descent.
  • Add predict_proba and predict methods to your logistic regression class, with a configurable classification threshold.
  • How would you add L2 regularization to your implementation, and what changes does it require in the gradient update?
  • Why do we use cross-entropy loss for classification instead of mean squared error?
  • How does learning rate affect convergence in gradient descent for logistic regression, and what are the failure modes?
  • How would you implement a numerically stable sigmoid function to avoid overflow issues?

“This one took the full session.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo SWE interview that threw a pretty gnarly low-level data structures problem at me. The kind of question where you think you know what they want and then realize halfway through you've been assuming too much.
  • Without using any built-in hash maps, sets, or dictionaries, implement a frozenset-like immutable collection from scratch. It needs to support membership testing, length, iteration, equality comparison, and produce a stable hash. You have to build the underlying hash table yourself using only raw arrays.

“I started with chaining because open addressing felt like more surface area to mess up under pressure.”

View Post

Waymo·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an ML Engineer role at Waymo and got hit with a pretty technical deep-dive on GPU/kernel-level stuff. Not the typical ML theory round I was expecting.
  • How would you approach optimizing a CUDA kernel for better performance?
  • How does memory layout affect kernel performance, and what strategies would you use to optimize it?
  • What is kernel fusion and when would you use it?

“I talked through occupancy, warp divergence, and memory access patterns but felt like I was listing buzzwords more than actually reasoning through a real scenario.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo software engineer interview with a coding problem that looks simple on the surface but bites you if you forget about the negative coefficient case. The two-pointer insight is the whole game here.
  • Given a sorted integer array and three coefficients a, b, c, apply the quadratic function f(x) = a*x^2 + b*x + c to every element and return the results in sorted order.

“My first instinct was to just map and sort, which is O(n log n) and they clearly wanted better.”

View Post

Waymo·Software Engineer·Technical Phone Screen

Jun 2026
Waymo SWE interview with a grid partitioning problem that I fumbled pretty badly in the moment. The concept seemed approachable at first but the randomness constraint completely derailed my BFS approach and I had to look up the right direction afterward.
  • Given a 4-token set and an m×n grid, design an algorithm to randomly populate the grid so that each token occupies exactly m*n/4 cells, each token's region is fully connected (4-directional adjacency), and the entire grid is covered.

“I went straight to BFS and got a working structure on paper, but the randomness part broke everything.”

View Post

Waymo·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Waymo MLE interview that was basically a long open-ended conversation about building a CSV processing pipeline. No right answer, which sounds freeing until you're the one expected to drive the whole thing. Scoping ambiguity was clearly the whole point.
  • You're given a CSV file to process for downstream engineering teams. The downstream task and schema aren't defined yet. How do you approach building this pipeline, and what questions do you ask first?
  • Given a single sample row as a raw string, how would you infer a schema, assign types, and define validation rules from it?
  • How would you handle parsing edge cases in a CSV, things like unusual delimiters, quoting, escaping, and encoding issues?
  • How do you handle schema evolution over time, and what do you do with malformed rows?
  • Walk through your thinking on output format and delivery. When would you choose Parquet over CSV, how would you partition the data, and how do you make the pipeline idempotent?
  • How would you test and monitor this pipeline, and how do you communicate the data contract to teams consuming your output?

“This is the whole interview, basically.”

View Post

Waymo interview FAQ

What rounds are in the Waymo interview?

Candidates most often report a technical phone screen (36 write-ups), a system design round (7), a hiring manager screen (3) and a behavioral / leadership round (3).

What does the Waymo technical phone screen cover?

Across 36 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (46 questions), Technical Trade-offs (42) and System Design (15).

Waymo interview guides by role

38 notes

Waymo Software Engineer interview questions

14 notes

Waymo Machine Learning Engineer interview questions