Should You Put Expected Salary on a Job Application Form?
By Pinal Dave | Last updated: 2026-08-01
TL;DR: If the field is required, give a researched range rather than a single number, and anchor it slightly above your true minimum. If it's optional, you can often leave it blank or write "negotiable," but in states with pay transparency laws, many job postings already list a range — check that first before guessing.
Why This Field Trips People Up
Application forms often force a single number into a field designed for a range, and applicants worry that number becomes a hard ceiling before any negotiation happens. In reality, most applicant tracking systems store this as a screening filter, not a locked commitment — but a lowball number can anchor the eventual offer, so it's worth answering deliberately rather than rushing through the form.
Handling the Field by Scenario
| Situation | Recommended Approach |
|---|---|
| Field is required and only accepts one number | Give the midpoint or slightly above the midpoint of your researched range |
| Field accepts a range | Enter your real range, with the low end still comfortably livable |
| Field is optional | Consider leaving blank or writing "negotiable" unless a number could help you clear an initial filter |
| Job posting already lists a salary range (pay transparency states) | Answer within that posted range, don't lowball below it |
| Field asks for "current salary" | Skip or decline where legally allowed — many states and cities ban this question outright |
Step-by-Step: Filling Out the Field With Confidence
- Research the market rate first. Use recent postings for the same role, level, and location — pay transparency laws in states like California, Colorado, New York, and Washington mean many postings already show a real range.
- Check if the job posting already lists a range. If it does, use that as your anchor rather than guessing independently.
- Answer at or slightly above the midpoint, not your bare minimum — the form number often becomes the starting point for negotiation later.
- Use "negotiable" only when the field truly allows free text. Many ATS systems reject non-numeric entries in a "required" salary field, so check before assuming you can skip it.
- Never lie upward significantly. A number wildly inflated beyond market rate for the role can get you filtered out before a human ever reviews your application.
- Keep a personal record of what you entered. If you're later asked in an interview, your form answer and your verbal answer should be consistent.
- Remember it's a screening input, not your final word. Real negotiation happens after interviews and a written offer, regardless of what was entered on the initial form.
Frequently Asked Questions
Can employers legally ask for my current salary? In many U.S. states and cities, no — salary history bans prohibit employers from asking about your current or past pay, though they can still ask for your expected salary or desired range.
What happens if I put a number that's too low? It can anchor the eventual offer lower than necessary — this is exactly why a researched range at or above the midpoint is safer than guessing conservatively.
Will leaving the field blank get my application rejected automatically? It depends on the system — some ATS platforms require an entry to submit, in which case use a reasonable range rather than leaving it empty if the form won't let you.
Should my answer match what I say in the interview? Yes — consistency matters, so keep a note of what you entered on any application form so your verbal answer during screens doesn't contradict it.
Does answering honestly on this field hurt my negotiating leverage later? Not significantly if you gave a reasonable range — most of the real negotiation happens after interviews, once the employer already knows they want you specifically.
What if the posted salary range seems too low for my experience? Apply anyway if the role is otherwise a strong fit, and use the interview process to make the case for the top of that range or ask directly if there's flexibility.