Desired Salary on Applications

You are most of the way through an online application and you hit the field that makes everyone pause: desired salary on the application form. There is no “let us discuss” button, the field will not accept “negotiable,” and you have to type something to move on. What you put there can quietly knock you out before a human reads a word, or it can box you into a number lower than the role pays. This is a different problem from the salary question in an interview, and it deserves its own playbook.

When the field is required and will not accept text

Plenty of forms make this field mandatory and reject words. “Negotiable,” “competitive,” and “open” all bounce, so your usual dodge does not work. You have three real options, each with a tradeoff.

A range. The most common and usually the safest, when the form allows it.
A single number. Sometimes the only thing the field accepts.
A zero or a one. A workaround people use to skip past the field. It carries its own risk, below.

The form’s format dictates a lot. Some accept “90,000 to 110,000,” some want one integer, some reject anything but digits. Read what the field will take before you decide what to say.

Desired salary on an application: range vs single number vs zero

Each entry sends a different signal. Here is what each one risks.

A range. Put the number you actually want near the bottom of the range, because employers tend to anchor to the low end. A range of “95,000 to 110,000” reads as flexible while protecting a real floor. The risk is anchoring low, so do not set the bottom below what you would accept.
A single number. When forced to one figure, give a specific researched number rather than a round guess. Specific numbers (“104,000”) read as informed; round ones (“100,000”) read as a placeholder. The risk is rigidity, since one number leaves no visible give.
Zero or one. Typing “0” or “1” is a known trick to slip past a required field without committing. The risk is real: some systems read it literally and either filter you out or flag the application as incomplete. Use it only when the field rejects ranges and you genuinely have no market read yet, and know it can backfire.

There is no universally correct answer. There is only the answer that fits the format while protecting your floor and avoiding a knockout.

How a number can trigger a knockout

This field is not always a note for a recruiter. Sometimes it feeds a filter that screens applications before anyone sees them, the same kind of gate that quietly handles other entries on the form. Two ways a number gets you cut:

Too high. If your figure sits above the band budgeted for the role, an automated screen can drop you for being out of range, even when you would have happily negotiated down.
Too low. A figure well under the band can read as a mismatch in level or as a signal you do not understand the market, and some screens treat that as a flag too.

The lesson is not to game the filter. It is that a number typed without research is a coin flip on a gate you cannot see. The defense is knowing the actual range for the role before you type anything. Our guide on knowing your market rate covers how to find that band from posted ranges and salary data.

Tie the number to your researched market rate

The way out of all of this is preparation, not cleverness in the moment.

Anchor to the role and location. Salary tracks title, level, and metro. Pull the real band for that specific combination, not a national average for a vaguely similar job.
Use posted ranges as ground truth. Pay-transparency rules mean many postings now list a band. If the same company or its peers post ranges, you have your answer with no guesswork.
Set a floor you will not go under. Decide the lowest number you would accept, then make sure whatever you type, range or single figure, never dips below it.

When your entry sits on a real band, the field stops being scary. A range that brackets the posted band, or a single number near the top of it, reads as someone who did the homework. This is also where a tool like Linora helps with the rest of the form: it starts each application from your profile and a tailored resume, so the salary field is one of the few entries you have to think hard about rather than one of forty.

This is not the interview salary question

One important distinction. The salary field on a form and the “what are your expectations” question in an interview are different events with different rules.

The form is a static filter with no room to read the conversation. You commit to a number cold. The interview question is a live exchange where you can ask about the band first, defer, or anchor based on what you have learned about the role. Strategies that work in a conversation, like turning the question back, simply do not exist on a form. For handling the spoken version, see the salary expectations question.

Filling the same fields across dozens of applications, salary included, gets tedious fast. Linora’s browser extension fills the application form with the details from your profile and your tailored resume, then you check every field, including this one, and submit yourself. If you would rather not retype the same answers on every form, see how the extension works.

If you are unsure what to put, see current salary ranges by role and anchor your answer to real data.