Free Scorecard · IC / Senior / Lead

PM Hiring
Scorecard.

A calibration rubric for product manager hiring. Six competencies, behavioral signals at each level, anti-pattern flags.

Role: ______
Hiring Mgr: ______
Date: ______

The framing problem

Most PM interview disagreements aren’t about the candidate — they’re about uncalibrated levels. One interviewer is grading against a Senior bar, another against an IC bar, and the debrief turns into a personality contest. This rubric removes that disagreement: same six competencies, three explicit levels, behavioral signals tied to evidence in the interview transcript. Disagreement becomes "I saw signal X, you saw anti-pattern Y" — a conversation you can actually finish.

The 6 competencies

Strategy & Vision

Connects work to a defensible "why" and a measurable outcome.

Execution & Delivery

Ships outcomes — not just output — through ambiguity and dependencies.

Customer Obsession

Operates from real customer evidence, not internal opinion or anecdote.

Communication & Influence

Aligns engineering, design, sales, and exec without authority.

Technical Depth

Reads architecture well enough to make sound trade-off decisions.

Leadership & Coaching

Raises the people around them; scales themselves through others.

IC PM rubric (Junior–Mid)

Meets bar · IC PM

Strategy & Vision

Ties their feature to a single team-level metric and explains why that metric was chosen Names one tradeoff they consciously made (e.g., scope vs. timeline) Can articulate the user problem in one sentence without jargon Flag: talks about strategy in abstract terms but can’t tie it to a metric or a customer

Execution & Delivery

Has shipped at least one full feature end-to-end, including the unsexy follow-up work Describes a specific scope cut they made under pressure and the data behind it Names dependencies they unblocked themselves Flag: uses "we" for everything — can’t isolate their personal contribution

Customer Obsession

Has talked to real customers in the last 30 days — can quote one References at least 2 distinct feedback sources (support, reviews, sales calls, etc.) Can describe a feature they killed because customer evidence didn’t support it Flag: says "users want X" with no evidence chain when pressed

Communication & Influence

Writes a clean problem statement live during the case study Asks clarifying questions before answering ambiguous prompts Describes a disagreement they navigated with one specific engineer or designer Flag: presents conclusions without showing the reasoning — pure storytelling

Technical Depth

Knows the architectural shape of their product (services, data flow, key constraints) Can explain one tradeoff between approaches engineering proposed Reads a basic API spec without help Flag: defers to engineering on every technical question without curiosity

Leadership & Coaching

Has mentored an intern, peer, or first-week teammate — even informally Asks for feedback explicitly and acts on it Describes a mistake they own without externalizing Flag: blames previous team / manager / engineering for every failure story

Senior PM rubric

Meets bar · Senior PM

Strategy & Vision

Owns a multi-quarter thesis with a measurable north star and stated assumptions Has killed a major investment based on data and recovered the team Articulates the competitive landscape and why their bet beats the alternatives Flag: "vision" stories that read as roadmaps with no underlying belief

Execution & Delivery

Has shipped through at least one cross-team dependency that almost derailed delivery Runs the team’s own operating cadence (standup, planning, review) and explains why Quantifies the outcome of a launch — not just shipped/not shipped Flag: ships features but can’t name the metric movement after launch

Customer Obsession

Has built a recurring system for customer signal — not ad hoc interviews Has changed a roadmap commitment because of unexpected qualitative evidence Distinguishes loud customers from representative customers Flag: over-indexes on the largest customer or the loudest internal voice

Communication & Influence

Has flipped a senior stakeholder’s decision with evidence — respectfully Writes narratives, not bullet decks, when the stakes are high Pre-aligns key stakeholders before the meeting where decisions get made Flag: wins arguments by volume or seniority, not by evidence

Technical Depth

Pushes back on architecture decisions when product timelines or UX are at risk Understands the tradeoff between technical debt and shipping speed for their domain Can hold their own in a design review with platform engineers Flag: performs technicality (jargon, name-drops) without depth on their own product

Leadership & Coaching

Mentors at least one junior PM or PM-adjacent peer — without being asked Has run a retrospective that resulted in a system change, not just a vibe shift Names what they’re actively bad at and what they’re doing about it Flag: "I lead by example" — no concrete coaching evidence

Lead PM / Group PM rubric

Meets bar · Lead / Group PM

Strategy & Vision

Sets the multi-team product strategy — with explicit "we are not doing X" statements Has defended a strategy against a board, exec team, or major customer and held the line with evidence Connects strategy to company-level objectives and pricing/positioning, not just product metrics Flag: strategy is a list of features, not a set of bets with disconfirming evidence

Execution & Delivery

Has shipped across 2+ teams in parallel and managed the cross-team operating model Knows when to centralize a decision vs. push it down to the IC PM Has navigated a public miss — recovery plan, transparent comms, learnings Flag: still operating like an IC PM with bigger scope — doing the work, not enabling it

Customer Obsession

Has built or scaled a customer signal system across multiple PMs and segments Distinguishes between segment-specific and product-wide signal Coaches PMs on the difference between research and confirmation bias Flag: outsources customer contact to the IC PMs entirely

Communication & Influence

Operates fluently with VP/CXO peers across functions Has set the narrative for a product re-launch or repositioning across the company Manages up effectively — gives the CEO/CPO the right answer in the right format Flag: performs gravitas; can’t actually translate strategy into something the team can execute

Technical Depth

Holds an opinion on platform-level architecture choices (build vs. buy, monolith vs. service) Has worked with engineering leadership on a technical strategy that enables product strategy Reads incident postmortems for product implications, not just engineering ones Flag: leaves all technical strategy to the engineering lead and is surprised by the consequences

Leadership & Coaching

