Questions › Root Cause Analysis › Google
Gemini engagement dropped 20% in two weeks among enterprise admins. Diagnose the issue
- Root Cause Analysis
- Hard
- 15 min
Sign in to view the question description. Premium company questions require an active Premium plan.
How to structure your root-cause analysis
Verify the signal before proposing fixes. Narrow the blast radius, compare hypotheses, and ask for evidence that separates them.
- Define the metric precisely and confirm the drop is real rather than an instrumentation change.
- Segment by time, platform, geography, cohort, funnel step, and release exposure to localize the issue.
- Build internal and external hypotheses, then rank them by likelihood, impact, and speed to test.
- Request discriminating evidence, identify the root cause, and only then discuss mitigation and prevention.
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
All Root Cause Analysis questions · Product manager interview questions by skill area
Reviewed by PMMockr Editorial. Company names are descriptive and do not imply affiliation.
Related Root Cause Analysis questions
- Conversion in Search fell after a redesign. How would you investigateGoogle · Root Cause Analysis · Easy
- Revenue from Gmail is flat despite user growth. Diagnose the root causesGoogle · Root Cause Analysis · Easy
- Retention for advertisers declined in Google Pay. What is your analysis planGoogle · Root Cause Analysis · Easy
- A key metric for Maps spiked unexpectedly. How do you determine if it is healthyGoogle · Root Cause Analysis · Hard
- Conversion in Android fell after a redesign. How would you investigateGoogle · Root Cause Analysis · Hard
- Revenue from Photos is flat despite user growth. Diagnose the root causesGoogle · Root Cause Analysis · Hard