Blog
Latest
There’s a pattern that plays out in talent acquisition teams constantly, and almost nobody talks about it directly: hiring managers ask for one thing and need another.
They ask for a shortlist of candidates with ten-plus years of experience, and what they actually need is someone who can operate autonomously in an ambiguous environment.
They ask for someone who’s “done this before,” and what they actually need is someone who can learn fast enough to make the last hire’s experience irrelevant.
The gap between what hiring managers ask for and what they actually need isn’t a sign of bad faith or poor communication. It’s a structural consequence of how intake conversations are designed — and of what we’ve taught hiring managers to believe about what makes a good hire.
Understanding that gap, and knowing how to bridge it, is one of the highest-leverage things a TA professional can do.
Why the Gap Exists
When hiring managers describe what they want in a candidate, they’re drawing on a mental model of success that is almost always backward-looking.
They think about the people on their team who perform well.
They think about the person who last held the role, or the person they wish had held it.
They think about credentials and experiences that have historically correlated with hiring success in their organization — even when that correlation was never rigorously tested.
This backward orientation produces requirements that are really descriptions of past hires, not predictions of future performance.
It’s the difference between asking “who has succeeded here before, and how do we find someone who resembles them?” and asking “what does this work actually demand of the person doing it — and what kind of person is built for those demands?”
The first question points backward at a historical pattern. The second points forward at a performance reality. They almost never produce the same answer.
The other driver of the gap is that most hiring managers have never been asked to articulate what a role requires at the skill level.
They’ve been asked to list qualifications. They’ve been asked to describe the ideal background.
But the question “what specific capabilities would someone need on day one to be successful in this role?” often produces a long pause — not because the hiring manager doesn’t know their team’s needs, but because nobody has ever asked them to translate those needs into that language.
The Four Most Common Versions of the Gap
They ask for experience. They need capability.
Years of experience is a proxy metric. It assumes that time in a role or industry produces the specific capabilities the role requires — which is sometimes true and often isn’t.
A candidate with seven years of experience in a highly structured, well-resourced environment may have significantly less relevant capability than a candidate with four years in a lean, fast-moving one.
The question worth asking in an intake: “What specific things would someone need to be able to do from the start?
Let’s make a list of those, and then we’ll figure out what experience typically produces them.”
They ask for a culture fit. They need a skills fit.
“Culture fit” is one of the most consequential phrases in hiring, and one of the least defined. In the absence of a clear definition, it defaults to familiarity: the candidate who went to the right school, who has a similar professional background to current team members, who made the interviewer comfortable in a way they couldn’t quite articulate.
That’s not culture fit. That’s pattern-matching — and it systematically filters out high-potential candidates who bring different backgrounds and perspectives.
What most hiring managers actually mean when they say culture fit is: “I need someone who will operate effectively in this specific environment.”
That’s a legitimate and important criterion. But it’s a behavioral one, and it can be assessed through behavioral questions — not through intuition about similarity.
They ask for someone who’s done it before. They need someone who can figure it out.
The “I need someone who’s done this exact thing before” requirement is among the most constraining in hiring — and among the least predictive of success.
The research on learning agility consistently shows that the ability to transfer skills from one context to another, to absorb new information quickly, and to apply judgment in unfamiliar situations is a stronger predictor of performance in dynamic environments than direct prior experience.
For roles where the work itself is evolving — which describes most mid-market roles — hiring the person who has done yesterday’s version of the job is often the wrong optimization.
They ask for a long list of requirements. They need three or four non-negotiables.
The average job description has fourteen to sixteen requirements.
Research consistently shows that longer requirement lists correlate with lower-quality hires — not because more requirements produce worse candidates, but because they obscure the actual prioritization.
When everything is required, nothing is weighted. Hiring managers end up making decisions based on whichever criteria happened to feel most salient in the interview room, rather than the criteria they agreed mattered most before the search began.
One of the most useful things a TA professional can do in an intake conversation is say: “Of everything on this list, if you could only have three — what would they be?
And which of these could someone develop in the first six months on the job?” That conversation almost always produces more useful screening criteria than the original list.
How to Surface the Real Need
The reframe from “what do you want?” to “what do you need?” starts with the intake conversation, and it starts with a different set of questions.
Start with outcomes, not attributes. “What does this person need to have accomplished by the end of their first year for you to consider this hire a success?”
That question forces a shift from credential-speak to performance-speak — and the answer is almost always more useful than anything that comes from asking what kind of background someone should have.
Test requirements against the actual work. For each stated requirement, ask: “In a typical week, what specific work will this person do where this matters?” If the answer is vague or hypothetical, the requirement is probably a preference, not a necessity.
Separate must-haves from nice-to-haves explicitly. Don’t leave this implicit. Ask the hiring manager to sort their requirements into two columns: things that, if absent, would make them decline an otherwise strong candidate, and things they’d love to have but could live without.
The exercise itself is illuminating — many things that feel like must-haves in the abstract turn out to be nice-to-haves under scrutiny.
Ask about failure modes. “What’s the most common reason someone struggles in this role in the first six months?”
The answer to this question almost always identifies the real non-negotiables — the things that, if absent, predict failure regardless of everything else on the resume.
The TA Professional’s Role in This Conversation
Surfacing the gap between what hiring managers ask for and what they need isn’t about being contrarian or dismissive of their expertise.
It’s about bringing a different kind of expertise to the table — the expertise of someone who has seen what predicts hiring success across many roles and many managers, and who has the data to support a different conversation.
That posture — strategic partner, not logistics function — requires confidence and organizational standing. It also requires structure: the intake conversation has to be designed to produce this kind of clarity, not just to collect a list of requirements that will be handed off to sourcing.
The design of the intake is itself a skills question. And it’s one of the most important things TA can own.
—
This is part of a five-piece series expanding on Why Your Hiring Managers Are Your Biggest Screening Bottleneck (And How to Fix It).
CLARA is an AI-powered skill-alignment hiring platform that helps mid-market companies build structured screening processes connecting TA and hiring managers around validated competencies — not credentials. Learn more at getclara.io.