Product sense questions
These test your ability to think like a product manager — user empathy, prioritisation, and structured thinking.
1. How would you improve [a product you use daily]?
What they're testing: Structure, user empathy, prioritisation framework.
Model answer structure:
- Clarify scope: "For which users? Which platform? What's the goal — retention, acquisition, monetisation?"
- Identify user segments and their core jobs-to-be-done
- Surface 3–5 pain points through that lens
- Propose 2–3 improvements, ranked by impact and effort
- State how you'd measure success
2. How would you prioritise a product backlog with 30 items and limited engineering capacity?
Model answer: "I'd start by mapping each item against two axes: user impact (based on user research, support data, and qualitative interviews) and strategic alignment (does it serve our current OKR?). I'd deprioritise anything that doesn't pass the strategic filter, however popular. For the remaining items, I'd use a scoring model — RICE or ICE — to rank by reach × impact ÷ effort. Then I'd sense-check the top 5 with engineering to validate effort estimates before committing to a sprint."
3. A product metric drops 20% overnight. Walk me through your diagnosis.
Model answer:
- Confirm the data: is the drop in the data pipeline or real?
- Segment the drop: which platform, region, user segment?
- Correlate with recent changes: deployment, A/B test, marketing campaign?
- Look at upstream metrics: is it a funnel issue?
- Check external factors: competitor launch, news event?
"The structure I'd follow: rule out data error → segment → correlate with changes → check externals."
4. How do you decide when a product is ready to launch?
Strong answer covers: launch criteria defined upfront, error rate and performance benchmarks, user testing with target cohort, rollout plan (staged vs. big bang), rollback plan, comms.
5. Design a product for elderly users who struggle with smartphone apps.
What they're testing: Accessibility thinking, user empathy, constraints-based design.
Discuss: larger touch targets, simplified navigation, high contrast, voice as primary input, family member proxy workflows, progressive disclosure.
Execution questions
6. How do you work with engineers who push back on timelines?
7. Tell me about a product launch that didn't go to plan. What did you do?
8. How do you handle a situation where engineering says something will take 3 months and the business needs it in 3 weeks?
9. How do you build trust with a new engineering team?
10. What does a good product spec look like to you?
Strategy questions
11. How would you evaluate whether to build, buy, or partner for a new capability?
12. A competitor has launched a feature that's getting rave reviews. How do you respond?
13. How do you think about pricing a new B2B product?
14. What framework do you use to evaluate a new market opportunity?
15. How would you build a moat around this product in 2 years?
Analytical questions
16. How would you set up an A/B test for a new checkout flow?
Strong answer: hypothesis, control vs. variant, sample size calculation, success metric, guardrail metrics, duration, analysis plan.
17. Our DAU/MAU ratio is 0.25. Is that good or bad?
Context-dependent: "That depends on the product category. For a social network, 0.25 is weak. For a tax filing tool, it's expected — the use case is monthly. I'd want to benchmark against category peers and track the trend."
18. How would you measure the success of a new onboarding flow?
19. What metrics would you track for a subscription product's health?
20. How do you know if a feature you shipped is actually working?
Behavioural questions for PMs
21. Tell me about a product decision you made that you later regretted.
22. Describe a time you had to say no to a senior stakeholder's feature request.
23. Tell me about a time you shipped something that failed. What did you learn?
24. Describe a situation where you had to align multiple stakeholders with conflicting priorities.
25. Tell me about a time you used data to change someone's mind.
Leadership and influence
26. How do you lead without authority?
27. How do you motivate a team that's been working on a long-running, unglamorous project?
28. Tell me about a time you had to influence an executive on a product decision.
29. How do you manage a difficult relationship with a designer or data scientist?
30. What does "being a good PM" mean to you?
Vision and creativity
31. What product would you build if you had unlimited resources?
32. How would you approach building a product in a market you know nothing about?
33. What's a product you think is underrated and why?
34. How would you design a product to reduce food waste?
35. What do you think will be the most important product trend in the next 3 years?
Role-specific questions
36. Why do you want to be a PM?
37. Where do you see yourself in 3 years?
38. What does your ideal PM role look like?
39. How do you stay up to date on product trends and tools?
40. What PM at a company do you most admire? Why?
Technical depth questions (for technical PM roles)
41. Explain how you'd architect a notification system that scales to 10M users.
42. What is an API and how would you explain it to a non-technical stakeholder?
43. What's the difference between SQL and NoSQL databases? When would you use each?
44. How do you work with engineers on estimating technical debt?
45. What does observability mean to you as a PM?
Questions about your work history
46. Walk me through the product you're most proud of.
47. What's the biggest mistake you made as a PM and how did you fix it?
48. Tell me about a time you had to work with incomplete user research.
49. Describe a product you killed. How did you make that decision?
50. What would your current team say is your biggest strength — and your biggest weakness?
How to practise these questions
Reading the questions is not enough. You need to say your answers out loud and get feedback on structure, depth, and delivery. AI Career Mentor generates PM-specific interview questions tailored to your level and target company, scores each answer, and gives you a model answer to compare.