Hire a PM

To: Elif Demir, VP Product From: Director of Product Subject: PM interview loop: what the data says and what to change next quarter

What seems to predict performance

We have records for 52 final-round candidates, including 8 hires with 12-month ratings. Those hires averaged 3.5, versus a company PM average of 3.4; four were below 3.4, including two rated 2.

Among the eight hires, the clearest signal is the behavioural metric round. Its score has a strong positive association with 12-month ratings (exploratory Pearson r ≈ +0.93). The four hires rated 4–5 averaged 3.75 on this round, versus 2.5 for the four rated 2–3. This is promising evidence for probing how candidates actually move metrics and what they learn—not proof that the round is a reliable predictor.

The other scored rounds show no positive relationship with ratings in this small hired sample:

The negative estimates for presentation and VP Engineering should not be read as evidence that those skills hurt PM performance. With only eight hires, these figures are highly unstable. They do tell us that our current scores offer no reassuring evidence that those rounds predict success.

How confident we should be

Low confidence overall; modest confidence that the behavioural round is the best lead to investigate. Eight outcomes are far too few to set reliable weights or cutoffs, and interview scores are ordinal ratings, so the correlations are descriptive only. We also observe performance only for people we hired: panel decisions restrict the range of scores and can distort associations. Non-hires have no performance outcome for comparison.

We lack recruiter-screen scores, interviewer-level data, consistent evidence of scoring reliability, and context about role, manager, or rating differences. The company-average comparison is also a coarse measure. The data can guide a better experiment; it cannot establish causation or validate the loop.

Loop I’d run next quarter

1. Keep the recruiter screen for eligibility, motivation, and logistics, but don’t treat it as a predictive assessment. We have no screen-score data to evaluate.
2. Replace the week-long take-home deck and separate presentation with one time-boxed, job-relevant work sample. Use a live or short-prep product problem, not a polished deck. Score problem framing, user evidence, prioritization and tradeoffs, success measures, and communication against anchored criteria. This reduces candidate burden and stops us treating two related presentation exercises as independent evidence.
3. Keep and strengthen the behavioural round. Ask for a specific metric the candidate owned or influenced; probe the baseline, their actions, evidence of impact, attribution, tradeoffs, and what they learned. Use the same questions and anchored scorecard for every candidate.
4. Refocus the VP Engineering conversation on PM–engineering collaboration and concrete technical tradeoffs—not general “technical credibility.” Use a structured scenario and score it consistently; don’t make an unstructured impression a veto.
5. Have interviewers score independently before the panel discussion. The hiring manager can decide after reviewing evidence against the role criteria, with any disagreement recorded. Do not introduce numerical weights based on these eight hires.

For each of the four hires, preserve round-level scores and interviewer notes, then collect comparable 6- and 12-month outcomes with role and manager context. Review the evidence after the cohort has matured. Next quarter’s loop should be a more structured, lower-burden test—not a claim that we have already found a validated predictor.

To: Elif Demir, VP Product From: Director of Product Re: What in our PM loop predicts success, and the loop for next quarter's four hires

Bottom line

Of the four loop scores, only the behavioural round ("tell me about a metric you moved") tracks how PMs perform after hire. The take-home, the presentation and the VP Engineering conversation show no positive relationship, and the last two are negative among the people we hired. The sample is very small, so treat this as a strong lead rather than proof. I recommend making the behavioural evidence the anchor of the loop, shrinking the deck work, and turning the VP Eng conversation into a pass/fail check.

What we have

We have 52 final-round candidates: 9 hired, 33 rejected and 10 who withdrew. Only the 9 hires have 12-month ratings (company average 3.4). The three who struggled (C107, C132, C148) each scored 2, and C104 and C134 scored 3, also below average. All five below-average hires are the same kind of candidate: strong on the deck and the presentation, and scored 3–4 by the VP Eng.

What the data shows

Correlation with 12-month rating, among the 9 hires:

The behavioural pattern is clean. Hires scoring 4 averaged 4.7 (ratings 5, 5, 4), hires scoring 3 averaged 3.3, and all three hires scoring 2 were rated 2. Had we required a behavioural score of at least 3, we would have avoided all three struggling hires and kept every hire rated 3 or above. The pattern also holds within background: among the 4 Big tech hires, the one scoring 3 outperformed the three scoring 2, and among the other 5 hires the 4s outperformed the 3s.

The other three signals deserve less trust than the negative numbers suggest, for two reasons:

• Selection effects. We only see people we hired. If hiring managers pushed through candidates who were strong on the deck and the VP Eng score but weaker elsewhere, those scores will look negatively related to outcomes among hires even if they carry some real signal.
• The VP Eng score works as a gate. Every candidate scoring 1 was rejected or withdrew, so we have no outcome data on that group and cannot say whether the gate screens out good people.

