Scenario-Based PM Interviewing
Interview PMs by making them do the real job under real constraints, not recite prepared stories
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 88%
A contrarian hiring approach for product managers. Instead of asking about work history and rehearsed 'tell me about a time' answers, Winters gives candidates real scenarios from the actual role and watches whether they can generate reasonable ideas and cheap ways to test them without analyst or research support.
Origin
Casey Winters' interviewing method, refreshed while helping the startup Whatnot hire early-career PMs after years away from interviewing.
Core principles
- 01Interviewing has become performative — most PMs are better PM interviewers than PMs
- 02The best signal is watching a candidate do the actual job you're hiring for
- 03You want people who use their brain under uncertainty, not who follow someone else's process
- 04Interviewing is a lossy format — maximize how much real work you observe
How to run it
- 1
Skip history and rehearsed answers
Don't ask about work history or perfectly practiced behavioral answers. Winters: 'I don't ask about your work history, I don't care about your perfectly practiced answers.'
Watch out Beware that interviewing 'has gotten so performative, it's like handing out Oscars based on who's prepared the best.'
- 2
Give a real scenario from the role
Present a genuine problem the role will face, then withhold the data and customers: 'you don't have the data, you can't talk to customers, make a decision now, what would you do?' Watch creativity and how much they intuit about the real problem and solution.
Pro tip Use a presentation or a live prompt so you see them work, not describe work.
- 3
Test whether they can cheaply test ideas
Require them to figure out how to test a few reasonable ideas quickly without analyst support or research. If they can't, pass.
- 4
Watch for time-horizon and metric red flags
Downgrade candidates who propose solutions needing months of engineering before any signal, who ignore time-to-signal, or who don't consider which metrics they expect to improve versus which they must guard against regressing.
Watch out A candidate saying 'I can't even begin to answer this without research and data' is a red flag for the constrained-startup context.
In the wild
Winters asks candidates to solve a problem; when they say they need all the data and customer calls first, he removes those and pushes: 'make a decision now, what would you do? I want to see how creative you are.'
→ Separates PMs who can operate under uncertainty from those who only execute a predefined process.
Common mistakes
Rewarding preparation over capability
Optimizing interviews for polished 'tell me about a time' answers selects for great interviewers, not great PMs who can actually do the job.
Ignoring time-to-signal in a candidate's plan
A candidate who proposes months of engineering before any user or business signal, without accounting for that time cost, signals poor judgment for a resource-constrained team.
Is it for you?
Best for
Hiring managers recruiting product managers for startups or public startups where PMs must decide under uncertainty and wear many hats
Not ideal for
Roles inside large, resource-rich orgs where the job genuinely is executing established process with full analyst and research support
From the transcript
“I'm going to give you real scenarios that I expect from the role I want to hear how you'd approach them and if you can't…”
“you don't have the data you can't talk to customers make a decision now what would you do I want to see how creative you…”
“it's like interviewing is handing out Oscars based on who's prepared the best”
“if they're talking about solutions that are going to take a long time to get signal from”
From the episode
Thinking beyond frameworks
Casey Winters (Pinterest, Eventbrite, Airbnb, Tinder, Canva,