PM interviews aren't a single test but a set of distinct question types, each probing a different competency and each best answered with a specific framework. Knowing which is which lets you prepare deliberately.
▸ Try the interactive toolPM interviews are not a single kind of test but a set of distinct question types, each probing a different competency and each best answered with a specific framework. Understanding the question categories — what each tests and the framework to use for each — lets a PM prepare deliberately instead of improvising, and recognise in the moment what's actually being assessed.
The major types include product design (product sense, answered with CIRCLES), product strategy (business judgement), analytical/metrics (data fluency, including the metric-drop RCA), estimation (structured quantitative reasoning), behavioural (past behaviour, answered with STAR), technical (working with engineering), and prioritisation. The key skill is recognising the type a question belongs to, because each rewards a different structured approach — answering a strategy question with a design framework, or improvising a behavioural answer without STAR, signals a lack of preparation and structure.
Recognise the question type first — each tests a different competency and rewards a different framework. Answering a strategy question with a design framework, or a behavioural one without structure, signals you didn't recognise what was being asked.
PMs treat interviews as one undifferentiated test and improvise — but each question type rewards a specific structured approach, and using the wrong one (or none) signals exactly the lack of structure interviewers screen for.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Treating interviews as one test | Improvising across all question types performs worse than structured answers. | Recognising types lets you apply the right framework. |
| Using the wrong framework | A design framework for a strategy question signals confusion. | Matching framework to type shows preparation and structure. |
| Improvising behavioural answers | Rambling stories without STAR lose the point. | STAR gives behavioural answers clear structure. |
| Not recognising what's tested | Missing the competency being assessed answers the wrong question. | Identifying the type reveals what to demonstrate. |
Each type tests a different competency and rewards a specific framework — so the first skill in any answer is recognising which type you've been asked.
| Question type | What it tests | Framework to use |
|---|---|---|
| Product design | Product sense, user empathy, creativity | CIRCLES — clarify, segment, needs, prioritise, solutions |
| Product strategy | Strategic thinking, business judgement | Market → goals → options → trade-offs → recommendation |
| Analytical / metrics | Data fluency, structured diagnosis | Metric-drop RCA; define success metrics from the goal |
| Estimation | Structured quantitative reasoning | Break into drivers; state assumptions; sanity-check |
| Behavioural | Past behaviour as a predictor; collaboration | STAR — Situation, Task, Action, Result |
| Technical | Working with engineering; technical literacy | Reason from fundamentals; show how you'd partner with eng |
| Prioritisation | Judgement under constraints | A prioritisation framework (RICE/value-effort); state criteria |
A PM preparing for interviews treated them as one undifferentiated challenge and practised improvising thoughtful answers. In the real interview, faced with a product-design question, they launched into strategy; faced with a behavioural question, they told a rambling, unstructured story. The answers weren't bad in content, but they didn't match what each question was testing, and they signalled a lack of the structured thinking interviewers specifically screen for.
Understanding the question types transformed their preparation. They learned to recognise each type in the first moments — design, strategy, analytical, behavioural — and apply its matching framework: CIRCLES for design, STAR for behavioural, a metric-drop RCA for analytical. The same person, now structured, demonstrated exactly the competencies each question was probing. Recognising the type first was the skill that turned good instincts into strong, structured answers.
The deliverable is the ability to recognise each question type instantly and apply its matching framework.
| When you hear… | Recognise & apply… |
|---|---|
| 'Design a product for…' | Product design → CIRCLES |
| 'Should we enter market X?' | Strategy → market→goals→trade-offs |
| 'A metric dropped — diagnose' | Analytical → metric-drop RCA |
| 'Tell me about a time…' | Behavioural → STAR |
PM interviews probe distinct competencies through distinct question types, and the meta-skill that underlies strong performance is recognising the type — because each rewards a specific structured framework, and using the right one is itself part of what's being assessed.
The reason type-recognition matters so much is that interviewers are largely assessing structured thinking, and applying the correct framework for a question type is a direct demonstration of it. Answering a product-design question with CIRCLES, a behavioural question with STAR, or an analytical question with a metric-drop RCA shows you can recognise a problem's shape and bring the right structure to it — which is exactly the PM skill in miniature. Conversely, improvising thoughtfully but without structure, or applying a strategy framework to a design question, signals that you can't read what's being asked and respond systematically. So the preparation isn't memorising answers — it's learning the types, internalising a framework for each, and practising the recognition that lets you reach for the right one under pressure. This is the index to the specific interview tools that follow (STAR, the metric-drop RCA).
Each type rewards a different framework. Recognise the type first.
A design framework for strategy signals confusion. Match framework to type.
Use STAR for structure, not a rambling story.
Identify the competency each question probes, and demonstrate it.
This catalogues the types; STAR (Tool 25) and the metric-drop RCA (Tool 26) are specific frameworks for two of them.
Design and prioritisation questions use frameworks from Module 1 (Tools 04, 11).
Strategy questions draw on Module 2's strategic tools.
Recognising types and applying frameworks shows the structure interviewers screen for.
AI is a genuinely effective interview-prep partner across every PM question type — practice on demand.
The judgment that stays yours: AI practice builds fluency, but interviews assess your structured thinking under pressure — leaning on AI to generate answers you don't understand will show. Use it as a sparring partner, not a script.
Take three sample interview questions ('design a product for X', 'a metric dropped, diagnose it', 'tell me about a conflict you handled'). Identify each one's type and the framework you'd use.
Notice how reaching for the wrong framework — or none — would weaken each answer.
If recognising the type instantly pointed you to the right framework for each, you've internalised the meta-skill that underlies strong interview performance: read the question's shape before answering.