Questions › Root Cause Analysis › Top-MNC
Diagnose a sudden drop in retention for AI writing review
- Root Cause Analysis
- Top-MNC
- Easy
- 10 min
Problem Statement Description
You are investigating a sudden retention drop among developers who use an AI writing review product. The product helps developers improve technical writing such as pull request descriptions, design docs, issue comments, code documentation, release notes, or internal engineering updates. The retention issue may affect whether developers continue returning to the tool after initial or repeated use.
Your task is to diagnose the drop before recommending any fixes. Focus on how you would confirm the anomaly, isolate where it is happening, and determine whether the cause is related to measurement, user behavior, product quality, AI output, workflow integration, or external factors.
The experience should consider:
- How retention is defined for this product, including the denominator, time window, and meaningful return action
- Whether the drop is real or caused by tracking, logging, identity, experiment, or reporting issues
- Segmentation by developer cohort, platform, IDE or browser extension, team type, company size, geography, plan, and acquisition source
- Workflow points where developers may abandon usage, such as draft submission, AI review generation, accepting suggestions, editing, or exporting back to their tools
- Product-quality hypotheses, including latency, relevance, hallucinations, tone mismatch, privacy concerns, or reduced trust in AI suggestions
- Recent changes such as model updates, question changes, pricing, onboarding, permissions, integrations, notifications, or enterprise policy changes
- Evidence you would seek from metrics, logs, user feedback, support tickets, session traces, experiments, and qualitative interviews
- Short-term mitigation and longer-term prevention mechanisms once the root cause is identified
The goal is to present a structured RCA approach that narrows the problem from a broad retention decline to specific affected users, workflows, and causes, while separating symptoms from root causes and avoiding premature solution recommendations.
What this question tests
- Root Cause Analysis
- Metric Decomposition
- Hypothesis Testing
- Decision Discipline
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.
Related Root Cause Analysis questions
- A launch in data export tool caused complaints from finance teams. Find the likely causeTop-MNC · Root Cause Analysis · Medium
- Latency and error reports increased in appointment booking. Prioritize the investigationTop-MNC · Root Cause Analysis · Medium
- Retention fell after a redesign of video meeting experience. Investigate the issueTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in repeat usage for loyalty rewards engineTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in renewal confidence for cross-border payment setupTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in accessibility adoption for knowledge search assistantTop-MNC · Root Cause Analysis · Medium
All Root Cause Analysis questions · Product manager interview questions by skill area