How do you decide which features to build first?
What the interviewer wants to hear
- Start from goals and strategy
- Estimate value or impact and effort
- Use a framework like RICE or MoSCoW for structure
- Consider risk, dependencies and evidence
- Review with the team and stakeholders
Model answer
I start from the current product goals, for example improving activation this quarter, because priorities only make sense against a goal. Then for each idea I look at the problem it solves, how many users it affects, how much impact we expect, how confident we are based on evidence, and how much effort it needs. A simple framework like RICE helps me compare ideas in a consistent way and makes the discussion less about opinions. I also look at risks and dependencies, like work that unblocks other teams. I review the result with engineering and design, because they often see effort or opportunities I miss, and share it with stakeholders with clear reasoning. The framework is a tool, not a rule; judgement still matters.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy Product Manager questions
- In your own words, what does a product manager do?
- What is an MVP? Give an example of how you would build one.
- How do you work with engineers and designers?
- Pick a product you use often. How would you improve it?
- Explain how an A/B test works and when you would use one.
- How do you write user stories and acceptance criteria that your team can build from?
- What is the product manager's role in agile ceremonies like planning, stand-ups, reviews and retrospectives?
- What makes a good product roadmap?
- Customers send feedback through support, sales, reviews and surveys. How do you use it?