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

Intermediate

May 2026

Summary

Google PM interview with a product sense question about a bad software experience. Pretty standard but it's the kind of question that sounds easy and then you're sitting there second-guessing every app you've ever used.

Questions Asked (1)

Describe a software product you've had a frustrating experience with recently and explain what made it feel broken from a user's perspective.

Product Sense & IdeationProduct Analytics & Metrics

Author's notes

I blanked for a second and picked something too obscure trying to seem interesting.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a product you use regularly and can critique objectively, then walk through a specific frustrating scenario from the user's perspective. Frame the frustration around unmet user needs and broken expectations, not just personal annoyance, and tie it back to product management principles like user empathy and metrics.

Pro tip: Show that you can separate emotional frustration from objective analysis by quantifying the impact (e.g., time wasted, tasks abandoned) and suggesting how you'd measure and prioritize the fix.

1. Select a Relevant Product

Pick a widely-used product (not a competitor) that you have deep experience with, so you can speak authentically and avoid confidentiality issues.

2. Describe the Frustrating Experience

Narrate a specific, recent scenario where the product failed you, including the context, your goal, and the exact breakdown.

3. Diagnose Why It Felt Broken

Analyze the root causes from a user perspective: mismatched mental models, poor feedback, unnecessary friction, or broken trust.

4. Connect to Product Principles

Link the frustration to broader product management concepts like usability heuristics, user journey mapping, or key performance indicators (e.g., task success rate, time on task).

5. Propose How You'd Improve It

Suggest concrete fixes and how you'd measure their impact, showing product sense and analytical thinking.

Key Points to Mention

User empathy: understanding the user's goal and emotional state during the experience.
Specific usability heuristics violated (e.g., visibility of system status, user control and freedom).
Quantifiable impact: time lost, tasks abandoned, or error rates.
Metrics to track: task success rate, time on task, customer satisfaction (CSAT), or Net Promoter Score (NPS).
Root cause analysis: distinguishing between symptoms and underlying issues.
Prioritization: how you'd balance fixing this against other product improvements.

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