Waymo Interview Questions
& Process for Software Engineers

Waymo runs several very different software loops under one roof, and the fastest way to waste a month is to prepare for the wrong one. Perception and ML in C++ and CUDA is almost a different company to interview for than infrastructure, simulation, or full-stack, so confirm your domain at the first recruiter contact. The spine holds across candidate reports: an application, a recruiter screen that routes your domain and level, a technical coding screen, a recruiter prep call, and an onsite with the team where the offer is decided. Waymo lists its open engineering roles on its own careers site.

The center of gravity inherits Google's coding bar, then adds an AV domain layer on top. Waymo is an Alphabet subsidiary spun out of the Google Self-Driving Car Project, so the DS&A bar is Google-grade, but the questions are frequently framed in driving scenarios and the senior loop leans hard on ML and robotics. This is a scaffold placeholder; the full process breakdown is being prepared.

Past the screens the loop turns onto the team you would join. The technical screen comes first, a Google-grade coding round in the language you pick, often framed on a driving scenario rather than an abstract puzzle. Then comes the onsite, roughly five interviews across coding, a design conversation tuned to your domain, a project deep-dive, and a general behavioral round.

The interviews to plan around are those onsite conversations, because that is where the holistic decision is really made. Interviewers press on depth: clean, correct code, a sensible design for your domain, and fundamentals probed until they reach the edge of what you actually understand. This is a placeholder; the worked loop breakdown is being prepared.

The Coding ScreenDS&A

Google-grade data-structures and algorithms, frequently dressed in autonomous-driving scenarios rather than abstract puzzles. Clean, correct, well-reasoned code is the bar.

The OnsiteThe loop

Roughly five interviews across multiple days: more coding, a system or ML design conversation tuned to your domain, a project deep-dive, and a general behavioral round on collaboration and cross-functional work.

The Domain SplitRouting

Perception and ML, planning and behavior, infrastructure and simulation, onboard and embedded, and full-stack and product are near-different interviews. You apply to a named team, and the loop's flavor follows the org.

Waymo's coding surface is Google-grade DS&A, frequently dressed in autonomous-driving scenarios. Expect graphs and grids framed as maps or occupancy scenes, dynamic programming at a standard ceiling, and word problems built on collision physics or trajectory prediction. The ML and perception tracks add their own coding layer.

The real depth on the senior loop sits one layer down, in ML coding and, on the onboard and embedded track, in C++ and real-time behavior. This is a scaffold placeholder; the full coding breakdown, with worked problems, is being prepared.

Get the honest version first: Waymo's design surface is AV-flavored rather than a generic hyperscale-web round. The signature problem is closer to the actual work: petabyte-scale sensor-log ingest, scene retrieval, and the simulation infrastructure the fleet runs on.

So read the round as domain design over distributed scaling for its own sake. This is a placeholder; a worked AV-data design is being prepared.

A Waymo offer is base plus equity plus a bonus, and the equity is where it differs from a Google offer. Waymo pays in its own restricted equity units rather than liquid Alphabet stock, which employees describe as harder to value than public shares. The ladder is a numeric L3–L8 scale. The exact figures live in the offer lesson rather than here.

Waymo uses Alphabet's numeric L-scale for engineering levels. The compensation for each level lives in the offer lesson.

This is a scaffold placeholder; the offer and negotiation breakdown, with the equity mechanics and the levers that actually move, is being prepared.