How Recruiters Read Your Salary Expectations

An application form in Chicago did the work before the first phone call. The candidate, a marketing operations manager with eight years of experience, typed $95,000 into the salary-expectations box on a Tuesday night. By Thursday morning the recruiter had used that number to rank her above 200 other applicants, and the hiring manager had already decided the range he would defend in the first conversation. Nobody had asked her anything yet. The number had spoken for her.

The recruiter in Austin has watched this happen for twelve years. She has screened more than 2,000 candidates for software companies, most of them through forms that ask for an expected salary before any human exchange. The field is usually the eighth item on the page, and it is often the first thing she reads. "The application is a filter," she said. "The expectations box is the fastest filter in it." Candidates treat the question as a courtesy or a trap. She treats it as a data point, and the data is collected whether the answer is a number, a range, or nothing at all.

"What are your salary expectations?" is one of the most studied prompts in hiring. Recruiters use the answer for three distinct jobs: matching a candidate to the pay band a company has already built, filtering applicants before a person reads a resume, and setting the number around which every later conversation will orbit. Each job has its own rules, and the same answer can succeed at one and fail at another. This article draws on interviews with recruiters and hiring managers in five cities, along with published research on how interview numbers shape outcomes, to explain what actually happens to the answer — and what responses the people reading them say work.

The question is a data point, not a courtesy

Every large employer runs on pay bands. Compensation teams build them from market surveys sold by firms such as Mercer and Willis Towers Watson, which poll thousands of companies about what they pay for each role, then publish ranges with a midpoint and a spread of roughly 20 to 50 percent. The band for a senior accountant in Denver might run $78,000 to $108,000, with a midpoint near $92,000. The recruiter's first job with your answer is to guess where you fall in that structure.

A candidate who asks for $95,000 against that band is inside it, and the conversation moves forward. One who says $70,000 is either underqualified, underinformed, or cheap to hire — and a recruiter will notice the third possibility before the candidate does. One who says $130,000 is telling the recruiter something about the role they think they are interviewing for, and it is not the role on the posting.

"When people say a number way above the band, nine times out of ten they've been looking at the wrong title or the wrong city," said a compensation consultant in Chicago who has advised about 40 employers and asked not to be identified. "When they come in low, we don't correct them. The market will, eventually." A number inside the band but below the midpoint, she said, gets the candidate a faster offer, not a better one — the range was already set, and the answer simply told the recruiter which end to aim at.

Screening happens before a person reads anything

The second job of the expectations box is to remove people. Applicant tracking systems — the software that receives applications at most large employers — treat the field as structured data. A hiring manager can sort a pool of 400 applications by expected salary the way a spreadsheet sorts by column, and many do exactly that at the end of the first day.

Recruiting-technology vendors have long estimated that automated screening removes the majority of applications before a recruiter opens them, and the expectations field is one of the few places where the software has a number to act on. Some systems are configured to flag or drop candidates whose answer falls outside the band; others simply list the field first on the screen. Either way, the candidate who typed nothing has told the system nothing, and nothing is the easiest value to ignore.

A recruiter in Seattle who has run about 400 searches for mid-size tech firms described what blanks actually get. "If the resume is extraordinary, I'll chase them down and ask," she said. "If it's one of 150, I won't. There's no time, and frankly there's no need." The same recruiter reads "open to discussion" as a low number with a coat of paint, and a range the way everyone does: from the bottom.

The screening function explains a pattern in the research on interview numbers: candidates who state any defensible figure survive to the negotiation, and candidates who refuse to engage are winnowed earlier. Studies of anchoring in negotiation, which date to the 1970s, keep finding the same asymmetry — a stated number, even a weak one, moves the final outcome; the absence of a number moves nothing.

The anchor is set before the negotiation

The third job is the one candidates feel. Once a number is in the conversation, it becomes the reference point for everything after it, and both sides know it. The psychologist Daniel Kahneman and his colleague Amos Tversky demonstrated the effect in 1974: people asked to estimate a quantity adjusted from whatever number they had just seen, even when the number was obviously random — a wheel of fortune that landed on 65 pulled estimates of the United Nations' African membership toward 65, and a wheel that landed on 10 pulled them down.

The follow-up studies are closer to a hiring conversation. In 1987, researchers at the University of Arizona gave professional real-estate agents identical property files but different list prices; the agents' appraisals and recommended offers moved with the list price even though the agents insisted the price had not influenced them. In salary terms, the equivalent finding is that the first number on the table — the candidate's expectation or the employer's offer — does most of the work of setting the final number.

The Austin recruiter has seen the mechanism operate in both directions. A candidate who opens at $125,000 for a role banded to $110,000 will usually land in the upper part of the band, she said; a candidate who opens at $95,000 for the same role will land below the midpoint. The two final offers can differ by $15,000 for identical work. That is not generosity or stinginess on the employer's part. It is the anchor doing what anchors do.

The practical implication is uncomfortable but consistent: the candidate who names a number first is not giving information away so much as choosing which information to give — and a researched number beats a number picked from the air.

What happens to candidates who refuse

Refusing to answer is a strategy with real costs and real defenders. In states without salary-transparency laws, the question is legal, and candidates who decline it are handled case by case. The Seattle recruiter's description — chase the extraordinary, skip the rest — was echoed by a hiring manager in Atlanta who said she has rejected roughly one candidate in twenty over the past two years for refusing to give any figure, usually when the field was marked required.

There is also a recorded upside. Studies of salary-history bans found that workers who were not asked about past pay negotiated from stronger positions, and the same logic extends to the expectations question: the less an employer knows about your starting point, the less it can build a low offer around it. The catch: the employer knows this too, which is why the refusal reads as a signal, not a neutral act.

