Skip to content
PMInterviewKit

Product metrics interview questions

Metrics questions come in two kinds: choose the number a product should steer by, or work out why a number moved. Both test whether you can tie a metric to the value a user actually gets.

Below: what the round tests, the method in short, and 40 practice questions, each with a first move and the outline of a strong answer. All free, no sign-up.

What the interviewer is scoring

  • Whether your metric counts real value, not opens, sign-ups or anything that only goes up.
  • Whether you check that a change is real and find where it lives before you guess at causes.
  • Whether you name guardrails, and what you would do next with the answer.

Watch a mock interview from this round

Grace’s first try, Ava’s pushback, then the stronger answer with its scorecard. The question: Daily active users on a messaging app dropped 10% week over week. How would you investigate?

Read what Ava and Grace say
Ava:
I'm Ava. Today I'm interviewing Grace, on a drop in daily users.
Grace:
I'm Grace. I'm preparing for product manager interviews.
Ava:
Grace, daily active users on our messaging app dropped 10% this week. How would you investigate?
Grace:
Probably a competitor launched something. I'd ship a new feature to win people back.
Ava:
Slow down. How do you know the drop is even real? Try again.
Grace:
Right. First, is it real? I'd compare the dashboard with raw server logs. If the logs are flat and only the dashboard fell, it is a tracking break, and I stop. I'd ask if the definition of a daily user changed, and check the pipeline ran in full. Say all three are clean, so the drop is real. Next, size. Ten percent against a normal weekly swing of two is a real move. It was a step on Tuesday, not a slide. Messages sent fell ten percent too, while sign-ups held. So existing users went quiet. Then I slice, by platform, country, app version, and new versus existing users. It lives on Android, version 8.2, in every country. Now suspects. Inside: Tuesday's 8.2 release, a notification experiment, a pricing change. Outside: an Android update, a competitor, a holiday. A competitor or a holiday would hit iPhone too, so they drop out. The experiment ran on both platforms, so it ranks last. The release fits the day, the platform and the version, so it ranks first. The Android update is second. To settle it. My likeliest cause is the 8.2 release. The proof: compare 8.2 with 8.1 on the same Android version. If only 8.2 is down, it is the release. If both are down, it is the update. If it is the release, I roll back behind a flag today. I tell the Android lead, so the fix has an owner, and support, so they can answer users. I call it fixed when daily users are back within two percent of last week for three days.
Ava:
That's the order. You proved it was real before you chased a cause, and you said what fixed looks like. That would score well.

The method in short

Metrics: pick the metric: Value Moment

  1. Name the valueWho gets what from the product, in one sentence. Name both sides of a marketplace.
  2. Find the momentThe action that shows a user just got that value, not that they opened the app.
  3. Make it a numberDecide what you count, over what window and with what qualifier. Match the window to how often the value happens.
  4. Stress-test itDoes it rise only with real value? Can a team game it? Does it lead revenue and retention? Will it move within weeks?
  5. Guard itAdd one to three guardrails that catch the damage if a team chases it too hard.

Example

A recipe app: a saved recipe is a promise and a cooked one is the value, so steer by recipes cooked per week, guarded by unsubscribes from its reminder emails.

Most common mistake

Reaching for revenue, sign-ups or plain daily users by reflex. They lag, only ever go up, or count opens that gave nobody anything.

The method in short

Metrics: diagnose a change: Change Drill

  1. Check it’s realRule out logging, pipeline and definition changes before you hunt for causes.
  2. Size itMeasure how large it is, when it started, whether it was a step or a slide, and which other numbers moved.
  3. Slice itSplit by platform, region, user type and the metric’s parts until you find where the change lives.
  4. Line up suspectsInternal changes (releases, experiments, prices) and external ones (season, competitors, OS updates) that fit the timing and the slice. Rank them.
  5. Settle itName the likeliest cause, how you would prove it, what you would do, and whom you would tell.

Example

Sign-ups down 12% since Tuesday: logging is unchanged, the drop is all on Android, and Tuesday’s release changed the sign-up screen, so roll it back behind a flag and confirm with tomorrow’s numbers.

Most common mistake

Guessing at causes (a competitor, the weather) before checking the drop is real and finding where it lives.

40 product metrics questions to practice

Pick one, answer it out loud on a timer, then open its page to compare with the outline. Start with the warm-ups if this round is new to you. Want a score? Paste your answer into the free answer grader, or answer it out loud with Ava.

Warm-up questions (10)

Standard questions (22)

Stretch questions (8)

Common questions about this round

What is a north star metric?

A north star metric is the one number a product team steers by, chosen because it rises only when users get the product’s core value. For a recipe app that could be recipes cooked per week, not recipes saved. A good one is hard to game, moves within weeks and leads revenue and retention.

How do I answer “a metric dropped, what do you do”?

Work in order. Check the drop is real (logging, pipelines, a changed definition). Size it: how big, since when, a step or a slide. Slice it by platform, region and user type until you find where it lives. Line up the internal and external changes that fit that timing and slice. Then name the likeliest cause, how you would prove it and what you would do.

What is a guardrail metric?

A guardrail is a number you refuse to harm while you chase the main one. If a team steers by recipes cooked per week and uses reminder emails to get there, unsubscribes from those emails is a guardrail: it shows the damage if the reminders get pushy.

Get all 200 questions as a PDF

Every question in the bank, all seven round types, with its first move, a strong opening, the answer outline and the common mistake.

From PMInterviewKit

One method for each interview round, 88 short lessons to read or watch, 66 worked answers and mock interviews with Ava. The first lesson of every module is free. The full kit is $129 once.