Google·Product Manager·Onsite - Product Sense / Strategy
- How would you design a self-driving car solution tailored specifically for children?
“I spent too long on the obvious stuff, parental controls, safety sensors, that kind of thing.”
FAANG / Big Tech
Most of these Google write-ups come from Software Engineers (1,167), then Product Managers (686) and Data Scientists (125). The most reported rounds are the product sense round (667), the technical phone screen (660), the behavioral / leadership round (252) and the onsite coding round (214).
2146 interview notes · updated Oct 2026
“I spent too long on the obvious stuff, parental controls, safety sensors, that kind of thing.”
“I went straight to the data model and storage layer, which in hindsight was the wrong move.”
“I went broad first, which was probably a mistake.”
“The constraint of staying within the existing Google ecosystem actually tripped me up more than a blank-slate question would have.”
“I went straight into user personas and pain points, which felt right, but I spent way too long on the problem space and barely had time to flesh out actual solutions.”
“I started with storage and bandwidth because those felt obvious, then realized I was probably underselling the compute side.”
“I went with the sweep-line approach, splitting starts and ends into separate events, sorting them, and simulating with two pointers.”
“I had a story ready but rambled through the recovery part and lost the thread.”
“I had a story ready but fumbled the delivery.”
“I froze for a second because the scope is genuinely absurd.”