The Prep-Call PM Interview Loop
Coach the candidate before their final presentation — how they use your feedback is the real signal
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 95%
Melissa Tan's four-stage process for hiring product managers, built around one unusual move: before the final presentation, she runs a prep call where she reviews the candidate's draft and gives them real feedback. The presentation itself matters less than whether they incorporate the feedback — that simulates working together. The loop opens with live problem-solving on the company's actual live product, which she says weeds out the most people.
Origin
Developed by Melissa Tan across hiring at Dropbox and Webflow. The live 'pull up our website, what would you test?' screen is a trick she explicitly learned at Dropbox.
Core principles
- 01Interviews should simulate collaboration, not performance
- 02Problem-solve on the real product, not a hypothetical case
- 03Ask why repeatedly — the reasoning is the signal, not the answer
- 04Setting the candidate up for success is not cheating; it is the test
- 05Cap the workload: a week of lead time, an explicit slide ceiling, substance over polish
How to run it
- 1
Hiring-manager screen with live problem-solving
In the first screen, pose a live problem tied to the actual role ('how would you approach pricing?'), then ask the candidate to open your live product or pricing page and say what they would change and why. Dig into the why relentlessly.
Pro tip Ask candidates to have a laptop open. Watching them react to your real surface in real time surfaces thinking quality no prepared case study can.
Watch out This screen is the highest-attrition stage by design — it weeds out the most people, so run it before you spend panel time.
- 2
Competency panel
Route the candidate to several team members, each assigned one distinct competency to test (technical depth, cross-functional stakeholder work, etc.) based on the specific role. No two interviewers cover the same ground.
- 3
The prep call
Schedule the presentation about a week out on a topic drawn from the company's real problem — often 'what would you do in your first 90 days?' Then hold a prep call where you answer their data questions, walk their draft, and give substantive feedback ('lean in heavier here'; 'we're thinking about XYZ, consider incorporating it').
Pro tip Set an explicit slide ceiling (Webflow used 'no more than 30, we do not expect 30') and tell them you're grading substance, not deck craft.
Watch out A week is deliberate — long enough to build, short enough that they don't sink days into it. Be mindful this is a big ask; the prep call is partly how you repay it.
- 4
Presentation — grade the delta, not the deck
Run roughly a 30-minute presentation plus Q&A. The decisive question is whether and how they incorporated your prep-call feedback into the final version. Candidates who ignore all of it are a no.
Pro tip Also read whether they actually used the product during the process. A candidate who never got into the product can't know if they'd like the work.
Watch out Don't have candidates present past work instead — they burn the session explaining a company you don't know and you learn nothing about how they'd think about yours.
In the wild
Tan would ask 'how would you approach pricing?', then ask the candidate to pull up Webflow's live pricing page and say what they'd change. In the prep call for the final presentation, she'd tell them what Webflow was actually considering and suggest they work it in.
→ She gets direct signal on what working with the person is like; candidates who did not incorporate any feedback were read as not a fit.
Common mistakes
Asking candidates to present past work
Tan tried this format and found candidates spend most of the time setting up context on a company you don't know, and it fails to test how much they absorbed about your business or whether they'd enjoy the actual problem.
Treating the prep call as giving away the answer
Helping the candidate is the point. The information asymmetry you remove is repaid by the signal you gain — you learn how they take feedback, which is the single hardest thing to test in a normal loop.
Is it for you?
Best for
Hiring managers running PM, growth, or senior IC loops who keep hiring people who interview well and work badly
Not ideal for
High-volume junior hiring or roles where the loop must stay identical and low-touch for legal/scale reasons
From the transcript
“I always have a presentation component to the interview process that checks for prepared thinking, communication, and I recommend a prep call between the two…”
“Usually, you know, hiring manager screen and I actually do the live problem-solving at this screen. I actually think it weeds out the most people.”
“That was a trick I learned at Dropbox where we would actually pull up the Dropbox website and be like, "Hey, what do you want…”
“Typically, we will schedule it about a week in advance. They have a week.”
“In Webflow's case, we've done like don't exceed more than 30 slides and that's like quite a lot.”
From the episode
Building high-performing teams
Melissa Tan (Webflow, Dropbox, Canva)