Blog
Latest
There is a version of this conversation that most TA professionals have rehearsed in their heads many times and almost never had out loud.
A hiring manager presents a requirement list that reads like a job description for three different people.
Or they reject a candidate who clearly met all the stated criteria with a vague “not quite right.” Or the goalposts move — again — two weeks into a search that was already difficult.
And the TA professional nods, updates the brief, and goes back to sourcing.
Push-back is hard.
The power dynamics are real, the relationship stakes are real, and the organizational norms that would make push-back safe to do often don’t exist.
But the cost of not pushing back is also real: searches that stall, roles that stay open for months, and hiring decisions made under pressure that produce exactly the kind of misaligned hires everyone was trying to avoid.
Knowing when and how to push back — collaboratively, constructively, with data rather than opinion — is one of the most important skills a TA professional can develop. Here’s a framework for doing it well.
First, Distinguish the Type of Unrealistic
Not all unrealistic requirements are the same, and the right response depends on which type you’re dealing with.
The impossible combination
This is the requirement list that describes a unicorn: ten years of experience, startup mindset, enterprise-level relationships, willing to be an individual contributor, and available for a below-market salary.
Each item might be reasonable on its own. Together, they describe a candidate pool of approximately zero.
The push-back here is a prioritization conversation — but it works best when it’s grounded in the cost of the combination, not a debate about which requirements matter.
Try: “I want to show you what the candidate pool looks like when we hold all of these simultaneously — and what opens up if we treat any one of them as a nice-to-have instead of a requirement. Can we look at that together before I go further?”
That’s not a negotiation. It’s market data delivered as a service. Most hiring managers, when they can see the trade-off in concrete terms rather than in the abstract, are willing to make a practical call.
The credential proxy
This is the requirement that sounds specific but is really standing in for something else. “Must have an MBA.” “Must have worked at a top-tier consulting firm.” “Must have direct experience in our specific industry.”
These requirements aren’t always wrong, but they’re often filtering out highly capable candidates based on credentials that were never validated as predictors of performance for this specific role.
The push-back here is a translation question: “When you say you need someone with consulting experience, what specifically are you hoping that will mean for how they operate in this role?”
Once you get the underlying capability articulated, you can have an honest conversation about whether the credential is the only way to develop it — or whether it’s a proxy that’s excluding candidates who have the actual capability through a different path.
The moving goalpost
This is the most frustrating pattern, and the most important one to address directly.
A hiring manager approves a success profile, a shortlist arrives that meets those criteria, and then the feedback is: “not quite right,” or a new requirement surfaces that wasn’t in the original brief, or the stated priorities shift.
One instance of this might be genuine evolution — sometimes hiring managers learn something through reviewing candidates that legitimately changes their view of what the role needs.
That’s fair, and it’s worth exploring. A pattern of it is something different.
It usually signals that the success profile wasn’t clear enough to begin with, that the hiring manager is avoiding a decision they’re not confident making, or occasionally that the role itself isn’t well-defined enough to hire for yet.
The push-back here is a documentation conversation: “I want to make sure we’re sourcing against the right criteria so we’re not both losing time. Can we update the success profile to reflect what you’re seeing, and confirm the new criteria before I go back to sourcing?”
That framing is collaborative, not accusatory. It also creates a record that either stabilizes the requirements or surfaces the conversation that needs to happen about the role itself.
How to Push Back Without Damaging the Relationship
The goal of push-back is alignment and collaboration, not confrontation.
The TA professional who pushes back well isn’t arguing with the hiring manager — they’re functioning as a strategic partner who brings data, pattern recognition, and process expertise to a shared problem. That posture makes all the difference.
Ground it in the data, not your opinion
The most defensible push-back is always tied to something observable. “Based on the last three searches where this requirement was on the list, our interview-to-offer ratio ran above 10:1 — which usually signals that the screening criteria are filtering out candidates who could actually do the job. Can we revisit this one?”
That’s a different conversation than “I think this requirement is too narrow.”
If you have quality-of-hire data — even informal 30-day or 90-day check-in notes — use it.
The hiring manager who rejected the candidate without the MBA four months ago and then hired the candidate with one who underperformed at 90 days needs to see that connection.
The data isn’t weaponized; it’s shared as information that improves future decisions.
Use the scorecard as your reference point
This is why agreeing on a shared success profile and scorecard before sourcing begins matters so much.
When a rejection comes in, the question “Can you walk me through where this candidate fell short against the criteria we agreed on?” is much easier to ask when those criteria are documented. It’s not adversarial — it’s a reference to a shared agreement.
When the answer reveals that the candidate actually met most of the agreed criteria and the rejection is based on something new, you have a natural opening: “It sounds like there’s a criterion that matters to you that we didn’t capture in the profile. Can we add it so I’m sourcing against the complete picture?”
That move converts a frustrating rejection into a useful calibration.
Name the cost
Sometimes the most effective push-back is the simplest one: “I want to flag that adding this requirement is likely to extend the search by four to six weeks based on what I’m seeing in the talent market. I want to make sure that’s a trade-off you’re aware of before we proceed.”
Hiring managers often add requirements without fully accounting for their impact on the candidate pool or the timeline.
Making that impact concrete and explicit — without editorializing — gives the hiring manager the information they need to make a considered decision.
Sometimes they’ll hold the requirement because it genuinely matters. Sometimes they’ll drop it because the trade-off isn’t worth it. Either way, the decision is made deliberately rather than by default.
When the Push-Back Needs to Go Up
Most alignment issues can be resolved in a direct conversation between TA and the hiring manager. Some can’t, and it’s important to know the difference.
When a search has been open for an extended period, multiple shortlists have been rejected, the requirements have shifted more than once, and the hiring manager remains unsatisfied, the problem may be above the TA/HM level.
The role may not be well-defined. The hiring manager may need support from their own leadership in clarifying what the team actually needs. Or the organization may be trying to hire around a structural problem that a new hire can’t solve.
In those situations, TA leadership has standing to surface the issue to HR business partners or to the hiring manager’s leadership.
Not as an escalation in the adversarial sense, but as a flag that the hiring process needs organizational input to move forward.
That conversation is easier when TA has the documentation — the original success profile, the shortlists delivered, the rejection feedback — to demonstrate that the process has been followed and the issue isn’t sourcing quality. Structure protects everyone when push-back needs to go up.
The Long Game
TA professionals who push back well, consistently, and collaboratively tend to earn something over time that is genuinely rare: hiring managers who treat them as strategic partners rather than service providers. Managers who start their next search by asking “can we do that intake process we did last time?” Managers who send a note after a hire works out saying “that scorecard made a real difference.”
That relationship takes time to build. It requires individual push-backs that go well, and some that are awkward, and patience through both.
But it’s the version of TA that produces the best outcomes for organizations — and the most satisfying work for the people doing it. Push-back, done right, is an act of genuine partnership. And partnership is what great hiring actually requires.
—
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.