Two further observations about the process:

• The take-home and presentation are the same artifact scored twice, so the deck gets double weight in the panel's discussion.
• Decisions look inconsistent. C135 (3/4/4/3) was rejected while C134 (4/4/3/3) was hired, and five candidates scoring 4 on the behavioural round were rejected. Three of those five had a VP Eng score of 1. With no written decision rule, we can't tell what drove these calls.

How confident we can be

• High confidence: the three struggling hires share one profile (Big tech, polished deck, VP Eng 4, behavioural 2), and our loop rewarded exactly those traits.
• Moderate confidence: the behavioural round carries real signal. The relationship is strong and consistent within subgroups, but it rests on 9 people and one outcome measure.
• Low confidence: any conclusion that the take-home, presentation or VP Eng conversation is useless. Selection effects and range restriction mean the data can't tell us either way. Our evidence only shows they haven't helped.
• Measurement problems:
• The 12-month rating comes from one source, likely the manager who chose the hire, so it may be biased toward justifying that choice.
• Behavioural scores and background are entangled: Big tech hires scored lower (2–3) than the others (3–4). I can't fully separate "behavioural score predicts performance" from "Big tech backgrounds fit us less well," though the within-group pattern favours the former.
• We have only a single 1–4 behavioural score per candidate, with no record of who scored it or how.
• Two or three outliers would change several of these numbers.

The loop I'd run next quarter

1. Recruiter screen. Keep it, with written criteria applied the same way for every candidate.
2. Two structured past-work interviews, replacing the single behavioural round. Different interviewers run them, each using a written rubric. They probe individual contribution versus team credit, the specific decisions the candidate made, what went wrong and what they would do differently, and how they worked with engineering. Interviewers score independently before any discussion. Two scores per candidate also lets us check whether the scoring is consistent.
3. Shorter work sample, replacing the one-week deck. Two to three hours, followed by a 30-minute live discussion, producing one combined score on a rubric. This cuts the double-counting and the candidate burden (10 of 52 withdrew). I'm keeping a work sample because we have no evidence it's useless, but it gets no more weight than any other single signal.
4. VP Eng conversation as a pass/fail risk check. The VP Eng answers one question: "Is there a specific, documented concern about this person's ability to work with engineering?" The 1–4 score no longer counts toward the decision, and a veto needs a written reason.
5. A written decision rule. A candidate must average at least 3 across the two past-work interviews to be eligible. Among those who clear that bar, the hiring manager decides and records the rationale against the rubric. This is a provisional threshold from 9 data points, so we should revisit it after this round.
6. Better outcome data. Run a structured 6- and 12-month review with defined criteria and a second reviewer, rather than a single manager rating, and log every candidate's scores in one place. Four hires bring us to 13 data points, still small, so decisions should stay modest in confidence until we have more.

What I'm not recommending

I'm not recommending a background filter (for example, avoiding Big tech candidates). The sample can't support it, and strong Big tech candidates may well do fine under a better-calibrated behavioural round. Interviewers should be told that polished decks and fluent technical conversation have not predicted success here.

I can have the rubrics and interviewer assignments ready within two weeks if you agree with the direction.

MEMORANDUM

TO: Elif Demir, VP Product FROM: Director of Product DATE: October 24, 2023 SUBJECT: Analysis of PM Hiring Loop Performance and Proposed Redesign for Q1 Hiring

*

Executive Summary

Over the past 18 months, we evaluated 52 PM finalists and hired 9. Three hires struggled significantly (rated 2/5 after 12 months, well below our 3.4 company average).

Our data reveals a clear and counter-intuitive pattern: 1. The only reliable predictor of success is the Behavioural Metric Round ("Tell me about a metric you moved"). 2. The Take-Home Deck, Presentation Round, and VP Engineering Conversation are negatively correlated with performance. They reward presentation polish, shared jargon, and Big Tech pedigree over actual execution. 3. The 1-week take-home deck is causing talent leakage: 19% of final-round candidates withdrew, including top performers. 4. All three struggling hires share the exact same profile: Big Tech background, high presentation and VP Eng scores (4/4), and poor behavioural metric scores (2/4). We over-indexed on polish and excused weak operational substance.

Below is an analysis of our interview signals, our statistical confidence, and a redesigned loop for next quarter.

---

What the Data Tells Us

#### 1. What Predicts Performance: The Behavioural Metric Round Candidate performance on the behavioural round correlates almost perfectly with 12-month post-hire ratings: * Score 4 (3 hires): Average rating 4.67 (two 5s, one 4). * Score 3 (3 hires): Average rating 3.33 (one 4, two 3s). * Score 2 (3 hires): Average rating 2.00 (all three are our struggling hires: C107, C132, C148).

