Waymo hero backdrop - Mountain View, California
LiveRefreshed weekly

The Waymo interview cheat code nobody talks about

57 verified questions from the last 14 days, the same ones Waymo is asking candidates this week. Most applicants never see them.

New questions added every 7 days.

57
Fresh questions
3.2K+
Engineers using this
$315K
Median offer at stake
Scroll
1600 Amphitheatre · Mountain View
The Process

Five rounds, and the people who decide never meet you

01
30 minPhone call

Recruiter screen

Waymo runs Alphabet's process with its own twist. The recruiter decides which specialisation you interview for, and that choice is hard to undo later.

  • Pick your specialisation deliberately.

    Perception, planning, simulation and infrastructure run different loops with different bars. The recruiter writes yours down on this call.

  • Say whether you want the car or the cloud.

    Half of Waymo engineering never touches a vehicle. The onboard and offboard sides are separate careers with separate panels.

  • Ask which level the role is mapped to.

    Waymo uses Alphabet's L3 to L7 ladder, so the level named on this call sets the band before you have written a line of code.

02
45 to 60 minShared doc

Technical phone screen

One or two problems typed into a plain shared document with no editor, no autocomplete and no run button. Waymo kept that part of the Google process exactly as it was.

  • Practise without a compiler.

    Syntax errors you would normally never notice become visible here, and interviewers do count them.

  • Say the complexity before you type.

    The screen is short. Stating the approach and its cost first is what leaves you room to finish the code.

  • Expect one question about physical reality.

    Sensor rates, timestamps and dropped frames turn up even in a generic coding screen, because that is the data everyone works on.

03
4 to 5 roundsOne dayVirtual

The onsite loop

Two coding rounds, one domain round on the area you were slotted into, one design round, and a general round on how you work. The domain round separates candidates.

  • Bring safety into the design round unprompted.

    Every Waymo system has a failure mode that ends with a vehicle doing something. Say what happens when your component stops responding.

  • Know how your work gets validated.

    Simulation, structured testing and public road miles are the three levers. Saying which one you would use, and why, reads as senior.

  • Numbers, not adjectives.

    Latency budgets, sensor rates, miles between events. Waymo engineers argue with figures and expect the same back.

04
1 to 2 weeksPacket reviewNo candidate input

Hiring committee

Your interviewers do not decide. Written feedback is assembled into a packet and read by a committee of engineers who never met you, exactly as at Google.

  • Your write ups are the only evidence.

    Anything you said that the interviewer did not record does not exist. Repeat your key point at the end of each round.

  • An even loop beats a spiky one.

    One outstanding round next to one weak one usually stalls the packet, because the committee is looking for consistency.

  • A missing signal is not neutral.

    If nobody scored your design ability, the committee tends to ask for another round rather than decide without it.

05
1 to 3 weeksThen comp review

Team match and offer

Approval and team matching happen after the committee, and the pay review is separate again. The grant is Alphabet stock, so the equity number is a public share price rather than an internal one.

  • Team match can add weeks.

    Passing the committee is not an offer. You still have to be wanted by a specific team with a specific opening.

  • Check what the units actually are.

    They are Alphabet GOOGL units with a public daily price. There is no funding round valuation to ask about, no strike price and no liquidity tied cliff.

  • The bonus is a target, not a promise.

    Alphabet style annual bonuses move with company and individual performance, so treat the headline total as a range.

Levels and Pay

Most of the offer is Alphabet stock with a public price

Pick a level to see how the package splits, what changes by city, and what the loop actually asks of you at that band.

LevelExperienceTotal comp
Software Engineer IIL3Entry0 to 2 yrs~$235K
Software Engineer IIIL4Mid2 to 5 yrs~$315K
Senior EngineerL5Senior5 to 9 yrs~$420K
Staff EngineerL6Staff9 to 13 yrs~$575K
Senior StaffL7Sr Staff13+ yrs~$775K

Waymo pays one national band. The same Software Engineer, Driving Behaviors requisition is listed for Mountain View, San Francisco and New York at a single range of $175,000 to $215,000, so these tabs are here to show you the number does not move, not to move it.

Live Question Feed

What Waymo is asking right now

57 questions · new ones added every 7 days
57 Verified
CODING

Given timestamped sensor frames arriving out of order, emit them in order with a bounded delay and drop anything too late.

Technical phone screen
60 min
Shared doc
Reported 5 times
Open
56 more questions available

The exact questions Waymo is asking this week, tagged by round and difficulty.

Unlock All 57 Questions

Each question stays in the bank for 14 days, so everything here was asked in the last 14 days. Candidates who see them first pass at 3.2 times the normal rate.

Get Full Access
The Unfair Advantage

Why this actually works

01

Real questions, not guesses

Collected from engineers who sat the loop, then cross validated against other intel sources.

02

Fresh every week

The database updates every 7 days, so you never study stale problems.

03

Covers every round

Coding screens, domain rounds, system design, the general round and the hiring committee packet.

04

120+ companies tracked

Also interviewing at Google, Uber or Anduril? We have their questions too.

05

Difficulty and pattern data

Tagged by difficulty, round and category, so you know where prep time goes.

06

Candidate verified only

Reported by a candidate, then cross verified against multiple data points.

3.2×
Higher pass rate
120+
Companies tracked
3.2K+
Engineers using this
FAQ

Common questions

Directly from engineers who interviewed at Waymo, then cross validated against other intel sources into a stack ranked list.

We add new questions every 7 days and retire each one after 14 days, so the bank turns over twice in the window it covers.

Yes, at Google's bar and in a plain shared document. Graphs, grids, heaps and intervals dominate, and the domain round is layered on top rather than replacing them.

Not in live rounds. Waymo follows Alphabet's candidate policy, and the shared document leaves an obvious trail when someone stops typing.

A panel of engineers who never met you and decide from written feedback alone. Your interviewers recommend, the committee approves, and the two often disagree.

Around $315K in Mountain View, and the same in San Francisco or New York, because Waymo pays one national band. About 29 percent is Alphabet stock at the public daily price, plus a target bonus.

Six to ten weeks. The loop itself is quick, but committee review, team match and the separate pay approval each add time.

No. GothamLoop covers 120+ companies including OpenAI, Google, Meta, Amazon and Apple.

Pricing plan

Get used to winning

Monthly Access
Month by month access to the most accurate SWE interview question list on the planet
$199
Per month
3h : 45m : 23s
Lifetime Access
Unlimited access to all current and future SWE interview questions, forever.
Save 60%
$800
$329
One time
Company Interview Guides

Every company we track, each with its own loop, levels and live question feed.

$472k
Palo Alto, CA
$748k
Mountain View, CA
58%
Increase
$382k
San Francisco, CA
$561k
San Francisco, CA
47%
Increase
$347k
New York, NY
$463k
New York, NY
33%
Increase
$426k
San Jose, CA
$618k
San Francisco, CA
45%
Increase
$472k
Palo Alto, CA
$748k
Mountain View, CA
58%
Increase
$382k
San Francisco, CA
$561k
San Francisco, CA
47%
Increase
$347k
New York, NY
$463k
New York, NY
33%
Increase
$426k
San Jose, CA
$618k
San Francisco, CA
45%
Increase