The answer depends on the field type. Most guides ignore this.
Salary expectation fields are not all the same. A free-text box, a numeric-only input, a min/max pair, and a dropdown each constrain what you can say — and each changes the risk. The right move for a numeric-only box (enter your target) is the wrong move for an optional field (leave it blank). No widely-read guide separates these cases. This one does.
Response by field type
- Optional: Leave it blank. Every extra answer is a free filtering signal for the employer and a risk for you.
- Required — free text: Give a short range with your target as the floor and a stretch number above it, plus one sentence about total compensation.
- Required — numeric only: Enter your target number — the amount you would say yes to without hesitation. Never your floor and never a placeholder.
- Required — min/max range: Minimum is the lowest you would genuinely accept. Maximum is a realistic stretch, not a fantasy. Keep the range tight around your target.
- Required — dropdown: Pick the band that contains your target. Do not select the lowest band you would accept, because it can cap the eventual offer.
If you want the exact copy-ready phrasing for your current form, use the free salary expectations response picker. It never asks for your actual salary number.
Your number is compared against a budget band.
Many applicant tracking systems treat the salary field as a knockout question. Your number is compared against the budget band the recruiter entered for the role. A number outside the band can end the process without any resume review.
The ATS does not judge whether your number is reasonable. It checks whether the number falls inside a range the employer set. Outside the range, the application is filtered out automatically — often before a person is ever involved.
This is why a placeholder value is dangerous. A zero or a single digit will almost always fall outside the band and trigger the rejection. The safest answer when a field is optional is to give no answer at all.
Never enter these values.
Newer ATS configurations are trained to flag and auto-reject the most common placeholders. Entering any of the following is worse than leaving a field blank.
- $0, $1, 000, 999, or 99999
- Your current salary where it is legally restricted
- A range wider than about $30,000
- A single low number with no range attached
Placeholders fall outside the budget band and trigger an automatic knockout. A disclosed current salary can anchor every future offer below your real worth. A huge range signals you have not done the research, and a single low number can cap the offer you eventually receive.
In more than 18 US states and many municipalities, employers are legally restricted from asking for your current or prior salary. If you are in one of those jurisdictions and the form still asks, you can decline or leave it blank — the employer cannot require it as a condition of your application.
A single low number can cap the offer.
If you enter $70,000 because it feels safe, and the role was budgeted at $85,000–$95,000, the recruiter has no incentive to offer more than what you asked for. Your entry becomes the ceiling, not the floor.
If your target is $90,000, a range of $90,000–$100,000 keeps you inside most budget bands and prevents a low anchor. A range also signals flexibility, which is what the field is really asking about.
For numeric-only fields where you must enter a single number, enter the target — not the lowest you would accept. You can always negotiate down later; you will rarely negotiate up from a number you typed into a form.
Pay-transparency laws change the calculation.
If you are applying in a pay-transparency jurisdiction, the employer is often required to post a salary range. That range is the single most useful input for your answer — it tells you the band before you ever type a number.
US states requiring salary ranges in postings
- California
- Colorado
- New York
- Washington
- Illinois
- Massachusetts
- Maryland
- Minnesota
- Vermont
- Hawaii
- New Jersey
- Maine
- Virginia (effective 2026)
Outside the US, the EU Pay Transparency Directive (2023/970) requires employers to share pay ranges and is being phased in through 2026. The UK government opened a consultation on pay-transparency requirements and is expected to move in a similar direction.
You have the right to ask for the range before entering a number. Doing so protects you from both the knockout filter and the lowball trap. The response picker adds this note automatically when you select a transparency state.
Check salary fields before submitting any autofilled application.
Autofill and auto-apply tools can fill the salary field from a stored profile, but field names are not standardized. One form may label the field “Expected compensation,” another “Desired salary,” and a third may split it into two fields. When the tool guesses wrong, it can enter a number that is far below your real target.
Reported cases describe autofill tools sending applications with a salary figure roughly $20,000 below the range stated in the job posting — purely because the tool matched the wrong stored value to the salary field. Always review the salary field as part of your final check, the same way you would review your name and email.
The broader lesson is in the autofill versus auto-apply guide: automation should fill, then stop. Final submission should stay with you.
What the research says about asking and negotiating.
- 45% of workers negotiate; of those who did, 78% received a better offer. (Resume Genius, 2025, n=1,000)
- 55% of Americans accept the first offer without negotiating at all. (Resume Genius)
- 75% of job seekers are more likely to apply when a salary is listed in the posting. (Indeed, 2024, n=5,000+)
- The median candidate ask in 2026 is $162,500. (Pin, aggregated from 220,000+ candidate replies)
- The viral reply — “My expectations are that you will provide a salary range” — reflects a growing refusal to name a number first. It was covered by Newsweek and resonated because it flips the transparency question back to the employer.
The pattern across these sources is consistent: most people do not negotiate, most people who do negotiate get more, and most people prefer to see a range before they apply. Your salary-expectation answer is the earliest place you can act on all three.
A 30-second check before you submit.
- Identify the field type. Optional, free text, numeric, range, or dropdown. The response differs for each.
- Find the posted range. If you are in a transparency state and none is posted, ask before entering a number.
- Enter your target, not your floor. Use a range with your target as the bottom where the field allows it.
- Verify no placeholder leaked in. No 000, no 999, no $1.
- Confirm autofill. If a tool filled the field, check that the value is the one you intended for this role.
For the exact wording matched to your field type and location, use the salary expectations response picker.