Waymo Software Engineer Interview Experience — 45-Minute Coding Phone Screen, Rejected for Slow Code

Waymo·Software Engineer·Jul 2026
Technical ScreenRejectedmedium

I had the Waymo phone screen at the end of August. It was 45 minutes of pure coding. I had spent about half a month grinding problems after work. Someone on the forum said they don't have a question bank, so I didn't really try to guess which questions would come up, figuring I would just perform normally.

The problem wasn't actually hard. You're given a list of events in the format [open or end, time, type], where type is something vehicle-maintenance related like oil or brake, and you have to decide whether the vehicle is ready to go. Every event needs a matching close, and each type can only have one event at a time.

I wasn't stuck on the approach. I was stuck on writing the code. You have to compile and run it yourself, and there were a few syntax points I couldn't remember, so I went back and forth editing for ages. I never even got to the follow-up.

A week later I got an automated rejection email. Probably I was just too slow.

Honestly, getting rejected feels pretty bad. If I get this kind of problem again, I'll make sure to run through the syntax and the tests myself first.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Waymo
Role
Software Engineer
Rounds
Technical Screen
Outcome
Rejected
Difficulty
medium
Interview date
Jul 2026
Questions from this interview
1 question

Real Waymo interview experiences

First-hand reports from Waymo candidates — the rounds, the questions they were asked, and how it went.

All 14 Waymo interview experiences