Google·Product Manager·Onsite - Product Sense / Strategy
- How would you design A/B tests to identify and reduce user frustration in Google Maps?
“My first instinct was to jump straight into test ideas, which was a mistake.”
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
“My first instinct was to jump straight into test ideas, which was a mistake.”
“I went in thinking I had a good story but halfway through I realized I was unconsciously framing it so I still looked smart.”
“This one threw me a bit because you're essentially sitting in Google's house telling them what they're getting wrong.”
“I picked a story about a cross-functional partner who kept pushing back on roadmap decisions.”
“This one sounds easy until you're sitting there realizing all your 'interesting' projects sound boring when you say them out loud.”
“I went straight to user segments and ad placement levers, which felt right but I probably skipped over defining what '20%' actually means in context.”
“Classic Google-style product sense question where the scope is deliberately huge.”
“I fumbled a bit because I hadn't thought about the 'why meaningful to you' part, I just had a rehearsed answer about growth and impact that felt hollow even as I said it.”
“I knew this one cold so I led with the linear decision boundary assumption and the sigmoid output, then hit the independence of features and the log-odds interpretation.”
“Classic stack problem but I second-guessed myself on the edge cases, like empty strings and nested mixed brackets.”