What to Say When an Application Asks for Salary Expectations

On a cold Tuesday in February, a product manager in Minneapolis sat at her kitchen table with a job application open and a cursor blinking in a required field: desired salary. The posting's pay-transparency section had already told her the range, $95,000 to $120,000, but the form wanted one number, and she had the uneasy sense that whatever she typed would be used against her. She typed $105,000 and deleted it. She typed "Open to discussion" and deleted that too. Then she closed the laptop and found the hiring manager's name instead.

The moment will be familiar to anyone who has applied for work in the past five years. The salary-expectations question has become a standard line on application forms, and it sorts candidates before any person reads a word of their resume. The number, or the blank, goes into an applicant tracking system, where it can trigger an automatic rejection, a flag, or a quiet note to the recruiter. What follows is what happens to that answer, drawn from recruiter survey data, research on anchoring in hiring, and conversations with recruiters and hiring managers who screen applications for a living. The short version: the field is a filter, and it is a filter you can use.

The field is a filter, not a conversation

Most large employers run applications through an applicant tracking system, or ATS, and the salary field is one of the few boxes the software can act on by itself. Recruiters set a minimum number for many roles, often the bottom of the approved band, and the system silently drops anyone whose answer falls below it. In survey after survey of recruiters, including annual research from Robert Half and from the Society for Human Resource Management, a majority say they use the salary answer to screen candidates before a first conversation.

The number does quieter work too. Since the 1970s, behavioral economists have shown that an initial figure, even an arbitrary one, pulls later judgments toward it; the effect is one of the most replicated findings in the field. In hiring, that means the figure you type becomes the reference point a recruiter carries into the salary conversation, whether you intend it or not. A candidate who writes $70,000 for a role budgeted at $90,000 has, in effect, negotiated against herself before the first phone call. A candidate who writes $130,000 for the same role may never get the call at all.

The screening cuts in both directions, and that asymmetry matters. A number too high can end the application outright, because the recruiter assumes the candidate will not accept the band. A number too low rarely gets the candidate rejected, but it can get them hired cheap — or, just as often, flagged as underqualified, since hiring managers sometimes read a low number as a sign of limited experience. Either way, the field is doing work that no human has reviewed.

A recruiter in Chicago who has filled more than 300 roles for mid-size companies described reading the field the way a waiter reads a table: fast, and for signals. A number far below the band tells him the candidate has not looked at the market. A number far above it tells him the candidate has looked and disagrees about the job. The middle, he said, is where the conversation starts.

The range, done right

The standard advice, from compensation consultants and recruiters alike, is to answer with a range rather than a single number, and the advice survives contact with real application forms. A range signals flexibility without leaving the number to chance. The craft is in the range itself. A tight, researched range, such as $98,000 to $108,000 for a role whose market midpoint is near $103,000, reads as a candidate who has done homework. A sprawling one, such as $75,000 to $150,000, reads as a candidate who has not.

How wide should a range be? Compensation consultants generally suggest keeping it to about 10 percent, enough room to move, not enough to look like guesswork. Where the range sits matters more. Many advisers tell candidates to anchor at the top of what they would accept: if you would take $100,000 and be delighted with $110,000, write $105,000 to $115,000, not $95,000 to $105,000. The recruiter who screens you will remember the number that starts the sentence.

There is a catch. A range only works if it is grounded, and grounding requires research before the form is open. Pay-transparency laws have made that easier in more than a dozen states, where the posting itself carries the band. Where it does not, market data from Glassdoor, Payscale, and the Bureau of Labor Statistics will get a candidate close; Marketivate's salary calculators do the same arithmetic for a specific title and metro. The goal is not precision; it is alignment.

The old advice to never name a number first has mostly faded, and the reason is practical. On an application form, the question is not optional, and a candidate who refuses to engage has already lost the ability to shape the answer. The newer consensus, among the consultants and recruiters consulted for this article, is that naming a researched number first is fine, even useful, because it sets the anchor on your terms instead of leaving the employer to guess — and the employer's guess is rarely higher than yours.

The empty field

The other common answer is no answer. Studies of job seekers suggest that a meaningful minority leave the field blank or write "open," and recruiters are sharply divided about what that means. Some read it as flexibility, the mark of a candidate who wants the whole package, not a number. Others read it as a candidate who has not done the homework.

What the software does is less ambiguous. In many applicant tracking systems, a blank salary field is treated as a missing value, which some configurations convert to zero and reject outright. A recruiter in Austin who has screened more than 2,000 applications put it this way:

"The blank tells me one of two things. Either the candidate doesn't know what the job is worth, or they know exactly what it's worth and have been burned before. Both are worth a phone call. The automated screen doesn't agree. It flags the blank and moves on."

His experience matches the survey numbers. When recruiters are asked what a blank answer tells them, the most common responses are that the candidate seems difficult to work with or unprepared for the process; a smaller group says it signals sophistication. The same split appears in how they act. Some hiring managers will raise the question in the first call and treat the blank as a starting point. Others never make the call.

The candidates who refuse to answer, as opposed to those who simply skip it, are a smaller group, and recruiters describe them with a mix of respect and frustration. The respectful read: refusing to name a number before seeing the full scope of the role is rational, and the most experienced candidates do it. The frustration: the form asks, the system records, and a refusal in a text-only field looks like a non-answer, which some recruiters read as the candidate making the process difficult before it has begun. The middle path, used by many senior candidates, is to answer the form with a range and save the refusal for a conversation, where it can be explained in a sentence.

Ask for the band back

When the question comes from a person rather than a form, the strongest move is often to ask for the range first. The request is no longer unusual. In the states that require pay ranges in postings, the band is public information, and candidates who cite it back are simply using it. Where no range is posted, a careful question can get one: "I'd like to make sure we're aligned before I name a number. Can you share the budgeted range for this role?"

