The PM Interview and Hiring Guide
How PMs actually get evaluated, written for both sides of the table. If you're interviewing, this tells you what each round is really testing. If you're hiring, this is the loop I run and what I weight. It maps directly onto The PM Competency Model, because a good loop is just the competency model turned into questions.
Every question is a proxy for one judgment: would I trust this person with an ambiguous problem and a team, and would the team be glad they did? That's competence and character. I'll take a slightly less polished PM with great judgment and integrity over a slick one I don't trust, every time. See Character, Competency, and Craft.
#The four standard rounds
Most strong PM loops break into four evaluations. Here's what each tests and where it lives in the model.
| Round | What it tests | Competency mapping |
|---|---|---|
| Product Sense | Can you reason about users, value, and what makes a product good? "Design X for Y" / "improve product Z." | Voice of the Customer · User Experience Design · Product Sense and Judgment |
| Execution | Can you actually ship? Trade-offs, scoping, decisions under constraint, "your launch is slipping, what do you do?" | Feature Specification · Product Delivery · Product Quality |
| Analytical / Metrics | Can you reason with data? Pick a metric, diagnose a drop, size an opportunity, design an experiment. | Fluency with Data · Business Outcome Ownership |
| Behavioral / Leadership | How do you work with people? Conflict, influence, stakeholder and exec stories. | Stakeholder Management · Managing Up · Team Leadership |
A fifth thread, strategy, gets its own round for Senior+ roles: "what's the strategy for this product, and why?" That's Strategic Impact and Product Vision and Roadmapping.
#What "good" looks like in each round
Product sense. I'm not looking for your favorite feature. I want to see you anchor on a user and a job (Jobs To Be Done), generate options, and make a defensible choice with a clear "why." The tell of a strong PM is they ask who the user is before designing anything, and they say what they'd cut.
Execution. I want concrete instincts about trade-offs and a bias to clarity. Strong answers name the outcome first, scope ruthlessly, surface risk early (Risk Identification and Mitigation), and communicate the call cleanly. Weak answers add process or escalate instead of deciding.
Analytical. I want structured thinking, not memorized metrics. Pick a metric and justify it; when diagnosing a drop, segment before you guess; know the difference between leading and lagging indicators and between correlation and causation. "I'd look at the data" is not an answer.
Behavioral. I want specific, first-hand stories: the situation, your action, the result, and what you'd do differently. Vague "we" answers and rehearsed perfection both worry me. The best signal is a candidate who can name a real failure and what they learned. This mirrors how I run a review: first-hand evidence, never rumor.
#What I look for beyond the rubric: character
The competencies are the competence half. The half that decides my yes is character, and I probe it deliberately:
- Humility and self-awareness. Can they name their shape honestly? Do they say "I was wrong"?
- Integrity. Do they take credit they didn't earn? Do their stories make every colleague a villain?
- Curiosity. Do they ask me good questions about the user and the business?
- Resilience and decisiveness. How do they talk about a setback? Can they decide with incomplete information?
- Empathy. For users and for the engineers and designers they'll work with daily.
These are the hardest things to teach (the bottom of Character, Competency, and Craft), which is exactly why I hire for them and coach the rest.
#How the loop maps to leveling
The bar isn't pass/fail. It's at what altitude. An APM candidate should reason well about a feature; a Senior candidate should reason about an area and influence without authority; a leadership candidate should set strategy and build teams (Hiring and Building a Product Team). Calibrate the same answer against the level you're hiring for (see The Master Competency Matrix and Calibration and Promotion).
Borrow the appraisal discipline from Running a Performance Review: evaluate against job-related signal, use first-hand evidence, give every interviewer a clear competency to assess (don't have four people all test "product sense"), and debrief on evidence, not gut. Bias toward a diverse, holistic, evidence-based decision, not the candidate who's most like you.
#Continue Reading
- The PM Competency Model for the rubric every round is derived from.
- Character, Competency, and Craft for why I hire for character and coach the rest.
- Hiring and Building a Product Team for the manager's view: building the bench, not just one hire.
- Frequently Asked Questions for "how do I break into PM?" and other candidate questions.
- Product Sense and Judgment for the competency the hardest round is really testing.