PM Interview Cheat Sheet
(2026 Edition)
5 openings, 5 transitions, 5 closings, 8 frameworks, and 6 red flags — everything on one page.
Make Daily Practice Your Habit — Free →5 Openings for Common Question Types
Product design question
'Before I propose solutions, let me make sure I understand the scope. [Clarifying question]'
Metric drop question
'Let me rule out data issues first, then segment to find where the change lives.'
Behavioural / STAR
'Let me walk you through a specific moment. At [Company], in [quarter]...'
Strategy / market entry
'Let me clarify the strategic intent first. Are we optimising for [A] or [B]?'
Estimation
'Let me walk you through my assumptions — I'd rather show structure than guess a number.'
5 Transitions to Signal Structure
'Now that I've defined the user, let me propose 3 solutions...'
'Before I pick my recommendation, let me walk through the trade-offs...'
'Let me check if my metric choice makes sense — I want to move [X] because [Y]...'
'Given my confidence level here, I'd want to validate with [research or test] before committing...'
'To make sure I'm answering your question, let me summarise what I've said and ask if this is on track...'
5 Closings That Land
'To summarise: user is X, problem is Y, recommendation is Z, success metric is W.'
'What I'd do differently with more information: validate [assumption] through [method].'
'Two risks to flag: [risk 1] and [risk 2]. Mitigations: [plan].'
'Is there a specific dimension you'd like me to go deeper on?'
'What I'd NOT do and why: [explicit non-goal].'
8 Frameworks to Know Cold
RICE: Reach × Impact × Confidence ÷ Effort
JTBD: When [situation], I want [motivation], so I can [outcome]
AARRR: Acquisition → Activation → Retention → Referral → Revenue
CIRCLES: Comprehend → Identify → Report → Cut → List → Evaluate → Summarise
STAR: Situation → Task → Action → Result (10/10/60/20 time split)
HEART: Happiness / Engagement / Adoption / Retention / Task success
MoSCoW: Must / Should / Could / Won't
SBI: Situation → Behaviour → Impact (feedback)
6 Red Flags to Avoid
Using 'we' when asked about YOUR impact
Naming frameworks instead of applying them
Skipping user definition to jump to solutions
Vague metrics ('improve engagement' vs 'D7 retention 22%→28%')
Claiming certainty when you're uncertain
Generic questions at the end ('what's the culture like?')
FAQ
How should I use this cheat sheet?
Review it the night before your interview. Don't try to memorise — the goal is to recognise the patterns. During the interview, you shouldn't be thinking 'now I'll use the opening from the cheat sheet' — you should be naturally using the structure. If you're still thinking about it in-interview, you need more practice, not more reading.
What's the single most important thing to remember in a PM interview?
Start with the user, not the solution. Every product sense question, strategy question, and metric question improves when you first define 'who is this for and what do they need?' Skip this step and even good answers feel generic. Start here and even average answers feel strong.
Make Daily Practice the Habit Before Interviews
2 minutes a day turns these patterns into instinct.
Start Free Trial →