Product manager analytics interview questions

As asked

You ship a new social-graph feature in a content app. How do you measure whether it worked?

Sample answer outline

Set the north star (does the feature increase the thing the product cares about - daily active, retention, content created). Set proximate metrics that should move first (adoption of the feature, follow graph growth, comments per session). Set guardrail metrics that must not regress (load times, reports of abuse, churn of cohorts who don't use the feature). Plan the A/B test: power, MDE, exposure unit, duration. Plan the read-out: who decides, against what threshold, on what timeline. The strong answer separates leading from lagging indicators and is explicit about confounders.

Expect these follow-ups

• What is a metric you would actively NOT use?
• How do you handle network effects in the experiment?
• What if adoption is high but retention is flat?

As asked

Lots of teams use DAU/MAU as a proxy for retention. What metric would you actively avoid using, and why?

Sample answer outline

DAU/MAU itself has known failure modes: it conflates frequency with depth, it's easy to game with notifications, and it's not cohort-aware - a flat DAU/MAU can hide aggressive churn covered by acquisition. Avoid: total session count (rewards superficial poking), time spent (rewards friction, not value), feature adoption in isolation (a single-feature spike doesn't mean health). Prefer: cohorted retention curves (day 1, day 7, day 30), L28 (days active in last 28), and an action-based engagement metric tied to the value the product delivers.

Expect these follow-ups

• When IS DAU/MAU the right metric?
• How do you measure retention for a product used once a quarter?
• What is L28 and why is it better than 28-day MAU?

As asked

Your team does not have a clear north star metric and different people optimise for different things. How do you choose one, what makes a good north star versus a bad one, and what are the dangers of a single metric?

Sample answer outline

A good north star captures the value the product delivers to users in a way that, when it goes up, the business genuinely benefits, so it sits between a vanity number and pure revenue. It should be a leading indicator you can influence with the product, reflect real user value rather than mere activity, and be understandable enough to align a team. Bad north stars are things like raw signups or total page views, which can rise while the product gets worse, or revenue alone, which is lagging and tempts short-term extraction. The danger of any single metric is that teams optimise it literally and find perverse shortcuts, so it must travel with guardrails, things that must not regress such as retention, quality, and trust, and it should be decomposed into the input metrics teams actually move. The signal is choosing a metric that proxies durable value and pairing it with guardrails, rather than pretending one number is the whole truth.

Expect these follow-ups

• Why are signups or page views poor north star candidates?
• What guardrail metrics would you attach, and why?
• How do you stop a team from gaming the single metric?