The most impressive person in the room is not usually the best hire, and learning that cost me more than one bad decision. I've sat across from candidates who were polished, articulate, confident, full of good answers and impressive-sounding experience — people who left the conversation having clearly won the interview — and I hired them on the strength of that impression, because how could I not? They'd been excellent at every part of the process I could see. And then the work started, and the polish turned out to be its own skill, unrelated to the one I actually needed. Meanwhile I've watched quieter, less-slick candidates, the ones who didn't dazzle in the room, turn out to be exactly the people who did the work brilliantly. The correlation between impressive in an interview and good at the job is far weaker than anyone wants to admit.
The reason is structural, and it isn't the candidates' fault: an interview measures interviewing. It rewards confidence, articulacy, quick verbal thinking, comfort under social pressure, and the ability to narrate your own competence persuasively — all real skills, and almost none of them the skills most jobs actually require. Being impressive in a conversation is a genuine talent, and it's simply a different talent from doing careful work, solving hard problems, sticking with something difficult, or collaborating well over months. So we run a process that measures one thing, and then hire for another, and act surprised when the results are inconsistent. The impressive candidate isn't fooling you; you're just measuring the wrong variable and reading the result as if it were the right one.
This connects to a pattern that runs through business generally: the polished performance and the underlying reality are different things, and the performance is what we're shown at the moment of decision. It's the same reason a dazzling pitch predicts so little about what an agency is actually like to work with — the pitch measures pitching, the interview measures interviewing, and in both cases the thing being measured is the thing optimized for the decision rather than the thing you'll actually live with afterward. [BACKLINK PLACEHOLDER → suggestion: internal link to article #57, the pitch is a performance, onboarding is the truth / the performance measures performing, not the underlying reality] Hiring is just this problem in its most consequential form, because the cost of getting it wrong is a person, a salary, and months of everyone's time.
I'm not arguing that being articulate is worthless, or that you should hire the least impressive person as a rule — communication genuinely matters for many roles, and I'll address where impressiveness is a real signal. I'm arguing that impressiveness in an interview is systematically over-weighted, that it crowds out better evidence that's available if you look for it, and that the most impressive candidate is often the wrong hire for reasons the process is structurally bad at revealing. Here's why, and what predicts good hires better.
Key Takeaways
- An interview measures interviewing. Confidence, articulacy, and narrating your own competence are real skills, and mostly different from the skills the job requires.
- Impressiveness crowds out evidence. Once someone has dazzled you, you interpret everything else in their favor and stop looking for the harder evidence that actually predicts performance.
- Polish can be a substitute for substance. Some people have invested in being impressive rather than in being good, and the process rewards exactly that investment.
- Watch what they've actually done. Real work, real examples, and specific reasoning about real problems predict far better than how well someone performs in a conversation.
- How they handle being wrong tells you most. Someone's response to not knowing, being challenged, or having made a mistake reveals more than any polished answer they've prepared.
The Interview Measures the Wrong Thing
Start with the structural problem, because everything else follows from it. An interview is a short, high-pressure, conversational performance, and the people who do well in it are the people who are good at short, high-pressure conversational performances. That means confidence, verbal fluency, the ability to think quickly out loud, comfort with social pressure, a well-rehearsed narrative about their own experience, and the knack of making their past work sound significant. These are genuine abilities. They are also, for most roles, close to irrelevant — the job is not a series of forty-minute conversations in which you must seem competent.
Meanwhile, the qualities that actually determine whether someone will be good — careful thinking, persistence with hard problems, judgment, reliability, the willingness to say "I don't know," how they behave over months rather than minutes — are mostly invisible in an interview, or actively penalized by it. The careful thinker who wants a moment to consider a question looks slower than the person with a fluent answer ready. The honest candidate who says "I've never done that, but here's how I'd approach it" sounds less impressive than the one who implies broad experience. The process systematically rewards the wrong signals and punishes some of the right ones, which is why interview performance predicts job performance so much less well than our confidence in it suggests.
And there's a compounding effect: because interviewing is a learnable skill, candidates who've invested in learning it — practicing answers, developing polish, refining their narrative — will outperform equally-capable candidates who haven't, regardless of who's better at the actual work. So the process partly selects for how much someone has optimized for the process. That's not a knock on anyone who prepares well; it's a reason not to read the result as a measure of anything but preparation and social fluency, which is what it actually measured.
Impressiveness Crowds Out Evidence
The subtler damage is what impressiveness does to your judgment for the rest of the process. Once a candidate has genuinely impressed you, a kind of gravity sets in: you start interpreting ambiguous signals in their favor, discounting concerns, filling gaps with optimism, and — most damagingly — you stop digging. Why probe hard into someone who's clearly excellent? The impression does the work that evidence should have done, and the interview becomes a confirmation exercise rather than an investigation.
This is where the real cost lands, because the evidence that would have predicted performance was usually available and you didn't go get it. You didn't look closely at their actual work. You didn't press for specifics on the project they described in flattering generalities. You didn't test how they think about a real problem from your world. You didn't check how they responded when they didn't know something, because they always seemed to know. The impressive candidate didn't hide anything from you; the impression simply made you incurious, and incuriosity is what lets a bad hire through.
There's a version of this that's worth being especially wary of: polish as a substitute for substance. Some people have invested heavily in seeming excellent rather than in being excellent, because seeming excellent is what gets rewarded in the moments that matter — interviews, meetings, presentations. This is the same dynamic as the elaborate deck that impresses and says nothing, or the confident consultant whose advice dissolves under examination: the performance of expertise standing in for the thing itself. [BACKLINK PLACEHOLDER → suggestion: internal link to article #39, most thought leadership has no thoughts in it / the performance of expertise substituting for expertise] Not every impressive candidate is this, and most aren't — but the process cannot distinguish them from the genuinely excellent, which is precisely why impressiveness alone is not evidence.
What Actually Predicts a Good Hire
If interview performance is weak evidence, what's stronger? Mostly, evidence about the actual work. Look at what the person has genuinely done — real work, real output, real projects — and examine it closely, because past work is a far better predictor than a conversation about past work. Where the role permits, give a small, realistic piece of the actual job and see how they handle it, since watching someone do a version of the work tells you more in an hour than talking about it does in five. And when you do talk, push relentlessly for specifics: what exactly was their contribution, what decisions did they make, what did they get wrong, what would they do differently. Vague, flattering generalities are the tell; concrete reasoning about real situations is the signal.
The most useful thing to examine, in my experience, is how someone handles being wrong or not knowing. Ask about a real failure and listen for whether they can describe it honestly, take responsibility, and articulate what they learned — or whether every failure in their history was someone else's fault. Push back on something they've said and watch what happens: do they think about it, engage with the challenge, and update if you're right, or do they defend reflexively? This reveals more than any prepared answer, because it's the one part of the interview they can't fully rehearse, and because the capacity to be wrong gracefully is genuinely predictive of how someone will work with others over time. The person who can say "I don't know" comfortably, and who gets visibly interested when challenged, is showing you something a polished narrative never could.
It also helps to be honest with yourself about what the role actually requires, rather than defaulting to a generic notion of "impressive." If the job is careful, detailed, independent work, verbal dazzle is nearly irrelevant and might even be a distraction from what matters. If it's client-facing, communication genuinely counts — but even then, warm clarity over months is a different thing from performing well in a forty-minute audition. Match your evidence to the actual job, rather than to an all-purpose impression of excellence that no specific role requires.
🎬 Embed a short contrast between an interview that rewards polish and one built around real work, specific reasoning, and how a candidate handles being challenged.
Why This Is Hard to Resist
Knowing all this doesn't make it easy, because the pull toward the impressive candidate is strong and partly social. Hiring the obviously impressive person is defensible — if it goes wrong, everyone agrees they seemed great, and nobody blames you for being persuaded by what persuaded them too. Hiring the quieter candidate whose work was excellent but whose interview was unremarkable requires you to back your own judgment against a visible impression, and to own the risk personally if it fails. The incentives quietly favor the safe, impressive choice over the better one, in exactly the way that diffused, consensus-friendly decisions usually beat correct ones.
There's also the simple fact that being impressed feels like information. It's a strong, vivid, emotionally-real experience, and it's very hard not to treat it as a finding rather than a reaction. The remedy isn't to distrust your reactions entirely — impressions carry some signal — but to treat impressiveness as a hypothesis to be tested against evidence, not a conclusion that ends the inquiry. When you notice you're impressed, that's precisely the moment to look harder at the work rather than less hard. The discipline is the same one that separates real evaluation from performance-acceptance anywhere else: don't let a polished front stand in for the underlying reality you'll actually have to live with. [BACKLINK PLACEHOLDER → suggestion: internal link to article #43, why the discovery call is mostly performance / testing substance rather than accepting polish]