A hiring manager in Seattle who has run interview loops for a decade said the question reads differently than it once did. "Ten years ago, a candidate who asked for the band was testing me," she said. "Now it's the candidate who doesn't ask who seems out of step. The range is on the table anyway, in half the states. Asking for it is just doing the math in the open."

Timing matters. Compensation consultants who coach job seekers say the band question works best after some rapport has been built, usually in the first or second conversation, not in the first automated message. And the question should be asked once, plainly, with the research visible: name the market data you are looking at, then ask whether the budget sits inside it. A candidate who does that has, in effect, turned the expectation question back into a salary conversation, which is what the field was never meant to allow.

The question has a mirror image, and it is worth rehearsing both. When a recruiter asks for expectations in a first phone call, before any range has been shared, the same research that fed the form gives you the answer: name your range, then ask whether the budgeted band overlaps it. When the budget comes in below your floor, the professional move is to say so plainly and let the other side respond, rather than to stretch your number and resent it later. Recruiters say the candidates who hold a line calmly are the ones who get the band moved, more often than candidates might expect.

When the form forces a number

Some forms will not take a range, will not take text, and will not proceed without a figure. The workarounds circulate on career forums: type 0, type 999,999, type the current salary plus a dollar. Recruiters mostly counsel against all of them. A zero can be read by the system as a missing value and rejected. A fantasy number can flag the application for the wrong reasons. Text like "Open" often lands in the same database field and is parsed by software that does not know what to do with it.

The better move, when a form insists, is to treat the box as what it is: a place for a number, not a test of character. Enter the low end of your researched range, or the midpoint if you are comfortable, and say nothing more. The number will be screened, but it will also be the opening figure in a conversation you can still steer. If the form asks for a single figure and the posting shows a band, the band's midpoint is a defensible answer.

There is a newer wrinkle worth knowing. Some applicant tracking systems now let candidates choose "not specified" or "open to negotiation," and a handful of employers have dropped the field entirely under the pressure of state posting laws. Where the option exists, using it is a statement, not a dodge. Where it does not, the midpoint strategy above beats every forum workaround, because it keeps you in the running and leaves the real negotiation for later.

The laws are changing the field

The biggest shift in how the question works is happening outside the form, in state law. More than a dozen states now require employers to post a pay range, and the list has grown steadily since Colorado became the first in 2021. The table below shows six of them; the details differ, but the pattern is the same: the range the form asks you to invent is, in these states, already printed on the page.

Six states that require pay ranges in job postings, with the year the requirement took effect.

State	Range required since	What the posting must show
Colorado	2021	Pay range and benefits
California	2023	Pay scale for the role
New York	2023	Compensation range
Washington	2023	Salary range and benefits
Illinois	2025	Pay scale and benefits
Massachusetts	2025	Pay range

Massachusetts, Illinois, and Minnesota are among the newest entrants, and New Jersey and Vermont followed in 2025, so the map keeps filling in. The Economic Policy Institute, which tracks the research on these laws, has summarized studies finding that pay transparency is associated with higher pay for women and a smaller gender pay gap, while employers have adjusted by posting wider ranges that preserve room to negotiate.

The width of a posted range is itself information, and compensation professionals read it the way sailors read a barometer. A narrow band, say 10 percent, usually means the employer has priced the role tightly and has little room to move. A wide band, 30 percent or more, often means the employer is covering multiple levels in one posting, or is prepared to pay for the right candidate. Either way, the range tells you where the negotiation starts, which is precisely the information the expectation field once existed to keep from you.

For a candidate, the practical effect is simple. When a posting includes a range, the expectation field stops being a guessing game and becomes a consistency check: the employer wants to see whether your number fits the band it already published. The cleanest answer, several recruiters said, is the range itself, or a point inside it. Anything else invites a question the candidate has already answered.

Before you hit submit

By the time the cursor is in the field, the work should already be done. Decide, before you open the application, three numbers: the floor you will not go below, the figure you would be glad to get, and the range you are willing to type. Research the market first. Glassdoor and Payscale publish ranges by title and metro, and Marketivate's salary calculators and salary converter turn posted salaries into comparable figures when offers come in different forms.

Then match the strategy to the channel. A form gets a researched range or a midpoint. A human being gets the band question, asked once, with the research at hand. An email reply gets a short sentence that names a range and leaves the door open: "Based on my research and the scope of this role, I'm targeting $105,000 to $115,000. I'm glad to discuss the full package." The sentence does two jobs at once: it gives the recruiter a number to enter, and it tells the recruiter this candidate came prepared.

Consistency matters more than candidates realize. If you type $105,000 into a form and then say $125,000 in the first call, the recruiter will notice, and the discrepancy will become the subject of the conversation. Keep a note of what you wrote, in which application, and say the same thing twice. The field, after all, is a data point. The least dangerous way to fill it is to make it a true one.

The field is shrinking

The trajectory of the expectation field is fairly clear. State posting laws keep spreading, and each new law removes a little more guesswork from the question. Applicant tracking systems are adding explicit "open" options, which suggests the software industry expects the blank to become respectable. And the recruiters interviewed for this article, whatever they thought of the field, agreed on one thing: the candidates who handle it best are the ones who treat it as a routine part of the salary conversation rather than a trap to be outsmarted.

If the question survives, it will keep shrinking in importance as more of the answer becomes public. In the meantime, the field belongs to you for the ten seconds it takes to fill it. A candidate who has done the research, picked a floor, and chosen a range has already answered the question the way a negotiator would, before the software, the recruiter, or the hiring manager ever sees the number. That is the quiet advantage of treating the box as what it is: a first move, not a confession.