How to

How to push back on a hiring manager: scripts for the six hardest conversations

On this page
  1. What makes pushback work?
  2. What evidence should a recruiter bring?
  3. How do you push back on an unrealistic must-have list?
  4. How do you tell a hiring manager the pay is below market?
  5. What do you say when hiring manager feedback is slow?
  6. How do you handle moving goalposts?
  7. What if the manager rejects candidates without giving reasons?
  8. What should you never negotiate?
  9. How is pushback different for agency recruiters?
  10. When should you escalate, and to whom?
  11. What should you send after the conversation?
  12. Questions people ask

To push back on a hiring manager, replace opinion with evidence and a choice: say what you are seeing, show the data behind it (pipeline numbers, pay data, candidate feedback, reactions to sample profiles), offer two or three options with their trade-offs, and ask the manager to decide. Do it early, by phone or in person, and confirm the decision in writing the same day. Escalate only when a pattern continues after a direct conversation, or at once if a request would be unlawful.

This page is the conversations themselves, with scripts for the situations recruiters raise most: an impossible must-have list, pay below market, slow feedback, moving goalposts, rejections with no reason, and requests you cannot act on. Agreed timings belong in a recruiting SLA with hiring managers, and most of these conversations go better if the intake meeting settled the must-haves first.

What makes pushback work?

Hiring managers hear "you're asking for too much" as an opinion, and they outrank you on opinions about their own team. They respond to facts about the market and to choices that keep them in control. Every script below follows the same four steps:

  1. Observation. One sentence of what is happening, without blame. "We've had 40 applicants and two met the must-haves."
  2. Evidence. The numbers or quotes behind it, from your own pipeline or a primary source.
  3. Options. Two or three real choices, each with its cost: time, money, or a requirement.
  4. Decision and record. The manager picks; you write it down and send it.
Sounds like opinionSounds like evidence
"That's a unicorn.""Of the 60 profiles that match the title and location, four have both the license and the language."
"The pay is low.""The three finalists who withdrew all cited pay, and the median for this occupation in this metro is above our midpoint."
"You're too slow.""The last two candidates accepted other offers while waiting four and six days for feedback."
"You keep changing your mind.""The brief has changed twice in three weeks; each change sends the search back to sourcing."

The numbers in this page's scripts are examples. Use your own.

What evidence should a recruiter bring?

  • Your funnel. Profiles reviewed, contacted, replied, screened, submitted, interviewed, with the reason each dropped. A recruiter KPI dashboard makes this a two-minute export.
  • Pay data from a primary source. The Bureau of Labor Statistics Occupational Employment and Wage Statistics publishes wages by occupation and metro area; the May 2025 estimates were released on May 15, 2026. Ranges in comparable postings help too, since several states require pay ranges in job ads; see how to set salary ranges for job postings.
  • Candidate words. Decline reasons, written down as the candidate said them. "Two candidates said the five-day office requirement ruled it out" lands harder than your summary.
  • Reactions to sample profiles. A manager who said no to three profiles and gave reasons has told you what the brief really is. Calibration profiles are the cheapest evidence you can collect.

How do you push back on an unrealistic must-have list?

Do it at the intake or straight after the first calibration round, not after four weeks of sourcing. Ask the manager to rank the requirements, then show what each one costs in candidate numbers.

"Before I start sourcing, can we rank these? If I search for all seven,
I find [4] people in [region], and most aren't looking. If we make
[requirement] a nice-to-have, it's [35].

Three ways we could go:
1. Keep all seven, widen to remote across [country], and expect [8-10] weeks.
2. Drop [requirement] to a nice-to-have and teach it in the first 90 days.
3. Keep the list, raise the range to reach people at [competitor level].

Which matters most to you: the full list, the start date, or the budget?"

If the manager insists on everything, agree a review date: "Let's try it for two weeks; if I have fewer than three people you'd interview by then, we revisit number two."

How do you tell a hiring manager the pay is below market?

Lead with what candidates did, then the data, then the options. Never quote a figure you cannot source.

"I want to flag something before we lose more people. Of the [6]
candidates who met the must-haves, [4] dropped out at the pay
conversation. They're earning [range] now. The BLS estimate for this
occupation in [metro] puts the median at [figure], above our midpoint.

Options as I see them:
1. Move the range to [figure], which gets us to the people we're losing.
2. Hire one level down at the current range, with a review at six months.
3. Open the search to [lower-cost locations] if the role can be remote.
4. Keep the range and accept a longer search; I'd suggest we review in
   three weeks.

Who would need to approve option one, and should I bring the data to them?"

The last line matters: the hiring manager often agrees and cannot approve. Offer to build the case for whoever can. When the range cannot move at all, how to hire when you can't match salary covers what else you can offer.

What do you say when hiring manager feedback is slow?

Make the cost concrete, offer a smaller ask, and agree a default if they stay silent.

"Quick one: [Candidate] withdrew this morning. She accepted an offer
she got while waiting on our feedback from Tuesday's interview. [Name]
is in the same position now.

Could we try this: you send me a yes or no plus one line within two
working days of each interview, and if that's not possible, I'll grab
ten minutes on your calendar and take the notes myself. Would that work?"

For the reminder itself, use the hiring manager feedback reminder email. If the problem is the interview, not the inbox, a manager who was briefed beforehand has less to write up afterward.

How do you handle moving goalposts?

Requirements change for good reasons: a reorganization, a teammate leaving, a candidate who showed what was possible. The fix is to make the change explicit, so the search resets on purpose instead of drifting.