The middle path is the one most experienced candidates take, and it is not a refusal at all. It is a question back. "What's the range you're working with?" or "Where does this role sit in the band?" — asked in the first phone screen, before any number is volunteered. The Austin recruiter said she answers it about half the time, with the band or the midpoint. The other half, the question bounces back. Either way, the candidate has learned something and given nothing.

What no one recommends is answering with a figure you would not accept, hoping to seem flexible. Recruiters log that number too, and it follows the candidate into the offer stage, where it functions as a ceiling the employer is happy to hit.

The answers that work

The recruiters interviewed for this article, working in Austin, Seattle, Atlanta, Chicago, and New York, were asked the same question: what does a good answer sound like? The responses converged on a formula with three parts. A defensible number or range. A reason tied to market data, current compensation, or the scope of the role. And an opening that keeps the door open.

The best answer the Austin recruiter said she has heard in the past year came from a product manager who had looked up the band, the market rate, and her own number before the call: "Based on the market data I've seen for this title at this stage, and my current base of $128,000, I'm targeting the mid-$130s. If the range here is different, I'd like to understand the full picture before we land anywhere." The recruiter's translation: the candidate knew the market, knew herself, and would not be lowballed, but she was not going to make the first offer a hostage negotiation.

"I'm not looking for a number to argue with. I'm looking for evidence that you know what the job is worth. The candidates who get the offers I'd take myself are the ones who can show their work." — a recruiter in Austin who has placed more than 300 product and marketing hires, asked not to be identified

The answers that fail are just as consistent. A single round number with no reasoning. "Whatever you think is fair." A figure pulled from a different city's market, or from a job title that is not the one on the posting. And the answer that recruiters say quietly kills more candidacies than any other: a number with a sigh — "$95,000, I guess" — which reads as a candidate who does not believe in the number either.

How the same expectation reads in a phone screen, in the words of three recruiters

What you say	What it signals	How it usually lands
"I'm targeting $150,000"	Prepared, confident	Offer near $150,000 if the band allows
"$130,000 to $150,000"	Anchored at the bottom	Negotiation starts at $130,000
"I'm flexible"	No anchor at all	Offer at the low end of the band
"What's the range?"	Experienced, cautious	Band disclosed roughly half the time
"I'd rather not say"	Risk, or a strong hand	Survives only with an exceptional resume

Building a range you can defend

The consensus across the recruiters, the research, and the compensation consultants reduces to a short procedure, and it begins before the application. Find the band or the market rate for the role in your city. Three sources are enough: the salary pages at Payscale and Glassdoor, and the Bureau of Labor Statistics' occupational wage data at bls.gov, which publishes medians for hundreds of titles by metro area.

Then set three numbers. The floor is the lowest figure you would accept and still show up on day one with a straight face. The target is what the market says the role is worth, adjusted for your experience. The ceiling is the top of the market range for the role — not your dream number, but what a strong candidate could plausibly command. The range you give should run from floor to ceiling and be about 10 to 15 percent wide. A range that wide tells the recruiter you know the territory; a range twice that wide tells them you are guessing.

The script that emerged from the interviews, in its plainest form: "Based on my research, this role in this market pays $130,000 to $150,000, and I'd target the middle of that. I'm flexible depending on the full package." Five sentences. The recruiters said an answer like that takes the expectation question out of the screening column and puts it in the negotiation column, which is the only column that pays.

One more rule from the Austin recruiter, who has watched the number travel: answer the same way every time. "The number you give on the form is the number they'll quote back in the final call," she said. "If you put $120,000 on the application and ask for $140,000 at the offer, I know both numbers are fiction, and so do you." Consistency, in other words, is part of the evidence.

Transparency is changing the script

The legal ground under the question has shifted. Colorado began requiring salary ranges on job postings in 2021, New York City in 2022, California and Washington in 2023, and a wave of newer laws followed in 2024 and 2025; by some counts more than a dozen states now post ranges by statute. In those states, the expectations question has not disappeared — it has moved indoors. Candidates still get asked, but both sides now hold the same band, and the question reads differently when the range is already public.

The early research on transparency laws, summarized by the Economic Policy Institute, found modest effects: posted ranges moved wages in the lower part of the band upward, and applications rose for jobs that disclosed pay. Job-posting data from LinkedIn and Indeed show that listings with salary ranges draw more applicants than identical listings without them. What the laws have not done is end the screening function; it has simply moved into the range field. A candidate whose expectation sits below the posted range is still flagged — now by the system, not the recruiter.

The compensation consultant in Chicago put the change in blunt terms: "The laws changed the paperwork, not the psychology. Candidates still get anchored, still get screened, still get asked. They just have more of the map now." That is the honest version of the transparency story: the map is real, the reading of it is still a skill, and the answer to the expectations question remains the single most informative thing a candidate says in the first ten minutes.

What the answer is worth

The expectations question is not going anywhere. More states will post ranges, more systems will sort by the field, and the question will keep arriving in the same polite form. What has changed is that the answer is no longer a shot in the dark — the band is findable, the anchor is documented, and the playbook for both sides is public. Candidates who do the reading before they type, and who treat the question as the start of a negotiation rather than a test, are the ones recruiters describe as easy to work with. That phrase, in a hiring market, is worth more than a well-timed number.

Before the next application, run the three-number exercise once: floor, target, ceiling. Use the salary calculators to convert the figure into the terms the conversation will use — hourly, annual, adjusted for inflation — so that whatever form the question takes, the answer is the same number. Then give it plainly, with the reasoning attached, and let the band do the work it was built for. The recruiter on the other end is not trying to trick you. They are trying to find out, in the first ten minutes, whether the two of you can get to a yes. A prepared number is the fastest way to show them you already know the answer.