Product Manager Interview Questions

1.1The PM role - what it is, what it is not, and why it is often misunderstood

1.2Product strategy - vision, goals, and how the product roadmap connects to business objectives

1.3The PM as the intersection of user, business, and technology - balancing all three

1.4Different types of PM - B2B vs B2C, platform vs feature, growth vs 0-to-1 product management

2.1User research methods - interviews, surveys, usability testing, and when to use each

2.2Jobs to be done - understanding what customers are actually trying to accomplish

2.3Building and using personas - how to make them useful rather than decorative

2.4Synthesising research - moving from raw data to insights that drive product decisions

3.1Product vision - how to develop one, communicate it compellingly, and use it to guide decisions

3.2Competitive analysis - understanding the market, identifying differentiation, and tracking competitors

3.3Market sizing - TAM, SAM, SOM, and using market data to build the product business case

3.4Strategic trade-offs - how to make hard prioritisation decisions when everything feels urgent

4.1Roadmap formats - outcome roadmaps vs feature roadmaps and why the distinction matters

4.2Prioritisation frameworks - RICE, MoSCoW, impact vs effort, and how to choose the right one

4.3Managing stakeholder requests - how to handle the constant stream of feature demands professionally

4.4Communicating the roadmap - how to present it to different audiences without overpromising

5.1Working with engineering in agile - the PM role in sprint planning, refinement, and review

5.2Writing user stories and acceptance criteria - what good looks like and why bad stories cause rework

5.3Managing scope in a sprint - what to cut, what to escalate, and how to make the call

5.4Velocity, capacity, and planning - how to work with engineering estimates without turning them into commitments

6.1Defining the right metrics - how to choose KPIs that actually measure what matters

6.2Funnel analysis - understanding where users drop off and what to do about it

6.3A/B testing - experimental design, statistical significance, and interpreting results

6.4Using data to make decisions - combining quantitative and qualitative evidence effectively

7.1Product launch planning - coordinating engineering, marketing, sales, and support for a release

7.2Pricing and packaging - the PM role in how the product is positioned and sold

7.3Launch metrics - how to measure whether a launch was successful and what to do if it was not

7.4Post-launch iteration - how to keep improving a product once it is live with real users

8.1Managing engineering relationships - building trust, handling disagreements, and making decisions together

8.2Managing executives - how to communicate up, push back diplomatically, and get what you need

8.3Cross-functional collaboration - working with design, data, marketing, and sales without authority

8.4Saying no - how to decline requests without damaging relationships or missing important signals

9.1Business model understanding - how the product makes money and the PM role in protecting the model

9.2Unit economics - CAC, LTV, payback period, and why PMs need to understand them

9.3Build vs buy decisions - the product perspective on make or partner decisions

9.4Thinking in systems - second-order effects, unintended consequences, and designing for emergence

10.1Product sense questions - how to demonstrate empathy, insight, and commercial judgment in an interview

10.2Analytical questions - metrics problems, experiment design, and product case studies

10.3Behavioural questions - prioritisation decisions, stakeholder conflict, and shipping something imperfect

10.4Compensation negotiation for PM roles, evaluating a product organisation, and questions that reveal product culture