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.

MEMORANDUM

TO: Elif Demir, VP of Product FROM: Director of Product DATE: October 24, 2023 SUBJECT: PM Interview Loop Analysis & Recommendations for Q1 Hiring

*

Elif, you are entirely right to flag this. Looking back at our last 18 months of hiring data, out of our 6 hired PMs who completed their first year, half (C107, C132, C148) are struggling with 12-month performance ratings of 2 (well below our company average of 3.4). Meanwhile, our top performers (C101, C141 with ratings of 5, and C149 with a rating of 4) represent the standard we actually need.

To prep for hiring four more PMs next quarter, I’ve analyzed the data for all 52 candidates who reached our final rounds. Here is what works, what is completely broken, how confident we can be, and how we should redesign the loop.

---

1. What Predicts Performance? (And What Doesn't)

By analyzing the correlation between interview stage scores and 12-month post-hire ratings for our 6 completed hires, we see stark contrasts in signal quality:

* Take-Home Strategy Deck (Zero to Negative Correlation): Our take-home exam is a massive waste of candidate time and offers zero predictive value. Our struggling hires (C107, C132, C148) averaged a 3.7 out of 4 on the take-home. Conversely, our top performers averaged a 2.7. High scores on a 1-week unsupervised deck merely signal that a candidate has free time, a supportive current employer, or an agency background—not that they can execute at Kestrel. * Take-Home Presentation Panel (Weak / Misleading Signal): Similar to the take-home itself, presentation scores do not align with success. C107 and C148 both scored 4s on their presentation and turned out to be 12-month "2" ratings. * VP Engineering Conversation (Inverted Signal): Surprisingly, the VP Engineering score shows a negative relationship with success. Candidates who scored high with Engineering often struggled on the job, while our top performers (C101, C141, C149) mixed moderate-to-low engineering scores (2 to 3) with high marks elsewhere. While technical credibility matters, our current technical screen appears to favor academic/theoretical answers over pragmatic product-engineering partnership. * Behavioural Metric Round (Our Only Real Signal): The behavioural round ("Tell me about a metric you moved") is the only component in our current loop that correlates with on-the-job success. * Our three struggling hires averaged 2.0 on this round. * Our three successful hires averaged 4.0 on this round. This is our sole bright spot. It tests past execution, ownership, and learning—things that actually matter day-to-day at Kestrel.

---

2. Statistical Confidence

We must temper our confidence. We have only 6 data points of complete hire-and-tenure data. While the directional trend on the behavioural round is unmistakable (+2.0 delta between high and low performers), running statistical significance tests on $n=6$ is risky.

However, we can look at broader hiring funnel data across all 52 candidates to understand drop-offs. Notably, 13 candidates withdrew from the process, heavily skewed toward candidates who scored well on the take-home (e.g., C100, C113, C142, C147 all scored 4s on the take-home and walked away). Our heavy, one-week take-home is actively driving away top-tier passive talent who refuse to do free consulting work for a week, leaving us to select from a pool of people willing to endure it.

---

3. The Proposed Loop for Next Quarter

To scale our team to four new PMs without repeating past mistakes, we need to strip away vanity metrics (the take-home deck) and lean heavily into what actually predicts success: rigorous behavioural assessment of past execution, combined with a real-time collaborative product session.

Here is the 4-stage loop I propose we deploy immediately:

1. Recruiter Screen (30 mins): Standard fit, compensation alignment, and basic background check.
2. Product Craft & Execution Interview (45 mins - Live Video): Replaces the take-home. Instead of a week-long deck, we give the candidate a real Kestrel product challenge 48 hours in advance (requiring no more than 2 hours of prep) and spend the interview deep-diving into their hypotheses, prioritization trade-offs, and customer empathy.
3. Behavioural & Metric Ownership Round (45 mins): Double down on what works. Retain our behavioural round focusing on metrics moved, but expand the rubric to explicitly test for accountability, cross-functional conflict resolution, and handling failure.
4. Product-Engineering Partnership Round (45 mins): Refocused Engineering screen. Instead of "technical credibility" evaluated in a vacuum, this is a joint session with the VP of Engineering or a Senior Tech Lead to evaluate how the PM collaborates with engineering to ship product, scope down MVPs, and manage technical debt.

Decision Gate: Drop the consensus panel meeting where the loudest voice wins. The hiring manager makes the final call, but only if the candidate scores a predefined threshold on the Behavioural and Product Craft rounds.

Summary

By eliminating the 1-week take-home, we will stop scaring away top-tier talent, shorten our time-to-hire, and refocus our interview panel on real-world execution rather than polished slide decks. Let me know if you are aligned, and I will draft the new interview rubrics by Friday.

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.