The Compelled-to-Work-on-It PM Interview
Hire PMs by testing whether their story makes YOU want to go work on their boring old problem.
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 88%
Yamashita's PM hiring bar is mostly storytelling under pressure, tested through three specific probes. He asks candidates to describe a controversial product decision — watching whether they can construct the conflict, argue both sides fairly, and stay even-keeled. He asks them to describe a big problem they worked on, and applies a single internal test: coming out of it, do I feel compelled to work on that problem? And he probes for 'high-bandwidth UX conversations' — the ability to move fast up and down the solution tree, and to fast-forward to a future outcome so you can skip the work that won't change your mind.
Origin
The fast-forwarding probe comes from Jeff Holden, Uber's first Chief Product Officer, who often talked about pretending you had already run the experiment or the user study and asking what it would come back with. The controversial-decision and compelled-to-work-on-it questions are Yamashita's own, and follow from his conviction that storytelling is the PM's central job.
Core principles
- 01Nearly all of the PM job is storytelling and communication, so interview for it directly.
- 02A great PM can make any problem sound worth working on — even a boring one.
- 03Representing both sides of a conflict fairly is evidence of the perspective-taking the job requires.
- 04Speed up and down the solution tree beats depth at one altitude.
- 05The best PM shortcut is deciding NOT to build something.
How to run it
- 1
Ask for a controversial product decision
Ask the candidate to describe a time they were part of a controversial product decision and what they did. Score whether they can set up the conflict, explain why the problem mattered, and represent both sides well enough that you understand why the conflict existed at all.
Pro tip Watch for even-keeled delivery — a candidate who can genuinely hold both perspectives is the signal.
Watch out A candidate who can only narrate their side won't be able to take on other perspectives on the job either.
- 2
Ask about a big problem — and check if you now want to solve it
Have them describe a big problem they worked on. The scoring test is entirely internal: coming out of that conversation, do you feel compelled to work on that problem?
Pro tip The test holds no matter how boring the problem sounds on the surface. A great PM can cast an unglamorous problem so that you want in.
- 3
Probe for high-bandwidth UX conversations
Talk through a real problem and its solution tree. Look for candidates who can move up and down branches quickly and command multiple altitudes at once, so that you walk away from the conversation with actual progress.
- 4
Test fast-forwarding to the future
Pose a hypothetical: pretend we ran that experiment — what do you think it comes back with? Pretend we ran that user study — what do we learn? PMs who can imagine outcomes make the whole team more efficient.
Pro tip The payoff is negative decisions: if we all think it'll go there, and that result wouldn't compel us to act, why run it at all?
Watch out This is an imagination test, not a prediction test — it requires the ability to see around corners, not to be right.
In the wild
Uber's first Chief Product Officer, Jeff Holden, would routinely ask the team to pretend they had already run the experiment or the user study and to say what it would come back with.
→ When the imagined result wouldn't change the decision, the team skipped the work — making them substantially more efficient and, per Yamashita, proving that a lot of the PM job is knowing which shortcuts to take and when to decide NOT to build something.
Figma runs a strikingly small product org — roughly 22 product managers at the time of the interview — so the bar per hire is extremely high, and Yamashita weights it toward storytelling and communication rather than domain trivia.
→ The interview loop centers on the controversial-decision question and the compelled-to-work-on-it test, because in his view so much of the job comes down to that skill.
Common mistakes
Interviewing for frameworks instead of narrative
If almost the whole job is synthesis and storytelling, a loop built on process trivia and metric definitions is measuring the wrong thing. Yamashita's questions all measure whether the candidate can make you see and care.
Reading a one-sided conflict story as conviction
A candidate who narrates a controversial decision as a story where they were simply right, and the other side simply wrong, has failed the actual test — which is whether they can hold and articulate both perspectives.
Is it for you?
Best for
Hiring managers building small, senior product teams where each PM must operate autonomously and carry the narrative for their area.
Not ideal for
High-volume junior hiring where candidates have no substantial prior product conflicts to draw on, or heavily technical PM roles where domain depth is the binding constraint.
From the transcript
“if they can kind of like set up this conflict and understand like why this problem is really important and represent both sides and such…”
“the thought experiment for me is always like coming out of that do I feel compelled to work on that problem right”
“Jeff Holden was someone who often talks about kind of fast forwarding to the Future and this idea that you know okay like let's just…”
From the episode
An inside look at how Figma builds product
Yuhki Yamashita (CPO of Figma)