Waymo Interview Process & Rounds
Waymo's loop is recruiter contact → a real technical phone screen (60 min live coding — BFS/graph problems and pure-Python data processing are the recurring themes, often with 'no pandas' as an explicit constraint) → a 3–5 round virtual onsite mixing coding, system design, a technical deep dive, and a hiring-manager behavioral. The timeline is fast: candidates report a median of 3 days from phone screen to onsite and about a week from onsite to outcome. System design rounds carry a strong autonomous-vehicle flavor — evaluation systems for self-driving models, simulation logging, ML inference at 100M-DAU scale — and interviewers probe domain specifics like the sim-to-real gap and compute-constrained simulation, so a generic template gets picked apart.
Key facts
- •5 distinct round types
- •28 questions reconstructed from 44 candidate reports
- •Reports span Aug 2025 – Jul 2026
- •Refreshed monthly · last updated August 2026
The Waymo loop, from candidate reports
Waymo's loop is recruiter contact → a real technical phone screen (60 min live coding — BFS/graph problems and pure-Python data processing are the recurring themes, often with 'no pandas' as an explicit constraint) → a 3–5 round virtual onsite mixing coding, system design, a technical deep dive, and a hiring-manager behavioral. The timeline is fast: candidates report a median of 3 days from phone screen to onsite and about a week from onsite to outcome. System design rounds carry a strong autonomous-vehicle flavor — evaluation systems for self-driving models, simulation logging, ML inference at 100M-DAU scale — and interviewers probe domain specifics like the sim-to-real gap and compute-constrained simulation, so a generic template gets picked apart.
What does Waymo ask in each round?
Waymo interviews span 5distinct round types, shown below. Counts reflect distinct questions per round across the loops we’ve indexed.
- •On ML/inference system design: run the back-of-envelope first (QPS → memory → bandwidth → bottleneck) before proposing any optimization — passers structured the numbers up front
- •On open-ended AV design prompts (evaluation systems): anchor the scope fast with a concrete real-world analogy (candidates cited Scale AI / Mercor) and split human-eval vs LLM-eval into distinct subsystems
- •When one round chains multiple design areas (inference serving, model efficiency, kernel-level), keep breadth across all of them rather than going deep on one and running out of time
- •In the hiring-manager round: crisp STAR structure with quantified outcomes and ownership language ('I decided,' 'I designed') — and treat it as a two-way conversation with real questions about the team's roadmap
- •Align behavioral examples with the team's domain (planning, autonomy, simulation) — candidates who did reported better traction
- •Applying a generic system-design template without adapting to self-driving specifics — interviewers pivot to sim-to-real realism and compute constraints, and candidates who can't follow lose the round
- •Not drawing any diagrams on open-ended design rounds, leaving the discussion unstructured
- •Burning the first ~15 minutes of a 45-minute design slot on experience discussion or over-clarification, leaving no time for the actual design
- •Missing numpy/tensor traps in the debug coding round — array aliasing (Matrix.zeros), omitted axis parameters, silent type truncation
- •Giving a team-level project narrative without separating personal contribution, or citing no quantitative results — reported as the differentiator in otherwise-clean loops
FAQ
How many rounds is the Waymo interview?▾
What is the Waymo interview process?▾
How fresh is this Waymo interview data?▾
Get the full Waymo catalog
Every question, every candidate-reported follow-up, and what passers actually do. Monthly refresh.