Product Manager interview questions

PM interviews look for clear thinking under ambiguity: who the user is, what problem matters most, how you would measure success and how you bring a team with you. Structure your answers and say your assumptions out loud.

  1. 1Tell me about a product you love and how you would improve it.

    What a good answer shows: Pick a specific user and problem, suggest one focused improvement, and say how you would know it worked.

  2. 2How do you decide what to build next?

    What a good answer shows: A clear framework (impact vs effort, RICE), tied to goals and evidence from users and data.

  3. 3How would you improve our product?

    What a good answer shows: Research first: one or two opportunities based on real user pain, with a rough plan to test them.

  4. 4Daily active users dropped 15%. What do you do?

    What a good answer shows: Check data quality, then break the drop down by segment, platform, release and channel before guessing at causes.

  5. 5How do you define success metrics for a new feature?

    What a good answer shows: One primary metric linked to the goal, supporting metrics, and a guardrail so you do not harm something else.

  6. 6Tell me about a product you launched end to end.

    What a good answer shows: Problem, discovery, decisions, trade-offs, launch and a measurable result.

  7. 7How do you work with engineers who disagree with you?

    What a good answer shows: Listen, share the user evidence and the goal, look for options together, and decide clearly.

  8. 8How do you say no to a senior stakeholder?

    What a good answer shows: Show the trade-off against agreed goals, offer an alternative or a later slot, and keep the relationship.

  9. 9How do you gather user insights?

    What a good answer shows: Interviews, usability tests, support tickets, analytics and experiments, and how you avoid leading questions.

  10. 10Write a short product spec for a feature of your choice.

    What a good answer shows: Problem, users, goals and non-goals, user stories, success metrics, risks and open questions.

  11. 11How do you prioritise technical debt against features?

    What a good answer shows: Make its cost visible (incidents, slower delivery) and agree on a steady share of capacity.

  12. 12Tell me about a launch that failed. What did you learn?

    What a good answer shows: Own it, explain what you misjudged and what you now do differently.

  13. 13How would you design a product for first-time internet users?

    What a good answer shows: Simple language, low data use, offline support, trust signals and testing with real users.

  14. 14What is the difference between output and outcome?

    What a good answer shows: Shipping features is output; changing user behaviour or business results is the outcome.

  15. 15How do you run a good roadmap review?

    What a good answer shows: Goals first, themes not dates, evidence for each bet, and clear trade-offs.

  16. 16Estimate how many food delivery orders happen in Bengaluru each day.

    What a good answer shows: A clear, stated chain of assumptions and a sanity check; the reasoning matters more than the number.

  17. 17How do you handle a feature request from your biggest customer?

    What a good answer shows: Understand the underlying need, check if other customers share it, and avoid building one-off features.

  18. 18How do you work with design?

    What a good answer shows: Involve design in discovery, agree on the problem, and review work against user goals, not taste.

  19. 19What makes a great product manager?

    What a good answer shows: Curiosity about users, clear communication, good judgment with incomplete data, and ownership of results.

  20. 20Why do you want to be a PM here?

    What a good answer shows: Specific reasons tied to their product, users and stage, and what you would bring in the first months.