How would you define success metrics for a new feature?
What the interviewer wants to hear
- Start from the user problem and business goal
- Choose one primary metric tied to value
- Add input or leading metrics and guardrails
- Set baseline and target before launch
- Plan how to measure, such as an A/B test
Model answer
I start with the problem the feature solves and the business goal it supports. Then I choose one primary metric that shows real value, not just usage. For example, for a reminders feature in a bill payment app, the primary metric could be on-time payments per active user. I add supporting metrics, like adoption of reminders and the share of reminders that lead to a payment, so I can see where the funnel breaks. I also choose guardrails, such as notification opt-outs or uninstalls, to make sure we are not annoying users. I record the baseline and agree a realistic target before launch. Where possible we run an A/B test or a staged rollout so we can link the change to the feature, and I review results after two to four weeks.
Can you answer it under time pressure?
Take a timed medium round and get scored on every answer.
More medium Product Manager questions
- How do you say no to a stakeholder request?
- How do you run customer discovery for a new problem area?
- Tell me about a feature that did not perform as expected. What did you do?
- How do you write a product spec or PRD that engineers find useful?
- Leadership wants to change your product's pricing. How would you approach it?
- Walk me through how you plan a major product launch.
- Your A/B test finished and the result is not statistically significant. What do you do next?
- How would you set OKRs for your product team for next quarter?
- How would you tell whether a new product has product-market fit?