Metrics question

A design-partner customer says adoption of Claude Tag on a newly launched surface spiked at launch and then stalled. How would you diagnose the problem, what metrics and segmentation would you examine, and how would you determine whether the root cause is onboarding, permissions friction, model behavior, or weak product-market fit for that surface?

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

Tests diagnostic rigor for a spike then stall adoption pattern, distinguishing onboarding, permissions, model behavior, and product-market fit as root causes.

How to approach it

  1. Restate the pattern: a launch spike then a stall, pointing to a novelty effect rather than sustained value, needing segmentation to confirm why.
  2. Segment usage by team and role, since the stall could be concentrated in specific teams that hit a specific blocker.
  3. Check onboarding completion and repeat invocation separately, since a stall right after first use points to onboarding while a later stall points elsewhere.
  4. Check for permissions friction, such as users who tried to invoke it in a channel it lacked access to and silently gave up.
  5. Interview a sample of users who stopped, asking whether outputs were wrong, invocation was confusing, or the surface just was not a fit.

What a strong answer includes

Common mistakes

Likely follow-up questions

More metrics questions

More questions from Anthropic

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