Hire a PM

MEMO

To: Elif Demir, VP Product From: Director of Product Subject: Fixing the PM Interview Loop Before Next Quarter’s Hiring

Elif,

I analyzed the data from the 52 PM candidates who reached our final rounds over the last 18 months—specifically looking at the 9 we hired, the 33 we rejected, and the 10 who withdrew.

The headline is clear: We are over-indexing on polished presentation skills and Big Tech pedigrees, while actively ignoring our single best predictor of on-the-job success.

Here is what the data shows, how confident we can be in these findings, and the revised interview loop I recommend for next quarter.

---

1. What Predicts Success (and What Doesn’t)

Of the 9 PMs we hired, their average 12-month performance rating is 3.33 (slightly below the company PM average of 3.4). Four hires met or exceeded expectations (ratings of 4 and 5), two were below average (rating of 3), and three struggled significantly (rating of 2).

When we compare their interview scores to their 12-month performance ratings, the patterns are striking:

• The Behavioural ("Metric You Moved") Round is our only strong positive predictor ($r = +0.87$).
• Every hired PM who scored a 4 in this round (C101, C141, C149) went on to become a top performer (ratings of 5, 5, and 4).
• Every hired PM who scored a 2 in this round (C107, C132, C148) struggled on the job (all three received a rating of 2).
• Despite this, we treated this round as optional: we hired three candidates who scored a 2 here because we were dazzled by their decks and pedigrees. Conversely, we rejected 5 candidates who scored a 4 in this round.
• The Take-Home and Presentation are negatively correlated with performance ($r = -0.57$ and $r = -0.84$).
• Our three struggling hires (all rated 2) scored 4s on their presentations, and two of them scored 4s on the take-home.
• Meanwhile, our top performers (rated 4 and 5) scored 2s and 3s on the take-home and presentation.
• A one-week strategy deck tests a candidate’s ability to craft polished slides in a vacuum with unlimited time—a skill that does not translate to shipping product at Kestrel.
• The VP Engineering Round is heavily biased toward Big Tech and negatively correlates with success ($r = -0.68$).
• Across all 52 candidates, Big Tech PMs averaged a 3.44 with the VP of Engineering, while Startup, Agency, and Consulting PMs averaged 2.16, 1.70, and 1.93, respectively.
• Every single Big Tech PM we hired scored a 4 in this round, yet they averaged a 2.25 performance rating at 12 months. Meanwhile, top performers from Startup and Agency backgrounds (C101, C149) scored 2s in this round. The unstructured conversation is indexing on Big Tech jargon rather than the scrappy technical collaboration we actually need.
• The Process Causes High Candidate Drop-Off.
• 10 of our 52 finalists (19%) withdrew. Notably, 3 of the 8 candidates who scored a 4 on our best predictor (the Behavioural round) withdrew. A one-week take-home followed by a 4-stage loop is too slow and burdensome for top-tier, in-demand talent.

---

2. How Confident Can We Be?

We should treat these findings as directionally vital, though statistically limited: 1. Small sample size ($n = 9$): Nine hires is a small dataset. A correlation of $+0.87$ on 9 data points is remarkably clean, but we shouldn't treat the exact coefficients as immutable laws. 2. Survivorship and selection bias: We don't know how the 33 rejected candidates would have performed. Furthermore, the negative correlation on the presentation and VP Eng rounds is partially an artifact of our hiring decisions: when candidates had a weak Behavioural score (2), we only hired them because they had 4s in the other rounds. 3. The "Big Tech" confounding variable: All three struggling hires came from Big Tech, while all four top performers came from Startups or Agencies. Big Tech PMs aced the deck and VP Eng rounds, while Startup/Agency PMs aced the metric-execution round.

Even with $n=9$, the qualitative logic backs the data: past execution on moving metrics predicts future execution at Kestrel; making pretty slides and name-dropping Big Tech infrastructure does not.

---

3. The Proposed Loop for Next Quarter

To hire four great PMs next quarter—and stop losing top candidates to withdrawal—we need to cut the time-to-hire, eliminate the take-home deck, and re-center the loop on execution and structured collaboration.

1. Recruiter Screen (30 mins) * No change, except: Source more heavily from Startup and Agency backgrounds, and screen out Big Tech candidates who haven't owned end-to-end execution.

2. Behavioural Execution Deep-Dive: "A Metric You Moved" (60 mins) * Change: Move this to the very first round after the recruiter screen and make a score of 3 or 4 a hard requirement to advance. * Why: It is our strongest predictor of success. Moving it up filters out "talkers" early and saves panel bandwidth.

3. Live Product Case & Prioritization Workshop (60 mins) * Change: Kill the 1-week take-home and panel presentation. Replace them with a zero-prep, live working session with two PMs using a real, messy Kestrel problem. * Why: The take-home selects for slide-making and causes nearly 20% of finalists to withdraw. A live case tests how candidates structure ambiguity, incorporate feedback, and think on their feet—without requiring 15 hours of unpaid homework.

