Waymo VO got blindsided by the data fluency round (Rejected)
Replies (5)
Same thing happened to me last year. The data fluency round is no joke. I spent 3 weeks doing LC graphs and basically nothing on experiment design. Walked out knowing I had bombed it.
Thanks for sharing this. I have a Waymo phone screen next week and this is exactly the kind of thing I wouldn't have thought to prep. Going to look into AV evaluation metrics now.
Good luck. Honestly even if you read up on it there's not much out there. The round feels very internal to how Waymo thinks about measuring model quality.
What did the latency follow-up look like? Was it like A/B test significance testing or something more AV-specific?
More like compare two experiment groups and determine if the latency difference is meaningful. But the setup was really specific to their simulation pipeline which I had zero context on. Hard to reason about without domain knowledge.
Waymo coding is medium at best tbh. The data fluency is where they actually filter people. I passed coding and SD fine but got an extra data fluency round added before they finally rejected me.
Wait they added an extra round? That's rough. I at least got a clean no. Didn't know they did that.
back to grinding I guess. same boat, also rejected after data fluency. AV domain knowledge really matters there and it's not something you can fake in 45 minutes.