Google·Product Manager·Onsite - Behavioral / Leadership
- Tell me about a failure and how you dealt with it.
“I had a story prepped but the follow-up questions kind of unraveled it.”
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 had a story prepped but the follow-up questions kind of unraveled it.”
“This sounds open-ended but they drill hard once you pick your project.”
“The core implementation wasn't bad.”
“My first instinct was just a sorted list with bisect.insort, which gets you O(log n) insert but O(1) findLargest since you can index directly.”
“My first instinct was to just slap a set on the output from the plain subsets solution and call it done.”
“Spent the first two minutes just trying to scope it.”
“I went straight to multimodal stuff, real-time voice with better prosody, image translation that actually understands context not just words on a sign.”
“I started with the queue and producer interface which felt natural, but then they kept pulling the thread.”
“I leaned on lower_bound and upper_bound after sorting the dictionary lexicographically.”
“I had a decent story ready but the 'successfully implemented' part tripped me up a bit.”