4. Structured Engineering Collaboration Round (45 mins) * Change: Replace the unstructured VP Engineering "technical credibility" chat with a structured rubric led by a Senior Engineering Manager or Tech Lead. Prompt: "Tell me about a time you had to make a tough scope vs. technical-debt tradeoff with your engineering team." * Why: Eliminates the Big Tech halo effect and tests how the PM actually partners with engineers day-to-day.

5. Hiring Decision & Bar-Raising * Change: Replace open-ended panel discussion with independent score submission prior to debrief. Institute a hard rule: No candidate can be hired with a score below 3 on the Behavioural Execution round, regardless of how well they interview elsewhere.

If you're aligned, I will work with Recruiting and Engineering this week to build the new rubrics and live-case prompts so we are ready for next quarter's reqs.

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

Recommendation

For the next four hires, make demonstrated product judgment, metric ownership, and cross-functional execution the center of the loop. Replace the week-long strategy deck and separate presentation with a short, standardized work sample; retain and strengthen the behavioral metric interview; replace the unstructured “technical credibility” conversation with a scored collaboration exercise.

These are evidence-informed changes, not a validated hiring formula. Our strongest signal comes from just nine hires.

What appears to predict performance

We have 52 finalists: nine hired, 33 rejected, and ten withdrawn. Only the nine hires have performance outcomes. Their average 12-month rating is 3.33, versus the company PM average of 3.4. Three received a 2; none received a 1. The similar averages do not negate the three struggling hires, but neither establish that the entire loop is failing.

Among hires:

Descriptive Pearson correlations on ordinal scores, based on nine hires—not validated predictive estimates.

The behavioral round shows a particularly clear pattern: the three hires scoring 2 all subsequently received performance ratings of 2; those scoring 3 averaged 3.33; those scoring 4 averaged 4.67. It plausibly tests something relevant to the job: whether candidates can explain their own contribution, reason about outcomes, and learn from results.

Conversely, three hires—C107, C132, and C148—received presentation and VP Engineering scores of 4, but later performance ratings of 2. C101 scored 2 in both those rounds and subsequently received a 5. We should stop treating polish or this version of technical credibility as sufficient evidence of PM effectiveness.

We have no scored evidence for the recruiter screen, and cannot assess the independent value of panel discussion or hiring-manager judgment from these files.

How confident should we be?

Confident about the observed pattern; low confidence that it will generalize.

• Nine outcomes are too few to estimate stable predictive relationships or optimize weights and cutoffs. A few cases could materially change the results.
• Selection limits the analysis. We observe performance only for people our existing process hired. Rejected and withdrawn candidates are not failed PMs; their missing outcomes prevent us from measuring false negatives or assessing validity across all finalists.
• Background and scores are entangled. The four big-tech hires averaged 2.25 in performance; the three startup hires averaged 4.67. Background also overlaps with interview-score patterns. We cannot isolate interview effects from background, assignments, support, or other differences—and should not turn this into a background preference.
• The rounds are not independent. The deck and presentation share content, while ratings may reflect overlapping impressions. We cannot establish which round adds value beyond another.
• Performance ratings are an imperfect criterion. We lack role scope, manager, onboarding, and rating-calibration information. The company average is not a matched comparison group.

Negative correlations therefore do not mean we should prefer poor presenters or candidates with low technical scores. They mean the current versions have not demonstrated useful positive signal.

The loop I would run next quarter

1. Structured recruiter screen. Confirm role expectations, relevant experience, motivation, and logistics using consistent questions. Explain the process and preparation requirements upfront.

2. Standardized product work sample, replacing the deck and presentation. Use a fictional product brief and small dataset, with a roughly 60–90-minute total candidate commitment. Ask candidates to diagnose a problem, choose an outcome metric, prioritize options, and explain tradeoffs. Introduce a new constraint during discussion to test adaptation, not slide polish. Use equivalent prompts, consistent preparation conditions, and accommodations where needed.

3. Structured behavioral metric interview. Keep the strongest observed signal. Probe the baseline, candidate’s personal actions, alternatives considered, attribution versus correlation, unintended effects, and lessons learned. Score ownership, analytical judgment, and learning separately using behaviorally anchored rubrics.

4. Structured engineering collaboration interview. Replace the standalone credibility conversation with a realistic scenario involving delivery constraints, instrumentation, and competing priorities. An engineering interviewer scores clarification, tradeoffs, and collaboration—not jargon, pedigree, or conversational rapport.

5. Evidence-led decision. Set role-specific competencies and minimum requirements before interviewing. Interviewers submit independent scores and concrete evidence before discussion. The hiring manager documents the decision and any override. Presentation polish must not compensate for missing evidence on critical competencies. Do not derive mechanical cutoffs from these nine hires.

How we will know whether this is better

Preserve round-level scores, interviewer identities, decisions, overrides, withdrawals, and candidate feedback. Define consistent, role-adjusted performance measures at 3, 6, and 12 months; where feasible, have reviewers assess performance without seeing interview scores.

Review candidate burden and scoring consistency immediately. Treat outcomes from the next four hires as additional evidence—not proof of success. Build a larger cohort before claiming predictive validity or tuning numerical weights.

