PM interviews feel intimidating because they're open-ended — but they're not random. They test a known set of competencies through recurring question types, and the candidates who succeed aren't the most brilliant; they're the ones with a structure for each type and the practice to apply it calmly.
The question types
- Product design / sense — "Design a product for X" or "improve product Y." Tests user empathy and structured creativity.
- Analytical / metrics — "What metrics for Z?" or "diagnose this drop." Tests reasoning with data.
- Estimation — "How many X in Y?" Tests structured quantitative thinking, not the exact number.
- Strategy — "Should company A enter market B?" Tests business judgement.
- Behavioural — "Tell me about a time…" Tests how you actually work, influence, and handle conflict.
Interviewers care far more about how you reason than whether you reach their preferred answer. Structure visibly; think out loud.
Structure is the skill
For each type there are well-known frameworks (for product design, approaches like CIRCLES: comprehend, identify the user, report needs, cut/prioritise, list solutions, evaluate, summarise). The framework matters less than having one — it stops you rambling, ensures you cover users before solutions, and lets the interviewer follow your thinking. Memorise a structure per type, then make it feel natural.
The mistakes that sink candidates
- Jumping to a solution before establishing who the user is and what problem you're solving.
- No structure — a stream of consciousness the interviewer can't follow.
- Ignoring trade-offs — real PM is prioritisation; pretending everything's possible signals inexperience.
- For behavioural: vague stories — use a clear situation-action-result arc with your specific contribution.
Practice out loud
Reading about frameworks isn't enough; the gap between knowing and performing under pressure closes only with spoken, timed practice — ideally with feedback. The fluency that reads as "natural PM thinking" is rehearsed.