"That's a real change from the brief, so let me make sure I have it
right. We're now looking for [new requirement] instead of [old one].
That means:
- [Two] candidates in process no longer fit. Shall I tell them this week?
- I'm back to sourcing for the new profile, so the earliest shortlist
  is [date].
- The scorecard needs updating so interviewers score the new thing.

I'll send the updated brief tonight. Can you reply 'agreed' so we're
working from the same version?"

What if the manager rejects candidates without giving reasons?

"Not a fit" tells you nothing about the next search, and it is a weak record. Federal regulations require employers covered by Title VII and the ADA to keep application forms and other hiring records for one year from the record or the personnel action, whichever is later (29 CFR 1602.14). A reason tied to the agreed criteria is far easier to stand behind than a shrug.

"Thanks. So I can change the search, which of the must-haves didn't
she meet, and what did you see in the interview that showed it? One
line is enough. If it's something we didn't put in the brief, that's
useful too; I'll add it."

If the reason is "culture fit", ask what the person would do day to day that showed it; see how to assess values without culture-fit bias. Notes with evidence also make this conversation easier. A tool such as Interview Signal, which we make, fills the scorecard with the candidate's own quotes checked against the transcript, so the reason can point at what was said rather than at an impression.

What should you never negotiate?

Some requests are not a matter of options. Title VII makes it unlawful for an employer, and separately for an employment agency, to refuse to refer or to classify candidates because of race, color, religion, sex or national origin (Title VII, section 703), and the ADEA does the same for age, protecting people who are at least 40 (ADEA). "Someone young and energetic", "no one who'll go on maternity leave" or "a native speaker" for a role that does not need one are not preferences to work around.

"I can't search on that, and I'd be putting you at risk if I did. What
I can do is find people who can [the actual job requirement, e.g.
'work the night rotation' / 'present in Spanish to clients']. Is that
what you need?"

If the request is repeated, escalate it the same day. This is general information, not legal advice; see age discrimination in hiring for more on the age rules.

How is pushback different for agency recruiters?

An in-house recruiter and a hiring manager work for the same employer and share the cost of an open role. An agency recruiter is a supplier, often on contingency, so pushback is also a decision about where to spend your desk time.

In-house recruiterAgency recruiter
Your strongest leverShared goal and data: time-to-fill, offer declines, cost of vacancyYour time: you can deprioritize or decline a job order you cannot fill
When to raise itAt intake and in the weekly updateBefore you accept the job order, and at the first submittal feedback
Who you escalate toTalent acquisition lead or HR business partnerThe client's main contact or whoever signed the terms, plus your own manager
Script to add"Can we agree this in the SLA so it doesn't depend on either of us remembering?""At this fee and this range I'd be taking your money for a search I don't think will close. Can we change one thing, or would you rather I step back?"

Agencies should write the agreed must-haves, range and feedback times on the job order form, so the conversation in week four can point at what was agreed in week one.

When should you escalate, and to whom?

SituationFirst moveEscalate when
Slow feedbackDirect conversation with the cost and a smaller askThe window is missed again on the same requisition after you talked
Pay below marketData plus optionsThe manager agrees but cannot approve; escalate together, not around them
Must-haves nobody can meetRanking exercise and a review dateThe review date passes with no change and no shortlist
Unlawful requestDecline and restate the real requirementImmediately if repeated
Rejections with no reasonsAsk for one line tied to the criteriaA pattern across several candidates who met the brief

Tell the hiring manager before you escalate: "I'm going to raise this with [name] so we can get it unstuck; I'd rather you hear it from me." Escalation the manager learns about second-hand ends the working relationship.

What should you send after the conversation?

Subject: [Role] - what we agreed today

Hi [Name],

Thanks for the time today. To confirm:
- Decision: [e.g. range moves to X-Y, approved by Z / requirement
  B becomes a nice-to-have]
- What changes in the search: [e.g. widening to remote in State,
  new shortlist by date]
- What I need from you: [e.g. feedback within two working days of
  each interview]
- We'll review on: [date]

Reply if I've got anything wrong; otherwise I'll work from this.

[Your name]

Five lines, sent the same day, turn a conversation into an agreement both of you can point to later.

Questions people ask

How do I push back on a hiring manager without damaging the relationship?

Bring evidence instead of opinion, offer two or three options with their trade-offs, and let the hiring manager choose. Do it early, by phone or in person rather than in a long email, and send a short written summary of what was agreed afterward. Managers rarely resent a recruiter who helps them fill the role faster; they resent being told they are wrong without an alternative.

What do I say when a hiring manager's salary range is too low?

Show the gap with sources, such as the Bureau of Labor Statistics wage estimates for the occupation and area, ranges in comparable job postings, and what candidates you have spoken to earn now. Then give choices: raise the range, lower the level of the role, widen the location, or accept a longer search with a defined review date.

When should a recruiter escalate a problem with a hiring manager?

Escalate when a pattern continues after a direct conversation, such as feedback windows missed repeatedly on the same requisition, or immediately when a request would be unlawful, such as asking for candidates of a certain age, sex or national origin. Raise it with the talent acquisition lead or HR business partner in-house, or with your own manager and the client's main contact at an agency.

How do I get a hiring manager to explain why they rejected a candidate?

Ask for one reason tied to the agreed must-haves, framed as information you need to adjust the search: which requirement the candidate missed and what evidence from the interview showed it. A specific reason also matters for the record, because federal rules require covered employers to keep hiring records for at least a year.