Waymo Machine Learning Engineer interview questions

14 Machine Learning Engineers have shared notes from their Waymo interviews, with the questions they were asked in each round. That is 26% of the 53 Waymo interview notes on Screna AI.

14 Machine Learning Engineer interview notes

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·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·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·Machine Learning Engineer·Recruiter / HR Screen

Jun 2026
Pretty standard recruiter screen for an MLE role at Waymo. Nothing technical, just the usual 'why are you leaving, what do you want, walk me through your background' stuff. Went fine.
  • Why are you looking to leave your current role?
  • What are you looking for in your next position in terms of scope, team size, tech stack, and growth?
  • Walk me through your resume, with a focus on your most relevant experience including any deep learning work.

“Prepared something honest but not too negative about my current situation.”

View Post

Waymo·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Waymo ML engineer interview with a data structures question centered on prefix search. Pretty classic trie problem but they pushed on complexity analysis and wanted a real comparison against naive approaches, so it wasn't just "code it and move on."
  • Given a list of words, design a data structure that efficiently returns all words matching a given prefix. Walk through your implementation, its time complexity, and how it compares to a brute-force approach.

“I went with a trie pretty quickly, which was the right call.”

View Post

Waymo·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jun 2026
Director-level behavioral loop for an MLE role at Waymo. Three questions, all designed to stress-test how you think about trade-offs at scale. Felt more like a leadership screen than a typical ML interview.
  • Tell me about a project where you had to balance high-level strategic vision with day-to-day execution details. How did you stay connected to the details without losing sight of the bigger goal?
  • Walk me through your most impactful project. Cover the problem, your specific role, the key decisions you made, and the outcome.
  • Describe a situation where following a policy (around safety, fairness, or compliance) conflicted with efficiency or hitting a business metric. How did you reason through the trade-off, and what happened?

“This one tripped me up a bit because I kept sliding into pure strategy and the interviewer pulled me back down to specifics twice.”

View Post

Waymo·Machine Learning Engineer·Technical Phone Screen

May 2026
Waymo ML Engineer interview had at least one coding round that went pretty deep on string algorithms. They didn't just want a working solution, they pushed through multiple optimizations and wanted you to actually explain the trade-offs at each step.
  • Find the longest palindromic substring in a given string, and walk through progressively optimized approaches with their trade-offs.

“Started with brute force, which they were fine with as a starting point but clearly expected more.”

View Post

Waymo·Machine Learning Engineer·Technical Phone Screen

May 2026
Waymo ML Engineer interview with a heavy focus on model efficiency and training techniques. The questions leaned pretty deep into the ML fundamentals side, stuff like QAT and contrastive learning that you don't always see covered in generic prep guides. Felt like they actually wanted to see if you'd worked with these things hands-on, not just read about them.
  • How does Quantization-Aware Training work, and what are the trade-offs compared to post-training quantization?
  • Walk me through how knowledge distillation works and when you'd choose it over other model compression techniques.
  • What metrics would you use to evaluate a machine learning model, and how do you decide which ones matter for a given problem?
  • Explain contrastive learning and describe a scenario where you'd apply it.

“This is where I spent most of my mental energy.”

View Post

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

May 2026
Waymo ML Engineer interview with a meaty system design question around autonomous vehicle drop-off logic. Pretty deep technically and covered a lot of ground fast.
  • Design an ML system that selects the best drop-off location for an autonomous vehicle approaching a passenger's destination, and decides how to maneuver to it.

“This one sprawled fast.”

View Post

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

Apr 2026
Waymo ML engineer system design round, focused on building an inference system at massive scale. Pretty intense scope for a single session, lots of back-and-forth on the math.
  • Design an inference system that can serve 100 million daily active users. Walk through your memory and bandwidth estimates, and explain how you'd handle latency and out-of-memory failures.

“This one sprawled fast.”

View Post