Waymo Interview Questions: Complete 2026 Guide to a LeetCode Myth

12 min read

If you’re researching Waymo interview questions before an application, a recruiter call, or an onsite loop, the most-read prep guides agree on one thing: expect coding problems reframed around self-driving cars, not plain algorithm drills. Real candidate reports filed between 2022 and August 2026 describe something else almost every time.

This guide separates the two. It walks through what prep sites claim about Waymo’s coding rounds, lines that up against dated, attributed reports from Glassdoor, Blind and 1point3acres, and lays out the stage-by-stage process candidates actually describe — including the one place the self-driving framing genuinely does show up. If you only take one thing from this page before you search any more Waymo interview questions, make it the table halfway down.

The Claim Every Waymo Prep Guide Makes

Search “waymo interview questions” and the pattern repeats across guide after guide: Waymo’s coding rounds aren’t generic LeetCode, they’re LeetCode wearing an autonomous-vehicle costume. One widely read guide puts it directly — instead of a plain sliding-window question, it says, “you might be asked to compute a moving average of sensor data points to smooth a vehicle trajectory.” Another guide, built from an anonymous “recent Waymo hire,” describes a coding round built around a VehicleTracker class handling live GPS updates, and a second round asking candidates whether diagrammed obstacles will collide.

Both examples are plausible-sounding, and neither is a verified, quoted candidate report. The first is explicitly framed by its own guide as an illustration — “instead of X, you might be asked Y” — not a documented question. The second is attributed to one unnamed source and never quoted from directly. Treat both as guide-constructed illustrations of a theory, not documented history, because the documented history looks different.

What Candidates Actually Report Being Asked

Set the guide claims aside for a moment and look only at dated, attributed Waymo interview questions from people who actually sat in the room. Cross-checking six Glassdoor role pages — Software Engineer, Senior Software Engineer, Staff Software Engineer, Software Engineering Intern, Developer, and the general company page — plus two Blind threads and 1point3acres’ Waymo interview log turns up a consistent pattern: most reported coding questions carry no autonomous-vehicle framing at all.

The Standard Software Engineer Screen Is Usually Plain LeetCode

Four separate Software Engineer candidates, spanning three years, describe generic algorithmic prompts with no vehicle, sensor, or trajectory framing attached:

“2D prefix sum screen, skip manager behavioral, final panel of hiring manager and system of ai for perception evals” — Software Engineer, Mountain View, CA, 3 Aug 2026 (Glassdoor)

“easy question leetcode questions and other generic questions” — Software Engineer, 11 Jul 2026 (Glassdoor)

“leet code question: greedy algorithm” — Software Engineer, California, MD, 3 Mar 2026 (Glassdoor)

“JavaScript fetch API, best time to buy and sell stocks, and one question based on their business needs” — Software Engineering Intern, 12 Sep 2022 (Glassdoor)

That last one is worth pausing on: “best time to buy and sell stocks” is LeetCode problem #121, one of the most-drilled questions in the entire genre. It’s about as far from a bespoke autonomous-vehicle prompt as a coding question gets, and it’s still what a Waymo candidate reports being asked.

Two dated entries from 1point3acres’ interview log corroborate the pattern with generic-sounding titles rather than vehicle-specific ones: a Software Engineer phone screen logged 18 Jun 2026 as a “Minimax Problem,” and another logged 4 Jun 2026 as “Validate Qualified Forest from Parent-Child Graph” — a tree and graph validation problem, not a sensor or trajectory one.

Senior and Staff Rounds: CoderPad, Android UI, and “Real-World” Framing

Senior and Staff-level reports diverge in an interesting way — not toward AV theming, but toward platform and language specifics the prep guides rarely mention. A Senior Software Engineer (Android) candidate reported on 13 Aug 2026 that the live coding round ran in CoderPad with no IDE autocomplete, and included this prompt:

“Write out all the UI code to represent a screen in an app and all its user interactions.”

A separate Senior Software Engineer candidate (31 Mar 2026, Mountain View) reported a two-question coding round with this data-structure prompt, quoted as written:

“Given a variable Page, which contains a list of words, a variable Book, which contains a list of pages, and a variable SynonymGroup containing groups of words…Write a function Print(string data), data is in Book, that output the page index and word index (in SynonymGroup) of data.”

Another Senior Software Engineer report (15 Jun 2026) says the coding problems felt like “real-world application scenarios” rather than LeetCode-style — the closest any Glassdoor report comes to matching the prep-guide narrative, and even this one describes an emphasis on trade-off discussion rather than an autonomous-vehicle-specific scenario. A Staff Software Engineer report from 2022 (offer declined) summarized the loop more plainly still: “regular algorithms, DS, problem solving, system design and behavioral questions.”

System Design Is Big Tech, With Exactly One AV Twist

The single clearest data point on this whole question comes from a Blind thread on Waymo’s system design round. One candidate’s account draws the line precisely: “Situation was AV related but everything else was big tech.” The only autonomous-vehicle-specific element, in that candidate’s words, was “back of the envelope calculation related to data generated by Cam[era]” — a bandwidth-estimation question, not a self-driving-algorithm one.

