What to Put for Desired Salary on a Job Application
The interview version of the salary question at least lets you read the room. A desired salary field on a job application gives you none of that — just a blank box, sometimes required, with no context about who's reading it or what happens with the number you type. That's a genuinely different problem from the interview conversation our salary negotiation guide and salary-expectations-question page cover, which is why it gets its own page here.
There's no universally correct answer, because application-tracking systems handle this field differently — some use it as a hard filter, some just pass it through to a recruiter as a data point, and some don't even look at it until much later. What you should type depends partly on which of those is likely true, and partly on how badly you want the role.
Below is a comparison of your real options, when each one makes sense, and the risk it carries — plus exact fills for the most common field formats.
Your options, compared
Every option below is defensible in the right circumstance. None is universally safe.
| Option | When to use it | Risk |
|---|---|---|
| Leave blank (if the field is optional) | Field is clearly marked optional and you'd rather discuss pay live | Some systems flag incomplete fields, which can slow processing even when technically optional |
| "Negotiable" | Field accepts text and you want maximum flexibility preserved | A minority of ATS filters treat free text as unusable and may not pass your application through cleanly |
| A range | Field accepts a range, and you've done your salary research | Too-wide ranges look unresearched; too-narrow ranges limit your own flexibility |
| A specific number | Field requires a number, or you have a clear, confident target | A single number becomes your anchor — going in low limits your negotiating room later |
| "$0" or "1" as a placeholder | Field is numeric-only and technically required but you want to avoid committing | Can trigger an automatic minimum-salary filter and screen you out entirely — generally not recommended |
If the form gives you any choice at all, a range beats a single number in almost every case — it keeps room to negotiate later while still giving the system something concrete to work with.
Template: exact fills for common field formats
Here's what we'd actually type into the most common versions of this field, based on your researched range from our salary research guide.
- Free-text field, optional: "Negotiable, open to discussing based on full scope and total compensation."
- Free-text field, required: "$[X]–$[Y], flexible depending on full role scope and benefits."
- Two separate numeric fields (min/max): Min = the bottom of your researched range; Max = slightly above your true target, not your absolute ceiling.
- Single numeric field, required: Your true target number, not the bottom of your range — this becomes your anchor, so don't lowball it out of fear of being screened out.
- Dropdown with salary bands: Select the band that contains your target number, even if it spans a wider range than you'd state verbally — dropdowns don't allow nuance, so pick accuracy over caution.
Let your resume do the convincing before the number does
Jobedly builds you a free tailored resume and matched cover letter automatically, so the desired-salary field isn't the only thing carrying your case to a recruiter.
Build a winning resume freeThe myth that a high number always screens you out
The safer framing: your number should reflect your researched market range for that specific role and level, not a padded guess meant to leave room for negotiation. Padding a number you don't believe in is what tends to create the mismatch that gets flagged.
When the form forces a genuinely hard choice
Some systems make this field required, numeric-only, and unskippable, with no range option. In that specific case, a few extra considerations help.
- Check whether the job posting itself already published a range — if so, answer inside that range rather than guessing blind.
- If no range is published, use your own researched target from BLS wage data and comparable postings, not a number pulled from thin air.
- Don't answer with an extreme low number to "get past" the field — it can become your anchor for the rest of the process if the system passes it through to a human.
- If you're deeply unsure and the role is a strong fit otherwise, err toward the accurate middle of your researched range rather than either extreme.
The overall labor market context matters here too — with U.S. unemployment at 4.2% per the BLS Employment Situation and wage data from the BLS Occupational Employment and Wage Statistics showing meaningful variation by metro area, a number that looks "high" in one market can be squarely at median in another. Don't anchor your form answer to a number you saw online without checking whether it matches your actual location and role.
How recruiters actually use this field, behind the scenes
It helps to know what happens to this number after you hit submit, since that changes how much weight to put on any single answer. At some companies, the field never reaches a human until well after an initial resume review — it's just stored data, referenced only if you make it to a recruiter call. At others, it's an active pre-screen filter that runs before anyone reads your resume at all.
When you genuinely can't tell which pattern applies, default to treating the field as if it matters immediately. It costs you nothing to answer it accurately, and it can cost you a lot if it turns out to be an active filter you treated as an afterthought.
Why the form and the interview question aren't the same problem
A form field is a one-shot, no-context answer read by a system (and eventually a person) with no chance to explain your reasoning in the moment. The interview version of this question is a live conversation where you can deflect, ask questions, and adjust based on what you learn — which is why we treat answering the salary-expectations question live as a separate skill from filling out this field.
If you're preparing for both at once, get your researched range settled first — it should be the same number feeding both the form and the live conversation, not two different guesses.
Let the AI team do the grinding
Jobedly scores every role 0–100 the moment it posts, rewrites your resume to win in seconds, and drafts a matched cover letter automatically. Your first tailored resume is free.
Get your free tailored resumeFrequently asked questions
Is it okay to leave the desired salary field blank on an application?
Should I put 'negotiable' for desired salary?
Will a high desired-salary number get my application rejected automatically?
What if the field requires a single number and won't accept a range?
Does the desired-salary field on a form matter as much as the interview question?
Glossary
- Applicant tracking system (ATS)
- Software employers use to collect, filter, and route job applications, which may treat a desired-salary field as a hard filter or a soft data point depending on configuration.
- Hard filter
- A screening rule that automatically disqualifies applications outside a set numeric threshold, such as a desired-salary field set too high or too low.
- Anchor number
- The first specific salary figure introduced into a hiring process, which tends to influence the range of later negotiation.
- Salary band
- A pre-set range of acceptable pay for a role, sometimes offered as dropdown options on an application form.