04 Sept 2026
You have the resume attached, the work history typed out, and one field left before the submit button turns blue. It says desired salary, it has a red asterisk next to it, and the posting never mentioned money at all. You try to skip it and the page scrolls back up with an error. You have four more applications open in other tabs, and you are now doing math about a job you may never hear back from.
The field exists because the employer wants a filter and a starting point. Some teams use the answer to sort applications before a human reads them, some use it to decide whether a first call is worth booking, and some barely look at it until an offer is drafted. You cannot tell which from inside the form, and your number will sit in your candidate record long after you forget what you wrote.
This guide compares the five answers you can actually give in that box, shows what each one signals and where each one breaks, and gives you a ten minute method for picking a figure when the posting has no range. It also covers hourly, contract, and cross-border applications, and how to keep the conversation open later.
Quick answer: If the field accepts text, "Negotiable" or "Open, based on the full compensation package" is the lowest risk answer, and it is the simplest thing to put for desired salary when you have no market data. If the field accepts digits only, enter a figure from the upper third of the market range for that role and location, or, when the form allows two values, a range about 10 to 15 percent wide whose bottom number is the lowest amount you would actually accept. Zero and 1 are technical workarounds for a required numeric field, not answers, so mention them out loud on the first call.
The field does three jobs at once, and they pull in different directions. First, it filters. If a team has a budget ceiling and a stack of applications, a figure far above the ceiling is an easy reason to stop reading. Second, it opens a conversation. A recruiter who likes your background and sees a workable number has a reason to call and check the details. Third, it becomes an anchor. When the offer is being put together, your own figure is sitting in the file, and nobody in the room is motivated to argue it upward for you.
That first job is why an empty or evasive answer is not automatically the safe move. Screening is a sorting exercise, and a blank line gives the person sorting nothing to work with. An awkward but explainable number may be easier to discuss later than a blank required field.
Form behavior varies between employers and between versions of the same software, so treat any claim about what a field accepts as something to test on the page in front of you. Type your answer, hit submit, and see what happens. That five second test beats any general rule.
Here are the five things people type into the desired salary field on an application, what each signals, and where each falls apart mechanically.
| Option | What the employer reads | What breaks in the form | Main risk | When it fits |
|---|---|---|---|---|
| One specific number | A clear expectation you have thought about | Nothing, this is what most numeric fields are built for | Becomes the ceiling of your own offer | Posted range exists, or the role is standard and you know the market |
| A range | Flexibility with a floor you will defend | Text fields accept it, single numeric fields reject it | Readers focus on your bottom number | Unfamiliar market, wide role, or your level is unclear |
| "Negotiable" or "Open" | You want context before committing | Fails instantly in digits only fields | May read as evasive to a screener who wants a figure | Text field, early stage, posting gives no range |
| Zero or 1 | Usually read as a placeholder, sometimes as an error | Passes validation, which is the whole point | Looks odd if you never explain it | Required numeric field and you refuse to anchor yourself |
| Blank or a dash | Nothing, or a skipped question | Blocks submission when the field is required | Sorted out with no chance to explain | Optional field only |
Two patterns are worth noticing in that comparison of desired salary on application forms. A text field gives you room to answer in words, so use the words. A numeric field gives you no room at all, so the only real decision left is which number and how you plan to explain it later.
Give one figure when you have something solid to base it on. The clearest case is a posting that already publishes a range, which happens more often as pay transparency rules spread. If the ad names a band, the employer has told you what they budgeted, and a number inside that band is usually easier to defend because it tracks the posted range.
Where inside the band matters. Pick from the upper part if your experience matches or exceeds the requirements, and closer to the middle if you are stepping up a level or switching functions. Taking the very top is possible, but be ready to explain what justifies it, because that is the first thing a recruiter will ask.
The second case is a role you genuinely know: same title, same industry, same city, and you have seen several current postings with numbers attached. Here you are not guessing, you are reporting. State desired compensation as one clean annual figure, rounded to the nearest thousand.
Do not attach conditions inside a numeric field. Notes like "plus bonus" or "depending on benefits" either get stripped out or make the value unreadable. If the package matters to your number, and it usually does, that belongs in the first conversation. Our guide to total compensation breaks down which pieces to count before you set a base figure.
A range works when you have real uncertainty about the market, the level, or the scope of the job. It answers the question without pretending to a precision you do not have, and it gives the reader a reason to call and ask which end applies.
Keep it narrow. A spread of roughly 10 to 15 percent reads as an informed estimate. A spread of 50 percent reads as a guess and invites the reader to ignore the top entirely. If your honest uncertainty is wider than that, the problem is missing information, and the fix is finding a comparable posting rather than stretching the numbers.
Now the rule that matters most: assume only your bottom number will be read. Whatever you write as the floor is the figure carried forward into budgeting conversations, so the floor is not a dream discount, it is the lowest amount you would sign for without resentment. Set the top as your realistic target, because you may be asked to justify it in the next five minutes.
Many text fields accept words. If the box accepts letters, "Negotiable" is a legitimate answer, and "Open, based on the full compensation package" is stronger because it names a reason instead of just deferring. A qualifier like "Negotiable, targeting market rate for this level and location" reads as prepared rather than avoidant, which is the usual worry about writing desired salary negotiable in an application.
Numeric fields generally reject letters. There is no version of "negotiable" that fits in a digits only box, so do not plan around it. When validation rejects your text, you are back to the same choice: a number you can live with, or a placeholder you will have to explain.
Zero and 1 are placeholders. People use them because a required field will not release the form otherwise and they would rather not anchor themselves yet. That is defensible, with one condition: raise it yourself at the first opportunity. An unexplained zero can be read as a data entry mistake, and a recruiter moving fast may not stop to ask.
Blank is only an option when the field is optional. If the form submits without a value, leaving it empty is fine and nobody will chase you. If it is required, blank is not a strategy, it is a form that never gets sent. A dash or "N/A" in a text field passes validation and says less about you than "Negotiable" does.
One more thing to check locally. Rules about whether employers may ask for salary expectations or salary history differ by jurisdiction and they change. Look up what applies where you are applying rather than assuming the version you read about online covers your situation.
If the role is hourly, answer in hourly terms. A number with no unit gets read according to the reader's assumption, and an hourly rate landing in a field someone reads as annual makes you look careless. When the field allows text, write the period explicitly. When it does not, match the unit used in the posting, since that is the unit the reader has in mind.
Contract work carries its own arithmetic. A contract rate usually has to cover gaps between engagements, unpaid time off, and costs an employee does not carry, so the raw hourly figure is not comparable to a salaried one. Do the conversion before you type. Our walkthrough on hourly to salary conversion covers the math, and the rule here is simple: always state the period.
Cross-border applications add currency and tax treatment. Name the currency using its standard code rather than a symbol, since a dollar sign is ambiguous across several countries, and default to the currency of the hiring location unless the posting says otherwise.
Gross or net is the second trap. Many employers discuss gross pay, but conventions differ by country and industry. In a text field, add one word: gross. If the field is numbers only, note the assumption you used so you can restate it on the first call. Two people using different conventions can look far apart when they are only a few points apart.
You do not need a paid salary report to answer this field. You need three or four comparable data points and a decision rule.
Search the same job title in the same city or country and filter for postings that publish a range. In many regions those exist because of transparency rules, and they are the closest thing to public pricing you will get. Open three or four and write down the low and high figures, skipping listings with a very different seniority label.
Take the lowest bottom and the highest top from your sample. That crude band is too wide to use, so trim it: drop any posting that does not match your scope, then keep the middle cluster where two or more ranges overlap. That overlap is your working band. You are trying to avoid being obviously wrong, not to be exactly right.
A role in a high cost metro sits differently than the same title in a smaller market or a remote posting priced to a national band. Then adjust for level: if the posting lists responsibilities beyond your current scope, the number should reflect the job being advertised, not the one you hold today.
Choose a target in the upper third of your working band, and separately decide the floor you would accept. If the form takes one number, enter the target. If it takes a range, enter floor to target. Write both down, because in two weeks a recruiter will ask what you put and you will not remember.
When your search comes up thin, you have one more source: ask. If you can reach a recruiter before applying, a direct budget question may give you a better number than any estimate, and that approach is covered in our piece on job ads with no salary listed.
A number in a form is a starting position, not a signed agreement, and nothing obliges an employer to revisit it. The normal way to reopen it is new information: the scope turned out broader than the ad suggested, or the package is structured differently than you assumed. That is more persuasive than simply changing your mind.
Keep two short bridge phrases ready so you are not improvising. On the first call: "The figure in the application was based on the posting, so I would like to hear more about the scope before I commit to it." At offer stage: "Now that I understand what the role covers, I would like to revisit the base number we started from."
That is as far as this article goes on wording. Full scripts for the recruiter's salary question, including how to hand the question back, live in how to answer the salary expectations question. Scripts for negotiating after an offer is on the table, including counteroffers, live in salary negotiation scripts.
One habit protects you either way: consistency. Whatever you typed is what you should be able to repeat, and explain, weeks later. Contradicting your own application without a reason costs more credibility than a slightly awkward number ever will.
These look like the same question and they are not. The form is one line with no context, no chance to ask anything back, and no idea who reads it. It will be read literally by whoever opens your record.
The conversation is an exchange. You can ask about the band, the level, the bonus structure, and the location policy before committing to a figure, and that kind of exchange is more natural in a call than in a form field. What is evasive in a form can be normal in a call, and what works in a call cannot be typed into a numeric box. Treat the form answer as provisional: enter something defensible, note what you entered, and say more when a human is on the other end.
Build a rough band from three or four current postings for the same title and location that publish ranges, then pick a point in the upper third of that band. If the field takes text, write "Negotiable" with a short qualifier instead. Either answer is provisional, and you can refine it once you know the scope.
In a text field it is a reasonable answer, especially early in a process where you have no information about the band. It reads better when you attach a reason, such as being open pending the full package. In a numeric field it is not an option at all, since the form will not accept letters.
You can ask, and the usual opening is new information about the scope or structure of the role rather than a simple change of heart. There is no guarantee the employer will move, since your figure may already be recorded in the budget for the role. Raising it early, on the first call, is easier than raising it after an offer is drafted.
Use a single number when a range is posted or the role is one you know well, and a range when the market or the level is genuinely uncertain. Keep any range narrow, roughly 10 to 15 percent, and set the bottom at the lowest figure you would accept. Assume the bottom is the number that gets remembered.
State the currency using its standard code, name the period, and default to the hiring location's currency unless the posting says otherwise. Assume amounts are before tax unless the form indicates otherwise, and say so in a text field if you can. If the field is numbers only, note your assumption and restate it on the first call.
It is a workaround for a form that will not submit, and it may be read as a placeholder or as an error, depending on who opens the record. If you use it, mention it at the first opportunity so it does not sit there unexplained. When the field accepts text, a word like "Negotiable" communicates the same intent more clearly.
Run through this before the form goes out, while you can still edit the answer.
The first time this takes ten minutes. By the tenth application it takes two, because the band is the same band and only the location and level adjustments change.
09 Sept 2026
A practical way to turn an hourly rate into a comparable annual number, with the assumptions spelled out instead of hidden. Includes a conversion table, a side-by-side offer worksheet, and the cases where hourly actually pays more.
10 Sept 2026
Explore 10 high-paying entry-level jobs in the U.S. that require no prior experience. Compare salaries, qualifications, career paths, and job search tips
10 Sept 2026
Explore 20 high-paying remote careers with U.S. median salaries above $100K. Compare pay, qualifications, remote fit, and job-search tips
08 Sept 2026
A practical, script-backed guide to asking for and getting a raise at work.
10 Sept 2026
Explore the average business analyst salary in the US, including pay by experience, location, industry, job level, and tips for negotiating an offer
09 Sept 2026
A copy-and-adapt template for online job applications, field by field. Covers the answers most people stall on: salary expectations, reason for leaving, contact permission, and knockout screening questions.