That one sentence is the most useful thing any candidate has published about how “AV-themed” Waymo’s interviews really are: the autonomous-vehicle framing shows up as a single estimation add-on to an otherwise standard big-tech system design round, not as the round’s premise. A second Blind thread on general interview experience corroborates that middle ground — not LeetCode, but not AV-themed either — describing “a code review, very relieving,” and API- and implementation-focused tasks the candidate called “more applicable than leetcode stuff you’d never use at your job.”

Waymo Interview Questions by Role: What the Record Actually Shows

Laid out side by side, the reports on real Waymo interview questions form a pattern the prep guides don’t: autonomous-vehicle framing correlates with how specialized the role already is, not with the word “Waymo” on the offer letter.

The pattern holds across every reported role: the closer the job title gets to a genuinely specialized technical discipline — quantization, SQL analytics — the more the questions reflect that discipline. The closer it stays to generalist “Software Engineer,” the more the coding round looks like any other big-tech LeetCode screen, self-driving branding notwithstanding.

Why the AV-Themed Story Persists

It’s worth asking why so many pages of Waymo interview questions lean on the same self-driving framing when the candidate record barely supports it. None of this is a knock on the guides for making it up out of nothing — Waymo’s entire public identity is autonomous driving, so a coding round with sensor data or vehicle trajectories in it is an easy story to believe and an easy one to write. It’s a better pitch than “it’s mostly a normal big-tech LeetCode screen,” even where the second version is what the dated reports actually support.

The risk for a candidate is spending prep time drilling imagined vehicle-trajectory or GPS-tracking problems that no report in this research documents, instead of the plain array, string, and graph fundamentals that Waymo’s own candidates say they were actually asked.

It’s a similar dynamic to the one behind Tesla’s software engineer interview process — a company whose public identity practically guarantees a themed-question myth, whether or not the candidate record backs it up. Stripe’s interview process runs the same trap in the opposite direction: guides there claim no LeetCode at all, and real reports say otherwise. For more breakdowns built the same way, see our full guide to coding interview questions by company.

The Waymo Interview Process, Stage by Stage

Waymo publishes a general description of its hiring approach on its own careers site, though it doesn’t break down round-by-round content there. Layering candidate reports from Glassdoor, Blind, and independent guides on top of each other, the process behind most Waymo interview questions that Software Engineer candidates describe in 2025–2026 looks like this:

1. Recruiter screen — background, motivation, logistics.
2. Technical phone screen — one live coding round, most often reported in CoderPad or a similar shared editor.
3. Virtual onsite loop — candidates most often report four to six rounds: one to two more coding rounds, a system design round, a behavioral or manager round, and sometimes a dedicated team-specific panel (one report names a “perception” evaluation).
4. Hiring committee and team matching — several candidates report a multi-week gap here; one Staff-level report put the full process at roughly three months end to end.

Two things are worth flagging honestly rather than smoothing over. First, round count varies more than most guides admit — the same “Software Engineer” title produced reports ranging from a single technical screen plus a final panel, up to six distinct onsite rounds. Second, no source in this research — guide or candidate report — names a specific take-home assessment platform for the Software Engineer track: no HackerRank, CodeSignal, or Codility mentioned anywhere. Every documented coding round is described as live.

Waymo Interview Questions to Practice

These are constructed practice exercises written to match the reported format above. They are not real Waymo questions and are not drawn from any candidate account. Use them to rehearse the pattern the real Waymo interview questions above actually describe — a generic algorithm, explained out loud, with edge cases called out — rather than the vehicle-trajectory scenarios the prep guides promise.

Practice 1: Generic Algorithm Under Time Pressure

Given an array of integers, find the length of the longest strictly increasing subsequence. State your approach’s time complexity before coding, then implement it and call out at least one edge case out loud.

def longest_increasing_subsequence(nums):
    if not nums:
        return 0
    tails = []
    for num in nums:
        lo, hi = 0, len(tails)
        while lo < hi:
            mid = (lo + hi) // 2
            if tails[mid] < num:
                lo = mid + 1
            else:
                hi = mid
        if lo == len(tails):
            tails.append(num)
        else:
            tails[lo] = num
    return len(tails)

Practice 2: The One Place AV Framing Shows Up — Back-of-Envelope Estimation

A vehicle's forward-facing cameras each capture 1920x1080 frames at 30 frames per second, uncompressed, at 3 bytes per pixel. If a vehicle carries 8 such cameras, roughly how much raw data does it generate per hour, and how would you reduce that before writing it to disk? This mirrors the one AV-specific element candidates actually report in the system design round: a bandwidth calculation, not a self-driving algorithm.

Practice 3: Behavioral — A Safety-Weighted Trade-off

Describe a time you shipped something you weren't fully confident in because of a deadline. How did you communicate the risk at the time, and what would you do differently at a company where a shipping mistake can have physical safety consequences?

FAQ: Waymo Interview Questions

The Bottom Line on Waymo Interview Questions

Prep for the coding round the way you'd prep for any big-tech Software Engineer screen — arrays, strings, graphs, explained clearly under time pressure — and treat vehicle-trajectory or sensor-stream scenarios as the exception, not the baseline. The dated record behind these Waymo interview questions supports that ordering, even where the most-shared guides suggest the opposite.