What to Put for Desired Salary on a Job Application
No time for long YouTube tutorials? Try Guidy and get it all done in minutes. It sits right on your screen and points you to exactly what to do in real time. And it works on any software or browser, in any language.
Try for free
The desired salary field is the one part of a job application where a single number can cost you the interview, and it usually appears before you know anything useful about the role. Answer too high and you may be filtered out automatically. Answer too low and you have set a ceiling on an offer you have not yet been made. The good news is that the field is far less binding than it feels, and there are four legitimate ways to answer it depending on what the form allows. Here is how to decide which one to use.
First, work out what the job actually pays
Every strategy below depends on this, and it takes about fifteen minutes.
Check the job posting itself. Many US states and cities now require employers to publish a pay range, so the answer may already be in front of you. If a range is listed, the safest answer is a number within it, generally in the upper half if your experience matches the requirements.
If no range is given, triangulate. Look at salary aggregator sites for the same title in the same city, check comparable postings from competitors, and adjust for company size, since a large employer typically pays more for the same title than a small one. Search the job title plus your metro area rather than a national average, because location changes the number more than almost anything else.
Set two figures before you write anything: the number you would be pleased with, and the lowest number you would accept. You will use both.
The four ways to answer
Leave it blank. Best when the form allows it, which is more often than people assume. A blank field is not usually disqualifying and it keeps every option open.
Write "negotiable" or "open." Best on forms with a free text field that will not accept an empty answer. It signals flexibility without committing, and no reasonable employer treats it as evasive.
Give a range. The strongest answer in most situations. Make the bottom of your range a number you would genuinely accept, because that is the number you will be offered. A spread of ten to fifteen percent reads as considered; a spread of forty percent reads as a guess.
Give a single number. Necessary when the form demands one. Pitch it slightly above your target rather than at it, since the figure you name becomes the starting point rather than the finish.
When the form will not let you skip it
Online application systems frequently require a numeric entry, and this is where people improvise badly.
Do not enter 0. Some applicant tracking systems read it literally and sort you into the lowest band. Others display it to a recruiter exactly as typed, which reads as either a mistake or a joke.
Do not enter placeholder numbers such as 1, 999999, or 123456. They are obvious, they look careless, and in a system that filters by salary they will do exactly the wrong thing.
Enter a real number at the top of your researched range. If the field permits any text at all, some applicants enter their target followed by a note that it is negotiable, which works when the field is long enough.
If the field accepts text and you want to defer honestly, "negotiable based on the full compensation package" is accurate and gives you room, because the base salary genuinely is only part of what you are evaluating.
The distinction worth knowing
There is an important difference between two questions that look similar.
Salary history is what you currently earn or have earned. Many US states and cities have banned employers from asking this, precisely because anchoring new offers to old salaries perpetuates existing pay gaps. If a form asks for your current salary and you are in a jurisdiction with such a ban, you are generally not obliged to answer.
Desired salary is what you are asking for going forward. This is almost always a fair question and is not covered by those bans.
Rules vary by state and city and they have changed repeatedly, so check the rules where you are applying rather than assuming. The practical takeaway is simple: your desired salary should be built from what the role pays, not from what you currently earn.
Four mistakes that cost money
Anchoring to your current salary. If you are underpaid now, asking for a small increase locks in the underpayment. Price the job, not your history.
Giving a range with a bottom you would refuse. You will be offered the bottom. Every time.
Being the first to name a number when you do not have to. Whoever names a figure first sets the anchor, which is why "negotiable" is a genuinely strong answer when the form permits it.
Forgetting everything that is not salary. Bonus, equity, employer retirement contributions, healthcare costs, and paid leave can be worth a great deal. A slightly lower base with materially better benefits is often the better offer.
The field is less final than it feels
Worth saying plainly, because the anxiety around this field is out of proportion to its weight. What you write is a starting point, not a contract. Nobody is held to it. Once you have interviewed, learned what the job involves, and been told about the wider package, you can revise your expectations, and doing so with a reason attached is completely normal.
The genuine risk is only at the extremes: a number far above the band gets you screened out before anyone reads your application, and a number far below it becomes the offer.
Application forms are full of fields like this one, where the wording gives no clue what the employer actually wants and a bad guess has consequences. Guidy reads the form on your screen and explains what each field is really asking for and how to answer it, one field at a time, which is covered on our AI form filler page.
Key takeaways
● Research the number before you write anything. Many US states and cities now require employers to publish a pay range, so it may already be in the posting.
● Four legitimate answers, depending on what the form allows: leave it blank, write "negotiable," give a range, or give a single number pitched slightly above your target.
● The bottom of your range is the number you will be offered. Make it one you would genuinely accept. A spread of ten to fifteen percent reads as considered; forty percent reads as a guess.
● Never enter 0 or a placeholder such as 1 or 999999. Applicant tracking systems either read them literally and sort you into the lowest band or show them to a recruiter exactly as typed.
● Salary history and desired salary are different questions. Many US jurisdictions have banned employers from asking what you currently earn; what you are asking for going forward is almost always fair game.
FAQs
What should I put for desired salary on an application?
If the field can be left blank, leave it blank. If it accepts text, "negotiable" keeps your options open. If it requires a number, enter a real figure at the top of the range you researched for that title in that city, rather than a placeholder.
Should I put 0 for desired salary?
No. Some applicant tracking systems take it literally and sort you into the lowest salary band, and a recruiter reading it directly will see either an error or a joke. Enter a researched number instead, or "negotiable" if the field accepts text.
Is it better to give a range or a single number?
A range is usually better, with one condition: make the bottom of it a number you would genuinely accept, because that is what you will be offered. Keep the spread to roughly ten to fifteen percent so it reads as researched rather than uncertain.
Can I change my desired salary later?
Yes. What you put on an application is a starting point, not a commitment. Once you understand the role and the full package, revising your expectations with a clear reason is standard practice and is expected in most hiring processes.
Do employers have to tell me the salary range?
In a growing number of US states and cities, employers are required to publish a pay range in the job posting. The requirements differ by location and have changed frequently, so check the rules where you are applying. Where a range is published, use it.
