Metrics question

Android weekly usage dropped all of a sudden. How do you find out what happened?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

Start a mock interview on this question · Mock interview from a job description

What this question tests

Root cause analysis for a metrics drop: structuring a debugging investigation methodically rather than guessing at causes.

How to approach it

  1. Confirm the drop is real: rule out data pipeline or instrumentation errors before investigating product causes, a common false alarm.
  2. Segment the drop: check if it is uniform across regions, device types, app versions, or user cohorts, since a localized drop points to a different cause than a global one.
  3. Check for a recent change: correlate the timing with recent app releases, OS updates, or Android policy changes, since a shipped bug is the most common cause of a sudden drop.
  4. Check external factors: competitor launches, negative press, or platform-level issues like Play Store policy changes or outages.
  5. Once the cause is narrowed, quantify severity and decide urgency: a widespread crash needs an immediate hotfix, while a gradual regional dip needs deeper investigation.
  6. Propose next steps: rollback the suspected release if correlated, or run a targeted user survey if the cause remains unclear.

What a strong answer includes

Common mistakes

Likely follow-up questions

More metrics questions

More questions from Meta

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank