Google·Product Manager·Onsite - Product Sense / Strategy
- How do you know when a design review is complete?
“I fumbled this a bit because my first instinct was to say 'when everyone signs off' which is basically a non-answer.”
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 fumbled this a bit because my first instinct was to say 'when everyone signs off' which is basically a non-answer.”
“The core of this is backtracking and I knew that going in, but I fumbled the box index calculation for a bit.”
“I picked the right data structure and got the code mostly working on my own, which felt good.”
“I jumped straight into a number and then had to backtrack, which felt messy.”
“This is where I spent most of my time and still felt like I left stuff on the table.”
“I went straight to wildlife conservation as the use case, which felt safe but maybe too narrow.”
“My first instinct was a plain linked list and I said so out loud, which was fine for addParty and cancelParty but then seatTable came up and I realized scanning the whole list each time was not going to fly for 200k ops.”
“I spent way too long on the problem setup and barely got to actual features before they nudged me along.”
“This one messed with my head a little because Google owns Android but also competes with Meta.”
“Went through it well enough but fumbled some edge cases.”