PMs who could drill into the mechanics of moving a metric—causality, counter-metrics, execution trade-offs, and failure lessons—excelled. Those who could not struggled immediately in our environment.

#### 2. What Misleads: Presentation, Take-Home, and VP Engineering Counter-intuitively, scoring at the top of these three stages predicted lower job performance: * Presentation Score: Hires scoring 4/4 averaged a 2.25 rating; hires scoring 2 or 3 averaged 4.20. * VP Engineering Score: Hires scoring 4/4 averaged 2.25; hires scoring 2 or 3 averaged 4.20. * Take-Home Score: Hires scoring 4/4 averaged 2.50; hires scoring 2 or 3 averaged 4.00.

Why are these rounds misleading us? * Deck Polish $\neq$ Product Sense: The take-home strategy deck and presentation test slide design and storytelling. Candidates with Big Tech or consulting backgrounds excel at creating slick artifacts, which creates an "executive presence" halo effect. * Flawed Engineering Rubric: "Technical credibility" currently measures whether a PM speaks Big Tech architectural jargon, not whether they partner effectively with engineers on scoping, trade-offs, and technical debt. * The "Big Tech Halo": All 4 Big Tech hires received top VP Eng scores (4/4), but 3 received failing behavioural scores (2/4). Panel discussions dismissed the poor metric scores because the candidates "interviewed so well." Consequently, Big Tech hires averaged a 2.25 post-hire rating, whereas Startup hires averaged 4.67 (C101: 5, C141: 5, C151: 4).

#### 3. Funnel Inefficiency and Dropout Of 52 candidates reaching final stages, 10 withdrew (19.2%). A one-week take-home assignment imposes an asymmetric burden that disproportionately deters active, highly sought-after PMs (e.g., C117 and C138, both of whom withdrew despite scoring 4 on the behavioural round).

---

How Confident Can We Be?

• Sample Size Constraints ($N=9$): Our post-hire sample is small. Standard statistical models on 9 points are vulnerable to sample variance, and we cannot observe post-hire performance for rejected candidates (selection bias).
• Directional Certainty: While we should not rely on micro-variations, our qualitative and directional confidence is very high. The three struggling hires did not randomly underperform; they share an identical score footprint (TH 3–4, Pres 4, Beh 2, VPE 4). Similarly, zero candidates with a Behavioural score of 2 succeeded, and zero candidates with a Behavioural score of 4 struggled.
• Verdict: We have more than enough empirical and qualitative evidence to eliminate rounds that waste candidate time and bias hiring decisions.

---

Recommended Loop for Next Quarter

To hire four strong PMs next quarter, we must eliminate pedigree bias, reduce dropout, and center the evaluation on rigorous product execution.

``` [Stage 1] Recruiter Screen (30 min) │ [Stage 2] Hiring Manager Screen: Problem Framing & Track Record (45 min) │ [Stage 3] Virtual Onsite Loop (3 Rounds, Same Day) ├── 1. Product Execution & Metrics (60 min) ├── 2. Live Product Design & Problem-Solving (60 min — replaces take-home) └── 3. Engineering & Cross-Functional Partnership (45 min) │ [Stage 4] Structured Debrief & Decision Rule ```

#### Key Adjustments & Rubric Changes

1. Kill the Take-Home Deck and Presentation Round: * Replace with a 60-minute Live Product Design Case (e.g., scoping a feature for an ambiguous user problem). This assesses real-time product thinking, hypothesis generation, and adaptability without requiring 15 hours of slide deck preparation. 2. Elevate the Metrics Round to a Core Gate: * Retain and standardize the Product Execution & Metrics interview. Probe deeply on unit economics, input vs. output metrics, experimentation, and cross-functional friction. 3. Refactor the VP Engineering Round into "Engineering Partnership": * Change the prompt from "technical credibility" to cross-functional execution: how the candidate navigates technical trade-offs, works through debt vs. feature priorities, and writes crisp specs. Pair the VP Eng with an Engineering Manager or Staff Engineer using a standardized rubric. 4. Enforce Non-Negotiable Decision Rules: * Hard Stop on Execution: Any candidate scoring $<3$ on the Metrics/Execution round is an automatic "No Hire," regardless of deck polish or pedigree. Hiring managers cannot override this rule. * Blind Background Debrief: Panelists submit written scorecards before debriefing to prevent seniority or company pedigree from anchoring the room.

This restructured loop eliminates candidate dropouts, shortens time-to-hire, and directly targets the operational execution our PM team needs to hit our growth targets next quarter.