Meta · Product manager · Analytical Thinking

WhatsApp launches usernames. How would you measure success?

Build a defensible answer, then pressure-test it in the same workspace where you can save the attempt.

See this question in OfferHack Browse the question first. Premium opens the complete worked answer and coaching when you need them.
Independent practice preview

This is a constructed rehearsal, not an official company answer or a prediction of what an interviewer will ask. A company-specific practice prompt synthesized from published interview guidance, candidate reports, official product material, role descriptions, and company values; it is not a claim that this exact question will be asked.

Start with a position

Give the interviewer your decision before the framework.

For “WhatsApp launches usernames. How would you measure success?” at Meta, I would define the intended outcome for a high-intent new or returning user trying to reach a first repeatable outcome, build a driver tree to retained successful outcomes, segment before explaining the movement, and make the decision only after checking low-quality use, churn, support burden, and trust.

Preview the reasoning

Three moves to make the answer concrete.

01

Define the outcome

  • Define product goal and north star first
  • Give the recommendation before the framework.
02

Build the metric tree

  • Build a metric driver tree and segment
  • Compare at least one credible alternative.
03

Segment before explaining

  • Use counter-metrics and second-order effects
  • Compare at least one credible alternative.

Measurement check

A metric is useful only when it changes the decision.

North star
retained successful outcomesMeasures the repeated user or customer outcome, not mere feature activity.
Diagnostic
time to first value and second-use rateExplains whether quality and the critical journey improved for the intended segment.
Guardrail
low-quality use, churn, support burden, and trustMakes the principal downside observable: novelty usage, incentive-driven growth, support burden, or a retention lift isolated to the wrong cohort.

Interviewer pressure test

Do not stop when the first answer sounds polished.

  1. Why prioritize a high-intent new or returning user trying to reach a first repeatable outcome, and who did you explicitly defer?
  2. How would your answer change with two weeks, three engineers, or a tenfold scale increase?
  3. What is the strongest rejected alternative and when would it win?

Turn reading into retrieval

Close the guide. Give the answer in your own words.

Use the free scratchpad and timer, then decide whether you need the complete worked answer and coaching.
See this question in OfferHack