Waymo Software Engineer Interview Guide

The short answer: Waymo says its process starts with a recruiter screen, then one or two phone or video interviews with peers or a manager, then a virtual onsite of up to five interviews of about 45 minutes each with potential teammates and cross-functional partners. Some roles also include a coding or technical assessment. Waymo allows no AI assistance in live interviews and none on assessments unless the instructions permit it. Candidate guides describe a hiring committee review before the offer. Last reviewed October 2026.

Waymo software engineer interview: quick answers

The Waymo software engineer role

What Waymo engineers work on, the skills its job postings ask for, and what a normal week looks like.

Waymo software engineer levels and pay

Your level sets the bar you are interviewed against and the pay band of the offer.

Waymo postings never state a level, so the rows below use posting titles. Level names such as L3 to L8 come only from third-party salary data, and Waymo does not publish how they map to titles.

Pay in Waymo's US job postings

Waymo's US postings give the expected base salary range across US locations, and say the role is eligible for Waymo's discretionary annual bonus program and equity incentive plan.

Waymo postings never state a level, so rows use posting titles. Titles do not always match the band: a Senior Fullstack posting sits in the same band as Software Engineer postings, while the Onboard Developer Platform posting, with no Senior in its title, sits in a senior band. Rows that combine postings share the same range. Ranges seen October 27, 2026.

Waymo software engineer interview process

The steps below follow Waymo's How We Hire page. The software engineer details inside each step, and the hiring committee, come from candidate guides and are labeled that way.

Based on Waymo's own pages and candidate reports.

Waymo publishes no timeline. Candidate guides report 4 to 8 weeks from application to offer, limited feedback, and decisions that are effectively pass or fail. One guide says senior and staff candidates sit the same loop and the level is set afterwards. Last reviewed October 2026.

What is different at Waymo

• Waymo publishes an AI rule. No AI in live interviews, none on assessments unless the instructions permit it, and AI only to polish the wording of your resume. Waymo says it uses Gemini and other AI tools internally but wants to see how you think in real time.
• The onsite is virtual. Waymo says it runs up to five interviews of about 45 minutes, and interviewers can include cross-functional partners as well as engineers.
• Coding problems often look like driving problems. Candidate guides report more geometry than usual, such as grid graphs, bounding boxes and collision checks over time.
• Correctness beats speed. Candidate guides say a safety-critical mindset is probed throughout and edge-case handling is weighted above raw speed.
• Modern C++ matters for onboard roles. Vehicle platform postings ask for C++17 or C++20, and one says the role is for C++ 'and not for C/C++'.
• The loop follows the Alphabet pattern. Candidate guides describe a Google-style hiring committee, and some postings prefer familiarity with Google infrastructure such as Flume, Borg and Protocol Buffers.

Waymo software engineer interview questions

Coding problems from our bank tagged to Waymo, then design, fundamentals and behavioral prompts we wrote for this guide.

1from typing import Optional, Tuple
2
3Box = Tuple[float, float, float, float, float, float]
4
5def first_contact(a: Box, b: Box, horizon: float) -> Optional[float]:
6    """Return the earliest time in [0, horizon] the boxes overlap, or None."""
7    pass

1from typing import Optional, Tuple
2
3Box = Tuple[float, float, float, float, float, float]
4
5def first_contact(a: Box, b: Box, horizon: float) -> Optional[float]:
6    if horizon < 0:
7        raise ValueError("horizon must be non-negative")
8    for box in (a, b):
9        if box[0] > box[2] or box[1] > box[3]:
10            raise ValueError("min must not exceed max")
11    lo, hi = 0.0, float(horizon)
12    for axis in (0, 1):
13        a_min, a_max, va = a[axis], a[axis + 2], a[axis + 4]
14        b_min, b_max, vb = b[axis], b[axis + 2], b[axis + 4]
15        d = va - vb
16        # Overlap on this axis needs both c + s * t <= 0 conditions to hold.
17        for c, s in ((a_min - b_max, d), (b_min - a_max, -d)):
18            if s == 0:
19                if c > 0:
20                    return None  # separated forever on this axis
21            elif s > 0:
22                hi = min(hi, -c / s)
23            else:
24                lo = max(lo, -c / s)
25    return lo if lo <= hi else None
26
27# Complexity: O(1) time and space.

How to prepare

A plan for the Waymo loop, most important first:

1. Practice coding for correctness first: restate the problem, ask clarifying questions, give an initial solution, then improve it and say how you would test it.
2. Practice geometry and grid problems framed as driving tasks, such as bounding boxes, collision checks over time and paths on a grid.
3. Practice system design for simulation, evaluation and ride-hail dispatch, which candidate guides say mid-level and senior loops include.
4. Prepare a deep dive on one past project, including the design decisions you would now change.
5. Prepare stories with ambiguity, prioritization and cross-team alignment, and map them to Waymo's values.
6. Read Waymo's website, blog and team pages, and plan to use no AI tools in interviews or assessments unless told otherwise.

Practice path

Courses that cover the rounds above:

• Data Structures and Algorithms
• System Design
• Modern C++
• SQL