# Waymo Machine Learning Engineer Interview Experience

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/experiences/waymo-machine-learning-engineer-interview-a6f409
Source observed: 2026-11-04T23:11:31.606Z
Last checked: 2026-11-04T23:11:31.606+00:00
Indexed: 2026-11-06T05:26:30.005+00:00

---

# Waymo Machine Learning Engineer Interview Experience

We provide this interview experience as part of our [Waymo Machine Learning Engineer Interview Guide](https://www.aced.io/guides/waymo-machine-learning-engineer-interview). Aced is formerly Exponent. The guide includes an [expert guide](https://www.aced.io/guides/waymo-machine-learning-engineer-interview), [interview experiences](https://www.aced.io/guides/waymo-machine-learning-engineer-interview/experiences), [questions](https://www.aced.io/guides/waymo-machine-learning-engineer-interview/questions), and [resumes](https://www.aced.io/guides/waymo-machine-learning-engineer-interview/resumes).

![Waymo logo](https://exponent-static.s3.amazonaws.com/company_logos/waymo.png)

**Company:** Waymo  
**Role and level:** Staff / L6  
**Location:** United States  
**Verification:** Verified  
**Result:** Got offer  
**Interview date:** A year ago  
**Interview timespan:** 2 months  
**Difficulty:** Difficult  
**Experience submitted:** 7 months ago  
**Guide updated:** A month ago by Waymo candidates

## Candidate overview

> I was definitely caught off guard because I was expecting more of a LeetCode type of question, and instead they showed a diagram about obstacles colliding and wanted me to figure out which one was bigger and where the force would move.

## Interview process

The candidate applied directly on Waymo's website without a referral and described the process as fairly Google-like:

1. Recruiter chat.
2. A surprisingly hard LeetCode-style coding screen.
3. A final loop containing:
   - Another coding round.
   - An ML coding round.
   - An ML system design round.
   - Two behavioral rounds.

The coding bar felt essentially software-engineer level rather than a reduced machine-learning-engineer bar, while the process also required solid machine-learning depth. The unusual final coding interview was practical and diagram-based rather than a conventional coding exercise. The behavioral rounds examined the technical details of the candidate's projects more deeply than at most companies. The candidate's advice is not to under-prepare data structures and algorithms simply because the role title includes machine learning.

The main process stages are:

- Recruiter screen
- Technical interview
- Final round

## Interview rounds

The experience is labeled as **9 questions across 7 rounds**.

### Recruiter screen

**Question count:** 1  
**Question type:** [Behavioral](https://www.aced.io/questions?type=behavioral)

The recruiter conversation was described as standard. A later preparation call covered the full loop and explained that senior and staff candidates use the same process, with leveling decided at the end.

**Question asked:**

> Can you walk me through what you're doing now, what you've done before, and why you're interested in Waymo?

The candidate treated this as a basic get-to-know-you call and focused on clearly explaining current work, previous work, and interest in Waymo. It did not feel like a substantive evaluation round to the candidate.

### Technical interview

The technical interview lasted **45 minutes** with a senior interviewer. It primarily used open-ended questions, included a short follow-up near the end, and involved substantial pushback on tradeoffs.

**Question asked:**

> How would you improve a product you use every day for a new market?

The candidate selected a segment first, sized the opportunity, compared three options, and then chose one option and its success metric.

### Final round (1)

The supplied experience records the same format and question for this round: **45 minutes** with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and considerable discussion of tradeoffs.

**Question asked:**

> How would you improve a product you use every day for a new market?

The candidate selected a segment first, sized it, compared three options, and chose one option and its success metric.

### Final round (2)

The supplied experience records **45 minutes** with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and pushback on tradeoffs.

**Question asked:**

> How would you improve a product you use every day for a new market?

The candidate selected a segment first, sized it, compared three options, and chose one option and its success metric.

### Final round (3)

The supplied experience records **45 minutes** with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and pushback on tradeoffs.

**Question asked:**

> How would you improve a product you use every day for a new market?

The candidate selected a segment first, sized it, compared three options, and chose one option and its success metric.

### Final round (4)

The supplied experience records **45 minutes** with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and pushback on tradeoffs.

**Question asked:**

> How would you improve a product you use every day for a new market?

The candidate selected a segment first, sized it, compared three options, and chose one option and its success metric.

### Final round (5)

The supplied experience records **45 minutes** with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and pushback on tradeoffs.

**Question asked:**

> How would you improve a product you use every day for a new market?

The candidate selected a segment first, sized it, compared three options, and chose one option and its success metric.

The experience also repeats this product-improvement question and response three additional times in the supplied content.

## Interview tips

Practice answers aloud with a timer, keep a framework ready for every round, and ask the recruiter what each interviewer will focus on so you can tailor your examples.

## Company culture observations

The candidate described interviewers as collaborative and said they repeatedly steered the discussion toward the user. The team appeared to value structured thinking over polish, and each interviewer left time for questions at the end.

## Access and practice

The public preview includes the recruiter screen and selected round details. We invite you to [become a member](https://www.aced.io/upgrade?src=experience) to read the rest of this interview and new experiences added weekly. You can also [share your experience](https://www.aced.io/questions/contribute?src=experience). A **24-hour trial starts once your submission is approved**.

You can [practice this loop](https://www.aced.io/questions/6390/design-organizational-hierarchy-direct-reports?interview=waymo-machine-learning-engineer-interview-a6f409).

[Back to all experiences](https://www.aced.io/guides/waymo-machine-learning-engineer-interview/experiences)

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fwaymo-machine-learning-engineer-interview-a6f409&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fwaymo-machine-learning-engineer-interview-a6f409). Opening a form does not execute a tool.