Has hired and grown PMs — can name specific promotions they sponsored and what they coached on Has managed someone out and handled it with dignity and clarity Builds PM leverage — rituals, templates, calibration — not just heroics Flag: high personal output, low team output — the bottleneck is them

Interview question bank

Twelve questions, two per competency. Use 4–5 in any single interview. The "what good sounds like" notes are calibration cues for debrief, not scripts to read.

StrategyWalk me through a product bet you made. What was the underlying belief, and what would have changed your mind?

Good (IC): a single-feature bet with one assumption named. Senior: a multi-quarter bet with a disconfirming experiment. Lead: a strategy bet with explicit "not doing" choices.

StrategyWhat’s a feature your team built that you would not build again? Why?

Good: names the metric that didn’t move and the lesson that updated their judgment. Bad: blames adoption on marketing.

ExecutionTell me about the launch where the most went wrong. Walk me through your decisions, in order.

Good: ownership of specific calls, not generic "we learned." Senior+: a mid-flight scope cut with the data behind it.

ExecutionHow do you know when a feature is "done"? Walk me through your last launch’s definition.

Good: includes follow-up adoption metrics, support volume, and a "no-go" rollback plan — not just a ship date.

CustomerWhen did you last talk to a customer? What did they say — in their own words?

Good: recent (within 30 days), specific quote, names the segment. Anti: "our research team handles that."

CustomerA loud customer is asking for X. The data says Y is more important. Walk me through what you do.

Good: reframes loud-vs.-representative, brings the customer into a discovery conversation, doesn’t dismiss.

CommsTell me about a time you changed a senior stakeholder’s mind. What did you bring?

Good: evidence-led; pre-aligned key supporters; respectful disagreement on record. Anti: "I just kept pushing."

CommsHow do you communicate a missed deadline? Show me the actual message you’d send.

Good: specific, names the cause, names the new commitment, names what changed in the system.

TechPick a feature you shipped. Whiteboard the architecture as you understand it.

Good: data flow, key services, one tradeoff. Senior+: identifies the constraint that shaped the product decision.

TechWhen have you pushed back on engineering, and how did it land?

Good: respectful, specific, ended in a better decision — not a power struggle.

LeadershipWho’s the last person you coached, and what specifically did you teach them?

Good: named person, specific skill, observable change. Anti: "I’m always available to help."

LeadershipWhat’s feedback you’ve received recently that you disagreed with at first — and now don’t?

Good: specific feedback, named source, real behavior change. Anti: performative humility with no system change.

Case-study assignment template

Format: 60 minutes, async, take-home. Brief: "Here’s a one-page background on [our product] and a snapshot of customer signal across 3 channels (attached: 30 paraphrased customer quotes, app review summary, sales call themes). Pick the single most important problem to invest in next quarter. Write a one-page memo: problem, evidence, proposed bet, what you’d kill to make room for it, top risk."

Why it works: calibrates strategy (chose this over that), customer obsession (uses real signal), execution (kills something to make room), and communication (one page, defendable). It explicitly does not test design fluency or a wireframing skill the role doesn’t need.

Grading rubric (5 points each, 25 total): Problem framing · Evidence chain (cites the signal, doesn’t invent it) · Tradeoff (explicit cut) · Defensibility (would survive a hostile question) · Clarity (one page, no jargon).

Debrief script

The debrief is where calibration lives or dies. Run this in order — do not let people open with their gut feeling.

Hold scores until the room is in the room. No Slack pre-debrief. No "I already submitted my scorecard, FYI."
Each interviewer reads their scores out loud, one competency at a time, 1–5 — with one piece of evidence per score (a quote, a moment, a written artifact).
Anti-pattern flags surface next — any flag from the rubric, with the supporting evidence.
Identify the deltas. Which competencies have a 2-point spread or larger? That’s where the conversation is.
Re-listen to the evidence on deltas. Pull the quote. The disagreement is almost always "we heard the same words and graded them at different levels."
Hiring manager states the level call. Not "should we hire," but "are we hiring at IC, Senior, or Lead?"
Vote on the level call — and if there’s a level mismatch, that’s a different decision than a hire/no-hire.
Write the one-paragraph rationale. If you can’t write it cleanly, you don’t have consensus — keep going.

Common scoring traps

Anchoring on the loudest interviewer. The first opinion dominates the room. Counter: scorecards locked before the room talks.
Overweighting one bad answer. A weak answer on one question ≠ a weak competency. Look for the pattern across the loop.
Level inflation for "passionate" candidates. Energy is not the same as judgment. Charisma masquerades as Senior signal more than any other trait.
Conflating culture with capability. "I want to work with them" is not a hiring signal. "They will raise the bar of the next person we hire" is.
Rejecting for missing skills you can teach. SQL, framework knowledge, your specific tool — these are 4-week ramp items. Judgment, taste, and operating instinct are not.

Hiring decision rules

Outcome	Pattern
Hire at level	Meets bar on 5/6 competencies; 6th is "developing" not "anti-pattern"; no critical anti-pattern flags raised by 2+ interviewers.
Hire at lower level	Meets bar at the level below across all 6, with 2–3 reaching the higher bar. Make the offer at the level you’re confident in — never up-level on hope.
Hold for second loop	Strong signal on 4/6, but a critical anti-pattern (e.g., no customer evidence, externalizes failure) raised by exactly one interviewer with weak evidence. Targeted follow-up before deciding.
Pass	Two or more anti-pattern flags raised across the loop with evidence; or doesn’t meet bar on Customer Obsession or Execution at any level. These two are non-negotiable.

The non-negotiable rule: if you can’t write the offer rationale in one paragraph that survives the question "why this level?", you don’t have a hire. Take the day. Re-read the evidence. Decide tomorrow.