Try the answer style before you buy.

Sample 1: product analytics case

Prompt: A new onboarding flow raised activation, but paid conversion stayed flat. The PM wants to launch it to every user. What do you inspect first, and what do you recommend?

• Open with the decision: ship, hold, narrow rollout, or investigate.
• Define activation and paid conversion at the right grain before comparing cohorts.
• Cut by acquisition source, first successful action, account size, and time to value.
• Check whether activation quality fell, conversion lagged, or one segment drove the lift.
• End with one recommendation, one risk, and one metric that would change your mind.

Score it in five checks

• Did you say the business decision before listing metrics?
• Did you name the denominator and timing window?
• Did you pick one high-signal segment instead of ten charts?
• Did you explain a credible mechanism?
• Did you finish with a clear recommendation?

If you missed three or more, use the Product Analytics packet before the live round.

Sample 2: leadership story

Prompt: A senior stakeholder rejected your analysis because it threatened a launch plan. Tell me what happened and what you changed.

• Start with the decision at stake and the metric or customer risk.
• Name the disagreement without making the stakeholder look foolish.
• Explain the evidence you used, the tradeoff you accepted, and the room you gave them to disagree.
• Say what changed afterward: launch scope, metric review, experiment design, dashboard ownership, or decision cadence.
• End with the operating lesson, not a perfect hero story.

Score it in five checks

• Did you name the real tension?
• Did you make your action specific?
• Did you avoid blaming the stakeholder?
• Did you show a change in behavior, process, or decision quality?
• Could you defend every fact in a follow-up?

If the answer turns into a resume walkthrough, use the Leadership packet before the final round.