← Google Interview Insights

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

Senior
May 2026

Summary

Google PM interview question about handling a live experiment gone sideways. Pretty classic product sense setup but the specifics made it tricky to navigate cleanly.

Questions Asked (1)

Q1

You're the PM for Chrome and need to make a go/no-go call on auto-playing video ads. You're in a 5% rollout and just got word that negative feedback on Chrome pages with auto-play enabled is up 20%. What's your next move?

A/B Testing & ExperimentationProduct Analytics & MetricsProduct Strategy
Author's notes

I spent too long upfront trying to dissect what 'negative feedback' even means here, which was probably the right instinct but I got a bit lost in it.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by acknowledging the negative signal but avoid making a premature no-go call; instead, frame the situation as a need for deeper analysis. Outline a structured plan to validate the data, assess the trade-offs between user experience and business metrics, and determine next steps such as pausing the rollout, iterating on the feature, or continuing with safeguards.

Pro tip: Demonstrate that you understand the difference between correlation and causation by questioning whether the 20% increase is directly attributable to auto-play ads or if other factors (e.g., seasonality, concurrent changes) could be responsible. Also, emphasize the importance of defining a clear kill criteria before the experiment to avoid emotional decision-making.

1. Validate the data and isolate the cause

Confirm the reliability of the negative feedback metric and check for confounding variables. Segment the data by user demographics, geography, and device to see if the impact is uniform or concentrated.

2. Assess the magnitude and business impact

Quantify the negative feedback in absolute terms and correlate it with other key metrics like engagement, retention, and revenue. Determine if the 20% increase translates to a material user experience degradation or if it's within acceptable bounds.

3. Evaluate trade-offs and alternatives

Consider potential mitigations such as limiting auto-play to certain contexts, adding user controls, or capping frequency. Weigh the expected benefits (e.g., ad revenue, content discovery) against the costs (user trust, satisfaction).

4. Decide on immediate action

Based on the analysis, choose one: pause the rollout to prevent further negative impact, continue with modifications, or proceed if the feedback is not statistically significant. Communicate the decision and rationale to stakeholders.

5. Define next steps and learnings

If pausing, plan a follow-up experiment with adjustments. If continuing, set up monitoring and guardrail metrics. Document learnings to inform future feature launches.

Key Points to Mention

  • Statistical significance and confidence intervals of the 20% increase
  • Guardrail metrics: user satisfaction, retention, and long-term trust
  • Segmentation analysis to identify affected user groups
  • Trade-off between short-term revenue and long-term user experience
  • Pre-defined kill criteria and success metrics for the experiment
  • Potential mitigations like user controls, frequency capping, or contextual auto-play

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