Hiring PMs
You have an open PM role and a stack of resumes. The hard part is not sourcing candidates — it is figuring out, in roughly three hours of interviews, whether someone can actually do the job. Product management is notoriously difficult to evaluate because the work is ambiguous, the outputs are shared with the team, and the best PMs often look nothing like each other on paper. Here is how the guests who have hired hundreds of PMs approach it.
What You Are Actually Evaluating
Petra Wille, product leadership coach and author of Strong Product People, who has coached over 130 product leaders one-on-one, emphasizes that the first step is having a clear definition of what good looks like: “A lot of the product leads that I’m working with have this as an implicit feeling-based, experience-based thing. They can talk about some of the aspects, but it’s often the case that they have not fully reflected on what personality traits I want to see in product people that are hard to develop while I’m coaching them, and what are skills, and know-how, and capabilities.” Without this explicit competency model, every interviewer evaluates against their own implicit standard — and those standards diverge. PM evaluation breaks into four core dimensions. Every interview loop should cover all four, with each interviewer owning one or two:
| Dimension | What It Means | How to Test |
|---|---|---|
| Product sense | Can they identify the right problem and propose a compelling solution? | Product design question: “How would you improve X?” |
| Analytical ability | Can they structure ambiguous data and draw the right conclusions? | Metric diagnosis: “Feature X launched and DAU dropped 5%. Walk me through your investigation.” |
| Execution | Can they ship? Do they understand the mechanics of getting a cross-functional team to deliver? | Behavioral: “Tell me about a project where you had to ship without full stakeholder alignment.” |
| Communication and influence | Can they bring engineers, designers, and leadership along without authority? | Observed throughout all interviews, plus a presentation round if senior |
The weighting shifts by level. For an APM or PM, product sense and analytical ability matter most — you are hiring for potential. For a senior PM or Group PM, execution and influence dominate. As Ken Norton, former Google PM leader who led teams that built Google Docs, Google Calendar, and Google Maps, puts it: “Part of what I think is pretty exciting about product management is you are a leader from day one in product management. You don’t have any formal authority, but you’re a leader.” At senior levels, the question is not whether they can think well — it is whether they can make an organization move without that formal authority.
The Interview Format Debate
There are three dominant formats for PM interviews. Each has tradeoffs, and the best companies often combine two.
Take-Home Exercises
The candidate receives a product problem — sometimes based on the actual product — and has 3-5 days to produce a written analysis or presentation.
Strengths: Tests written communication, depth of thinking, and how a PM actually works (not just how they perform under time pressure). Melissa Tan, former head of growth at Dropbox and Webflow, uses a distinctive variation: she gives candidates a preparation call before the final presentation where she provides feedback on their draft and shares additional context. “What this gives me signal on is what is it actually going to be like to work together. And then I see how they incorporate it into the final product and that is always really interesting and sometimes it’s the biggest signal to what it’s going to be like to work with this person.”
Weaknesses: Biases toward candidates with free time. Parents, people with demanding current roles, and candidates interviewing at multiple companies are disadvantaged. Some candidates outsource the work.
When to use: Senior and Group PM roles where written communication is critical. Pair with a follow-up presentation to verify the candidate actually did the work.
Live Case Studies
The interviewer presents a product scenario and the candidate works through it in real time. “You are the PM for Google Maps. Usage in rural areas is 60% lower than urban. What would you do?”
Strengths: Tests product sense and structured thinking under pressure. Allows the interviewer to probe, redirect, and see how the candidate responds to pushback. Tan uses live problem solving in her hiring manager screen specifically because it weeds out the most candidates: “I would ask, ‘How would you approach pricing?’ I sometimes would say, ‘Hey, do you have your laptop? Can you pull up our pricing page? Curious to get your thoughts, what would you want to change?‘”
Weaknesses: Favors candidates who have practiced case frameworks. Does not reflect how PMs actually work — no PM solves a problem in 30 minutes with zero data. Can feel like a performance rather than a conversation.
When to use: Entry-level to mid-level PM roles. Best used as one signal among several, not the deciding factor.
Behavioral Interviews
“Tell me about a time when…” questions that probe past experience.
Strengths: Past behavior predicts future behavior better than hypothetical scenarios. Jeremy Henrickson, SVP of Product at Rippling and former CPO at Coinbase, uses behavioral interviews as the primary signal for execution and influence dimensions. At Rippling, the interview process is deliberately short and grounded in the actual business: “A prompt should always reflect the actual business that they’re going to come into.”
Weaknesses: Candidates can prepare polished stories that exaggerate their contribution. Cross-referencing with references is essential.
When to use: Every PM interview loop should include at least one behavioral round.
Recommended Loop Structure
| Round | Format | Duration | Evaluates |
|---|---|---|---|
| Screen | Behavioral + motivation | 30 min | Communication, career trajectory, role fit |
| Round 1 | Live case study (product design) | 45 min | Product sense |
| Round 2 | Analytical / metrics diagnosis | 45 min | Analytical ability |
| Round 3 | Behavioral deep-dive | 45 min | Execution, influence, collaboration |
| Round 4 (senior only) | Take-home presentation + Q&A | 60 min | Written communication, strategic depth |
Evaluating Product Sense in 45 Minutes
Product sense is the dimension most teams struggle to assess. Here is a rubric:
Strong signals:
- Starts with the user and the problem, not the solution
- Asks clarifying questions about the target user, context, and constraints before proposing anything
- Prioritizes among possible solutions using a clear framework (impact, feasibility, alignment with company goals)
- Considers edge cases and second-order effects without being prompted
- Articulates tradeoffs rather than presenting a single “right answer”
Weak signals:
- Jumps immediately to a feature list
- Proposes solutions that are technically interesting but do not connect to a user problem
- Cannot prioritize — everything is “important”
- Treats the exercise as a creativity test rather than a decision-making exercise
Henrickson adds a practical expectation from Rippling’s culture: “In product, you don’t own a little feature, you own your product and you’re expected to be the world’s foremost expert in it. And if you are, what that means is instead of having to come back to people three days later with an answer, just off the top of your head, you can be like, ‘Yes, this is what I think I should do about that.‘” The best PMs can argue persuasively for a solution and then explain, without discomfort, why it might be wrong. That is the difference between conviction and stubbornness.
Red Flags Across the Loop
Patterns that experienced PM hiring managers watch for:
| Red Flag | Why It Matters |
|---|---|
| Cannot name a specific metric they moved | Suggests they were adjacent to impact, not driving it |
| Credits themselves for team accomplishments without acknowledging the team | PMs who cannot share credit will not retain engineers |
| Describes every past project as a success | Either lacks self-awareness or is selectively presenting. Push for a failure story. |
| Uses jargon without substance (“we leveraged synergies to drive engagement”) | Masks shallow thinking |
| Cannot explain why they left their last role clearly | Not necessarily disqualifying, but probe further |
| Shows no curiosity about your product during the interview | If they did not prepare, they will not prepare for the job |
Melissa Tan highlights a meta-signal she screens for across the loop: a growth mindset. “I tend to look for folks that have a growth mindset. There are people that are wanting to learn. They’re looking for feedback. They take feedback well.” She views the interview as the beginning of a development relationship, not just a gatekeeping exercise — and candidates who demonstrate coachability in the interview process tend to outperform those who present a polished but rigid front.
Closing the Loop: References and Calibration
The interview is necessary but insufficient. Claire Hughes Johnson, former COO at Stripe, emphasizes the importance of early hiring rigor: “The first thing you’re probably putting in place is a little bit of hiring process, and I think that’s going to matter sooner than you think. Don’t just be tempted to hire people in your friends. Think about what you need, what capabilities you need to build.” Structured back-channel references — not just the references the candidate provides, but people you find through your network who worked with the candidate — add signal that the interview alone cannot provide.
Calibration across interviewers matters. Before the debrief, every interviewer should submit their rating independently. If you discuss first, anchoring bias takes over and the loudest voice wins. Written independent evaluations, then discussion — in that order.
Key Takeaway
- Structure your loop to cover all four dimensions: product sense, analytical ability, execution, and communication. Assign each interviewer a primary dimension so nothing is missed.
- Combine formats — behavioral interviews for execution, live cases for product sense, take-homes for senior roles. No single format tests everything.
- The strongest signal for senior PMs is not how they think about products. It is whether they can make an organization move. Weight execution and influence accordingly.
Related
- Product Sense — The hardest dimension to evaluate and develop
- One-on-Ones — How to develop the PMs you hire
- Performance Reviews — Evaluating PM performance after they join
- Product Culture — The environment your new PM hire will operate in
Sources
- Petra Wille on coaching product people — Competency model for PMs, eight-legged creature metaphor, five ingredients for PM coaching, development plan over assessment
- Melissa Tan on building high-performing teams — Preparation call interview technique, live problem solving in screens, growth mindset as hiring signal, developing talent over external hiring
- Jeremy Henrickson on moving fast and navigating uncertainty — Interview prompts reflecting actual business, domain expertise expectation, speed of decision-making culture at Rippling
- Ken Norton on product leadership skills — Leadership from day one, people-pleasing PM archetype, reactive vs. creative leadership, redefinition of leadership style
- Claire Hughes Johnson on scaling Stripe — Early hiring rigor, capability-based hiring, structured hiring process as organizational foundation