Desired Salary on a Job Application: What To Put in the Box

If the desired salary field accepts text, write "negotiable" or note that you are open to the posted range. If it requires a number, enter the bottom of a range you have researched for that title, level, and metro area, and make sure it is a number you would genuinely accept. Do not enter 0, do not enter 999999, and do not leave it blank when the form requires a value. Applicant tracking systems frequently sort, filter, and flag candidates on that field, so a placeholder can remove you before a person ever opens your resume. This is career coaching, not legal or HR advice.

What does desired salary mean on an application?

Desired salary is the annual base pay you are asking for in the new role, before bonus, equity, overtime, and benefits, unless the form specifically says otherwise. If the job is paid hourly, enter an hourly rate. It is not your current salary, and it is not a binding commitment you can never revise. But employers do use it to sort candidates against a budgeted band, which is why a guess costs more here than it does almost anywhere else in the process.

The field also shows up under other names. Desired compensation, salary requirements, expected salary, and compensation expectations all mean roughly the same thing, with one useful distinction: anything that says compensation rather than salary is inviting you to describe the whole package, so answer with base pay first and then say you are flexible on structure.

The three versions of the field, and what to enter in each

Application forms are not consistent, and the right answer depends entirely on what the box will physically accept.

Why 0 and 999999 are worse advice than they look

You will see both suggested constantly: enter 0 so the field passes validation, or enter an absurd number so a human has to call you. Both assume a human reads the field. Frequently one does not, at least not first.

Most mid-size and large US employers run inbound applications through software that reads every resume and application, scores it against the criteria the hiring team set, and hands recruiters a ranked shortlist. The software that reads and ranks every inbound application works from structured fields exactly like this one, because a numeric field is trivially easy to filter on compared with the free text of a resume. A 0 can be read as an incomplete application. A 999999 can be read as out of band. Neither gets a phone call, and neither generates a rejection you would ever see, so you never learn it happened.

The safer play is boring: put in a real number you are comfortable with, and treat the conversation with the recruiter as the place where the negotiation actually starts.

How to build the number before you type it

The number should come from the market for the role, not from your current pay plus a raise. Anchoring to what you already earn is how people carry a low salary from job to job for a decade, and it is exactly the pattern that salary history bans were written to break. Twenty US jurisdictions now bar employers from asking what you currently make, which tells you how seriously regulators took the problem.

Start with the posting itself. In California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Washington, and Washington DC, covered employers must publish a good faith pay range in the job posting, and Maine joined that list on July 29, 2026. Connecticut, Nevada, and Rhode Island require the range on request or after an interview rather than in the posting. If a range is published, you are not inventing a figure at all, you are deciding where in someone else's band your experience places you.

Where no range is published, pull several sources for the same title, level, and metro area, and look for the band they agree on rather than the highest number any one of them reports. Then set two figures: the target you would be pleased with, and the floor you would genuinely accept. The floor is what goes in the box, because that is the number you will be offered.

Is it OK to put "negotiable" for desired salary?

Yes, at the application stage, if the field takes text. Recruiters see it constantly and it does not read as difficult. What it does not do is buy you unlimited time. If you are still saying negotiable in the second conversation, the question stops sounding flexible and starts sounding evasive, and the recruiter has to guess your range anyway. Use it to get past the form, then come to the screening call with an actual range and a reason for it.

One caveat worth knowing: some systems require a numeric value and will not accept the word at all, and some recruiters filter for applications where the field was completed. If the form takes text but you are applying somewhere highly structured, a number inside your researched band is the lower-risk answer.

Should you give a range or a single number?

On a form, a single number is usually cleaner, because a range in a text field is often parsed badly or read only at its bottom end. In conversation, a range is better, because it keeps the discussion open and invites the recruiter to tell you their band.

Either way, one rule holds: you will be offered the bottom of whatever you name. Build the range so its floor is a number you would sign for. If a range of 120,000 to 140,000 dollars would leave you disappointed at 120,000, the correct range was 130,000 to 150,000.

What should I put with no experience?

New graduates and career changers get hit hardest by this field, because they have no prior salary to reason from and the most to lose from a low anchor. Use published starting salary data for the field rather than a guess. The National Association of Colleges and Employers put the average projected starting salary for the class of 2025 at 68,680 dollars for all bachelor's degrees, with engineering at 78,731 dollars and computer science at 76,251 dollars, so the spread by major is wide enough that a generic entry level number will mislead you.

The fear that asking will cost you the offer is mostly unfounded. In Fidelity's 2022 study, 85 percent of people who negotiated received at least part of what they asked for, rising to 87 percent among people aged 25 to 35, while 58 percent of young professionals accepted the first offer without countering at all. The people leaving money behind are the ones who never asked.

Can you change your desired salary later?

Yes, and it happens routinely. The number on an application is an expectation given before you know the level, the bonus target, the equity, or the scope, and any reasonable recruiter understands that. What makes a revision easy is flagging it early: say in the first conversation that your figure was based on the posting and that you would want to revisit it once the level and total package are settled. That one sentence turns a later adjustment into something you predicted rather than something you sprung.

What damages you is revising upward with nothing new to point to. If the role turned out to be a level higher than advertised, or the on call load is heavier than described, or the bonus is discretionary rather than targeted, say so specifically. A revision attached to a fact holds. A revision attached to a change of heart does not.

Hourly, annual, or gross?

Match the form. If the posting quotes an hourly rate, answer hourly. If it quotes a salary, answer annual, and answer in gross pay before tax unless the field says otherwise. When you are converting between the two, remember that 2,080 hours is the standard full time year, so an hourly rate multiplied by 2,080 gives you the annual equivalent before overtime. Mixing the two units is the most common way people accidentally submit a number that is off by an order of magnitude.

The short version

Research first, then answer. Put "negotiable" if the field takes text and you would rather have the conversation live. Put the floor of a researched range if it takes a number. Never put a placeholder. And treat whatever you enter as an anchor rather than a formality, because the person on the other side certainly will.

If you want the band built for you rather than assembled from a dozen browser tabs, that is what Counteroffer does: it benchmarks the title, level, and metro area, sets the figure to lead with, and writes the sentence for each place the question shows up. Read the full guide to answering desired salary and salary expectations for the state by state table of where the range is already published, or see how to negotiate the job offer once the written offer arrives. If the number that comes back is well under your band, here is how to respond to a lowball salary offer without burning the relationship. Graduating soon? The new grad salary negotiation guide covers the starting salary data by major.