To: Elif Demir, VP Product From: Director of Product Re: What our PM loop predicts, and the loop for next quarter

Summary

Of the five stages in our loop, only the behavioural "metric you moved" round tracks how hires perform after 12 months. The take-home, the presentation and the VP Engineering conversation all point the wrong way: hires who scored higher on them performed worse. The evidence is thin (nine hires), so I'd treat this as a strong hint rather than proof. Even so, it is consistent enough to change the loop now and to measure the new loop properly.

What the data shows

Over 18 months, 52 candidates reached the final rounds. We hired 9, rejected 33, and 10 withdrew. Our hires averaged 3.3 at 12 months, slightly below the PM average of 3.4. The three who struggled are C107, C132 and C148, all rated 2.

Average 12-month rating of hires, by interview score

The three strugglers share an identical profile:

• 4 on the presentation
• 4 on VP Engineering
• 3 or 4 on the take-home
• 2 on the behavioural round
• Big-tech background

Our two strongest hires, C101 and C141 (both rated 5), had middling presentation and VP Engineering scores but scored 4 on the behavioural round.

In other words, we have been hiring for polish and for technical fluency, and overriding the one signal that worked.

Background is tangled up in this. All four big-tech hires were rated 2 or 3, averaging 2.25. The five others averaged 4.2. The VP Engineering round looks especially exposed to this:

• Every VP Engineering score of 4 in the dataset went to a big-tech candidate (9 of 11 big-tech candidates).
• No other candidate scored 4.

The round may be measuring familiarity with big-tech engineering culture rather than how well someone will work with our engineers.

The behavioural result holds within each group. This is the most reassuring part of the analysis.

• Among non-big-tech hires, the behavioural score still tracks performance. Those who scored 4 were rated 5, 5 and 4. Those who scored 3 were rated 3 and 4.
• Among big-tech hires, the one who scored 3 was rated 3 and the three who scored 2 were rated 2.

So the behavioural signal isn't simply a stand-in for background. Within non-big-tech hires, the presentation and take-home scores still lean negative.

How confident we can be

I'm only moderately confident, for five reasons:

• Nine data points. One or two different outcomes could change the picture, and none of these correlations would survive a strict significance test.
• We only see outcomes for people we hired. Hires were selected partly on high presentation and VP Engineering scores, so we can't see how low scorers on those stages would have done. We also don't know about strong behavioural candidates we rejected (C121, C123, C131, C135, C146), or about withdrawals. C135, for example, was rejected despite scoring 3, 4, 4 and 3, among the strongest sets of scores in the pool.
• Background is confounded. With four big-tech hires, I can't fully separate "big-tech PMs struggle here" from "our loop rewards the wrong things in big-tech PMs." Either way, the fix is to the instruments, not to filter on background.
• 12-month ratings are one manager's judgement, and they also reflect team and scope.
• Interviewer effects. We don't know who scored which candidates, so some of this may come from individual raters rather than from the stages themselves.

What I am confident about is narrower. The take-home, presentation and VP Engineering scores give us no evidence that they help. Given what they cost candidates and the panel, that is reason enough to stop relying on them.

The loop I'd run next quarter

1. Recruiter screen. Unchanged.

2. Structured behavioural round, now the core of the loop (two interviewers, about 60 minutes). - Keep "a metric you moved," and add a second prompt: "a decision you got wrong and what you changed." - Use a written rubric that scores: - specificity about the candidate's own actions; - how they diagnosed the problem; - the trade-offs they made; - what they learned. - Score the substance, not the delivery. Each interviewer scores independently.

3. Replace the week-long take-home and presentation with a 90-minute live working session. - Give the candidate a real, anonymised Kestrel problem with messy data, and work through it with a PM and an engineer. - Score how they reason, prioritise and respond to pushback, not how finished the output looks. - This also cuts the candidate time we ask for. Ten of 52 finalists withdrew; I can't say the week-long take-home caused that, but it won't have helped.

4. Redesign the VP Engineering round as a structured "working with engineering" round. - Base it on a scenario such as a scope cut, a technical-debt trade-off or an estimate dispute, with a rubric agreed with Engineering. - Score it pass/concern only until we have evidence that it predicts anything, so it can flag real problems without rewarding big-tech vocabulary.

5. Change how we decide. - All scores and written evidence go in before the debrief, so nobody anchors on the loudest voice. - No hire with a behavioural score below 3. - The hiring manager still decides. If they hire against the behavioural score, they write down why.

6. Measure it this time. - Log every interviewer's scores, not just the panel's. - Collect 6-month and 12-month ratings against a consistent rubric. - With four more hires we'll have 13 to analyse. We should review the data in two quarters, not two years. - I'd also like a quick look back at the strong behavioural candidates we rejected, to see whether the debrief was systematically discounting that round.

The ask

I'd like your sign-off to:

• pilot this loop for the four upcoming hires;
• get two hours of interviewer calibration on the new rubrics;
• secure the VP Engineering's agreement to redesign their round.

I can have the rubrics and the working-session problem ready within three weeks.