You found a strong candidate on Tuesday. Senior data engineer, eight years of experience, clean resume, sharp video responses. You advanced them through two technical rounds, a culture panel, and a reference check. Three weeks. Eleven hours of team time across four people.
Then you asked about pay range expectations. Their number was $25,000 above the top of your approved band.
Nobody asked until week three.
The pay range question is the cheapest, fastest piece of information you can get from a candidate. In most interview processes, it's the last thing anyone checks. This post is about moving it to the first.
Every misaligned candidate costs 8 to 12 hours
A typical mid-to-senior interview process runs a recruiter screen (30 minutes), a hiring manager interview (45 minutes), a technical or panel round (60 to 90 minutes), a debrief (30 minutes), and often a reference check (30 minutes). Three to four hours of interviewer time per candidate, spread across two to four people.
When compensation expectations are $20K apart, all of those hours are wasted. The candidate was never going to accept at your band. You were never going to stretch to their number. Both sides knew the range existed somewhere. Neither side surfaced it until the end.
Multiply across your open roles
Most hiring teams run into two or three misaligned candidates per quarter. That's 24 to 36 hours of interview time spent on candidates who were predetermined to decline. For a five-person hiring team managing 20 open positions, it's a full week of productive capacity lost to a question nobody asked.
The offer stage is where this shows up, either as a rejected offer or a counter offer. The root cause happened weeks earlier, when compensation got treated as an offer conversation rather than a screening question.
Pay range alignment is a qualification criterion
Work authorization. Required certifications. Availability. Location. Compensation expectations. Each of these is a yes/no gate that determines whether the rest of the process makes sense. Four of them get checked in the first touchpoint. The fifth usually gets checked three weeks in.
There's no principled reason for the asymmetry. If you won't advance a candidate who can't legally work in your state, why would you advance one whose compensation expectations are $25K outside your band? The legal impossibility and the financial impossibility are the same kind of gate. They both end the process.
The pay range question belongs with the other qualification criteria. Ask it first. Treat the answer like any other must-have.
Why most recruiters skip it
The reason is discomfort. Asking about pay range in the first conversation feels transactional. It feels like leading with money.
The alternative is worse. Discovering misalignment after three weeks of interviews doesn't feel respectful to the candidate. It feels like a waste of their time, which is exactly what it is.
The question stops feeling awkward when it's structural. A one-line qualification question in a screening form reads as standard. A spontaneous "what are you expecting?" in a phone call reads as a negotiation opener. Make it structural.
Four ways to ask the pay range question
How you ask determines how useful the answer is. Four versions, each suited to a different context.
Direct range check
"The approved compensation range for this position is $X to $Y. Does this range align with your expectations?"
The clearest version. Works when your state requires pay range disclosure anyway, or when you want maximum efficiency. The candidate sees the range and self-selects. No ambiguity.
Open expectation capture
"What is your expected base compensation for this type of role?"
Captures the candidate's number without anchoring them to your range. Useful when the role has a wide band or when you want to understand where the market sits. Compare their answer to your range and flag misalignment before advancing.
Total compensation framing
"Beyond base salary, what other compensation components matter most in evaluating an offer? (equity, bonus, remote flexibility, professional development budget)"
Surfaces what the candidate values beyond base. Useful when your total package is competitive but your base is below what competitors offer. An engineer who values equity and learning budget evaluates your offer differently than one who optimizes purely for base.
Timeline and availability
"Are you currently evaluating other opportunities? If so, what's your timeline for making a decision?"
Not a comp question directly, but it tells you how much time you have. A candidate with two other offers in final stages needs a faster process. A candidate early in their search gives you more room.
What to do when the answer is off
If the candidate's expectations are above your range, you have three options.
Transparent redirect. "Our range for this position is $X to $Y. If that doesn't align, I want to be upfront so neither of us invests time in a process that won't work." Most candidates appreciate the honesty and a few will accept anyway once they see the range is real.
Total comp reframe. If your total package is competitive but base is lower, walk through the full picture: equity, bonus, benefits value, PTO. Sometimes the gap is smaller than it looks.
Advance with a flag. If the gap is small (under 10%) and the candidate is exceptional, advance them with a documented flag for the hiring manager. The offer gets built with the gap in mind, not discovered after the fact.
Pay transparency laws make this easier, not harder
As of 2026, eleven states require salary or pay range disclosure at some point during the hiring process: Colorado, New York, California, Washington, Connecticut, Rhode Island, Nevada, Maryland, Massachusetts, Hawaii, and Illinois. Requirements vary. Some mandate disclosure in the posting. Others require disclosure upon request or at the offer letter stage.
If you're already required to disclose the range somewhere in the process, move it to the first touchpoint. The candidate sees it, confirms alignment, and you both move forward with shared expectations. The compliance box gets checked and the screening efficiency gets gained at the same time.
For states without pay transparency laws, early disclosure is still the smarter play. It signals respect for the candidate's time. It reduces counter offers at the offer stage. It costs you nothing except the 30 seconds it takes to add the question to your screening form.
What happens when you actually ask
The data engineer from the top of this post would have entered $175,000 as his expected base. Your band topped at $150,000. You would have seen the gap on Tuesday, the same day you reviewed his screening. Instead of 11 hours of team time over three weeks, you would have spent 30 seconds: strong candidate, comp misaligned, flag and move on.
Same candidate. Same outcome. Three weeks and 11 hours of difference.
The question costs you 30 seconds to add to your screening form and 30 seconds for the candidate to answer. It saves you 8 to 12 hours every time it catches a misalignment. The math is not close.
One question, one fix
Add the pay range question to your first screening touchpoint. Check alignment before anyone books a calendar slot. Treat it like any other must-have qualification.
Your team gets their hours back. Your candidates get honesty. And the $20K conversation stops happening three weeks too late.
Start screening with Truffle free for 7 days. No credit card required.
Frequently asked questions about pay range screening
When should you ask about pay range in the hiring process?
As early as possible. The first screening touchpoint is ideal. Whether that's a qualification question in an async screening flow, a structured question in a recruiter call, or a range disclosure in the posting itself, earlier is always better. Every interview conducted with misaligned comp expectations is time neither side gets back.
Is it legal to ask candidates about their salary expectations?
Yes, in all U.S. states. What some states restrict is asking about salary history (what they currently earn or previously earned). Asking about expectations (what they want) is different and is permitted everywhere. Check your state's specific salary history ban for compliance details.
Should you disclose the pay range in the posting or wait until screening?
Both work and both can be used together. Disclosure in the posting is required in some states and reduces misaligned applications upfront. Disclosure during screening catches anyone who missed the posting range and confirms alignment before interviews begin. The strongest approach is both: range in the posting, confirmation during screening.
What if a great candidate's expectations are slightly above your range?
Define "slightly." If the gap is under 10% and the candidate is clearly your top match, advance them with a documented flag. Discuss the gap with the hiring manager before interviews, not after. If the gap is over 15%, be transparent with the candidate and let them decide whether to continue.
