You open an application, and its salary expectations sit above the role’s pay range. It’s tempting to reject it, or to add a knockout question that rejects high answers automatically. Either way, you save time but turn people down on one number, before anyone reads the rest of their application. Some of those people may meet every requirement and accept an offer you can afford.

Instead, I’d agree with the hiring manager in advance on how far over the range you can go. Then I’d read every application before turning anyone down, and save the pay conversation for your first call with the candidate.

This guide is for recruiters and hiring managers deciding how to handle salary expectations above the range on an application. It shows you how to set that limit and handle each kind of salary expectation, including a number that stays out of reach. It ends with four signs that an open role is losing good applicants because of pay.

Should you reject an application when salary expectations are above your range?

Not on the number alone. Read the application first, then ask the candidate about the salary.

If your job ad shows the range and the candidate applied anyway, they’ve likely seen what the role pays and still want it.

The difference between a candidate’s number and your range is the gap. Sometimes the role can close it, for example by hiring at a higher level or adding a signing bonus. When the number is beyond anything the role can pay, it’s a real mismatch.

Agree on a pay threshold before the role opens.

Before any application arrives, agree on one number with the role’s hiring manager: the highest base salary you’d offer the right person. That’s your threshold.

For example, say the range tops out at $120,000 and the hiring manager agrees to go up to 10% higher. Your threshold is then $132,000. A candidate asking for $128,000 is inside it, so talk it through. One asking for $150,000 is beyond it, so ask once whether that number is firm.

To set your own, ask the hiring manager how far they’d go for a candidate who meets every must-have. A set percentage above the range works, and so does the highest pay for the next level up, if they’d hire at that level. If the role can’t pay anything above the range, your threshold is the top of the range. Write it down where everyone reviewing applications for the role will see it.

Four kinds of salary expectations and what to do with each.

Every salary expectation you see fits one of four cases, and the case decides your next step:

Talk about pay on your first call.

Bring up pay early in the call, before anyone spends time on interviews. The aim is to find out whether the gap can close.

Open with a question, so the candidate can explain the number rather than defend it.

Match your follow-up to the answer you get:

• A market rate they’ve seen. Ask where it came from, and compare it with your range.
• The raise they want from this move. Ask what would make the move worthwhile for them.
• A number they’d lower for the right offer. Ask what that offer would need to include.

Don’t ask what they earn now, because some places ban questions about pay history. In every case, talk through the whole package. Bonuses or stock options can help close the gap when the budget limits base salary. We have a separate guide to handling salary negotiations for when you reach the offer stage.

When the gap is a real mismatch, and when the range is wrong.

When a gap doesn’t close, check two things: whether the candidate’s number can change, and whether your range is out of date.

If the candidate won’t move below your threshold, even after you’ve discussed the whole package, treat it as a real mismatch. Decline quickly and kindly: tell the candidate you can’t meet their number. Then ask whether you may keep their details, since a more senior role could suit them later.

To check the range itself, look across all the applications for the role. If many of the applicants who meet your must-haves ask for more than your range, the range may be wrong. Check it against the market rates candidates mention on first calls.

Where Metaview fits, and what stays with your recruiters.

If you have more applications than you can read by hand, get help reading every application instead of using a knockout question. Metaview Application Review reads every application for you.

Your team first approves the role’s Ideal Candidate Profile (ICP), a description of who the role needs. Application Review then rates how closely each application matches that profile, from “Great” to “Poor.” It shows the reasoning for each rating.

The screen below shows sample applicants with their “ICP Fit” ratings.

Application Review never auto-rejects anyone. A recruiter makes every “accept” and “reject” call.

Signs you’re losing candidates over pay.

Once a role has been open for a few weeks, check how your team is handling salary expectations.

Here’s what to look for, and what I’d change first:

This week, agree on a threshold for one open role with its hiring manager. Then go back through the above-range applications already waiting for that role.

A salary number is where the conversation starts.

A salary expectation is one of the few places where a candidate tells you, before you’ve spoken, what they think their work is worth. When it comes in high, it can point to experience the job ad undersold, or to a competing offer you haven’t heard about yet. Both are worth knowing, and you only learn which it is by asking.

Hiring at volume works best when every applicant gets a fair read and recruiters still have time to ask.

That’s the thinking behind our Application Review: every application read against the profile your team approved, with the call on who moves forward left to your recruiters.