[hiring]·4 min read·
you don't actually want what you say you want in a hire
every hiring manager describes two candidates. the one they say they want, and the one they actually hire. these are rarely the same person.
every hiring manager i've ever talked to has told me two versions of what they want in a candidate.
the first version lives in the job description, the intake call, the "must-haves" spreadsheet. it uses words like "scrappy," "high-agency," "first-principles thinker." it tells a story about the team's values. it signals what the team wants to believe about itself.
the second version is the one that actually gets hired. you see it in the debrief notes, in the offer letter, in who the hiring manager keeps talking about a week later. it's often a very different person.
one client, last quarter, told us with a straight face that they wanted "scrappy startup energy." their last three hires had all come from google. another insisted on "mission-driven, not resume-driven" candidates, then rejected a founder who pivoted out of a failed startup because the founder "hadn't shown consistent growth."
this isn't lying. nobody's being dishonest. it's a gap between declared preferences and revealed preferences, and it shows up everywhere humans evaluate humans.
why the gap exists
three things conspire to open it.
memory decay. a one-hour interview is a lot of information. by the time the debrief happens three days later, the interviewer remembers about four things: two moments they liked, one moment they didn't, and the overall vibe. everything else rounds to zero. the things that survive are rarely the things they said they cared about. they're the things that were most memorable, which is a different filter entirely.
halo effects. a candidate who is articulate in the first ten minutes gets graded more generously on every dimension for the rest of the loop. a candidate who stumbles early has to climb out of a hole the interviewer doesn't know they dug. "communication" wasn't on the rubric. it doesn't need to be. it warps the rubric anyway.
social debrief pressure. the person who speaks first sets the frame. the second person calibrates to them. by the time the fifth interviewer weighs in, the decision is half-made, and they either agree or burn social capital dissenting. debriefs look like evidence. they're mostly vibes, laundered through a conference room.
what we see in the data
here's the pattern i keep seeing in the wild. the single most predictive variable of whether a candidate gets hired is not the rubric score. it's whether the hiring manager spoke first in the debrief and whether they came in hot.
"came in hot" is not a technical term. but you know it when you see it. the hiring manager walks in, and before anyone else says anything, says "yeah i really liked them." everyone else exhales and agrees.
the opposite also happens. "i don't know, i had some concerns." exhale. agree.
the rubric exists. the rubric is followed. the rubric doesn't decide.
the fix isn't more rubric
the usual response to this is: more structure. tighter rubrics. calibration sessions. scorecards. and all of those help, a little. but they fight the wrong battle. the rubric isn't the problem. the gap between the rubric and the decision is the problem.
what you actually want is a system that can see both layers at once. the declared preferences (what you said you wanted). the revealed preferences (who you actually chose, and why). and then surface the delta, so the team can decide whether the delta is a bug or a feature.
sometimes the delta is a feature. maybe your declared rubric was wrong and your gut was right. maybe "scrappy startup energy" was never the real hiring bar, and hiring senior googlers is the correct move. great, update the rubric.
sometimes the delta is a bug. you hired the person who reminded the ceo of himself. that's not a signal. that's a mirror.
you can't fix what you can't see.
what mazle does about it
we auto-capture every interview. structure the signal in the moment. pull the actual debrief conversation, not just the scorecard. and show teams, over time, the gap between what they say they reward and what they actually reward.
it's uncomfortable. we've had hiring managers stare at three months of their own data and go very quiet.
that's the point.
the gap between what you say and what you do isn't bad. it's just invisible. that's the problem.