← Google Interview Insights

Google·Product Manager·Onsite - Product Sense / Strategy·Intermediate

Intermediate
Apr 2026

Summary

Google PM interview with a classic product sense question. Pretty standard setup but the open-endedness of it made me second-guess my answer the whole way through.

Questions Asked (1)

Q1

Pick a non-technical product you use regularly. How would you improve it?

Product Sense & IdeationProduct Strategy
Author's notes

I went with a physical product thinking it'd be easier to reason about, which in hindsight was a mistake because I spent too long on the problem space and not enough actually proposing anything concrete.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a non-technical product you know deeply, then quickly frame the answer around user needs and business impact. Structure your response by defining the problem, proposing a specific improvement, and explaining how you'd measure success.

Pro tip: Pick a product with a clear, simple user journey (e.g., a coffee shop app) so you can focus on depth of reasoning rather than explaining the product. Show you understand trade-offs by acknowledging potential risks of your improvement.

1. Select and Define the Product

Choose a non-technical product you use regularly and briefly describe its core purpose and target user. Keep it concise to save time for the analysis.

2. Identify a User Pain Point

Highlight a specific problem or unmet need you've observed as a user. Explain why it matters and how it affects the user experience.

3. Propose an Improvement

Suggest a concrete, actionable improvement that addresses the pain point. Be specific about what you would change or add.

4. Explain the Impact and Trade-offs

Discuss how the improvement benefits users and the business (e.g., increased retention, revenue). Acknowledge potential drawbacks or challenges.

5. Define Success Metrics

Outline how you would measure the success of your improvement, using metrics like user engagement, satisfaction, or conversion rates.

Key Points to Mention

  • User-centric reasoning: start with a real user pain point you've personally experienced.
  • Business impact: connect the improvement to metrics like retention, revenue, or market share.
  • Prioritization: explain why this improvement is worth doing now versus other potential changes.
  • Trade-offs: show awareness of potential downsides or implementation challenges.
  • Measurement: propose specific metrics to evaluate success post-launch.
  • Iterative mindset: mention that you'd test and iterate based on user feedback.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.