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

SeniorPrefer not to say

Jun 2026

Summary

Google PM interview with a classic 'critique an app you hate' question that spirals into strategy and metrics. Pretty standard format but the follow-up about measurement tripped me up more than I expected.

Questions Asked (1)

Name an app that's widely popular but that you personally dislike. As the PM of that app, what would you change, and how would you measure whether those changes worked?

Product Sense & IdeationProduct Analytics & MetricsProduct Strategy

Author's notes

The first part is fun until you realize you're about to trash a product in front of someone who might love it.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a widely used app that you genuinely dislike, but be careful to frame your dislike around specific user problems rather than personal taste. Then, as PM, propose 1-2 high-impact changes that address those problems, and define success metrics that tie directly to your changes and the app's business goals.

Pro tip: Pick an app where your dislike is based on a clear user pain point that many others share, and show you understand the business trade-offs of your proposed changes. Avoid apps that are direct competitors to Google products to prevent awkwardness.

1. Select the app and articulate the problem

Name a popular app you dislike and explain why, focusing on specific user pain points or unmet needs rather than subjective preferences. Briefly mention the app's core value proposition and target users to show context.

2. Prioritize one or two key changes

Propose 1-2 concrete product changes that address the identified problems, explaining how they would improve the user experience and align with the app's business goals. Consider feasibility and potential trade-offs.

3. Define success metrics

For each change, specify measurable metrics that would indicate success, such as engagement, retention, conversion, or satisfaction scores. Distinguish between leading and lagging indicators.

4. Outline measurement plan

Describe how you would measure these metrics (e.g., A/B testing, cohort analysis) and what targets would constitute success. Mention potential guardrail metrics to monitor unintended consequences.

5. Summarize impact and iterate

Conclude by summarizing the expected impact and how you would use the data to iterate on the changes. Show a mindset of continuous improvement.

Key Points to Mention

User-centric problem identification: Clearly articulate the user pain point that drives your dislike, supported by evidence or common complaints.
Prioritization: Explain why you chose these changes over others, using a framework like impact vs. effort or RICE.
Metrics selection: Choose metrics that are directly tied to the changes and reflect both user value and business value.
Measurement methodology: Mention specific methods like A/B testing, user surveys, or funnel analysis to validate impact.
Trade-offs and risks: Acknowledge potential negative consequences of your changes and how you would mitigate them.
Business alignment: Connect your changes to the app's overall strategy and revenue model to show strategic thinking.

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