What to put in the desired-salary field so you don't negotiate against yourself
A blank or evasive answer often fails form validation, and a single low number becomes your ceiling later. Here's how to fill this field so it clears the form without quietly setting your own pay cap.
The desired-salary field causes more anxiety than almost any other part of an application form, for a reasonable reason: whatever you type there tends to stick. Recruiters anchor to the first number a candidate gives, and a number that's lower than what the role actually pays rarely gets corrected upward later — it gets treated as confirmation that the low end of the band was acceptable to you all along.
Why "negotiable" often isn't a real option
Plenty of advice says to write "negotiable" or "open" instead of a number. This works on a human-reviewed application. It frequently does not work on an ATS form, because a real share of these fields are built with numeric validation — a required field that expects a number, sometimes even a range with min and max inputs rather than free text. Typing "negotiable" into a field like that either throws a validation error that blocks submission, or gets silently stripped and stored as zero or blank, which can read worse than an honest number would have. Check what the field actually accepts before deciding your strategy for it: a free-text box behaves differently than a required numeric field, and the right move differs between them.
What to put, field by field
Free-text field, no validation: "Negotiable, targeting the range typical for this role and level" is fine here, and costs you nothing.
Required numeric field, single value: give your real target, not your floor. The number you write is read as your expectation, not your minimum — so writing your absolute floor "to be safe" just moves your expectation down, it doesn't protect you. Base this number on researched market data for the role, level, and location (not your current salary, which the field usually isn't asking for and which anchors you to a past negotiation, not this one).
Required numeric field, range (min/max): set the minimum at the bottom of what you'd genuinely accept for this specific role, and the maximum at the top of what's realistic for the level and market — not an aspirational ceiling with no relationship to the role. A range that's unrealistically wide (say, $80k–$200k for the same title) reads as not having done the research, which undercuts you more than a tight, well-researched range would.
"Current salary" field, asked separately: several US states and a growing number of other jurisdictions restrict employers from asking this at all, and many ATS forms have simply removed the field to stay compliant — if it's still there, decline to answer where the form allows it ("Prefer not to disclose" is usually a valid option precisely because of that regulatory shift), and if it's a required field with no opt-out, that's worth noting as a real signal about how the company treats compensation transparency generally.
The number to actually have ready before you apply
Whatever the field format, the number quality that matters is the research behind it, not the phrasing. Pull current comparable ranges for the specific title, level, and location — not a national average, which flattens out real regional and seniority variance — before you're filling out any form, so you're not improvising a number under time pressure on the fifth application of the evening. A number you can defend if a recruiter asks "how did you land on that" is a stronger anchor than a round figure picked because it felt safe.
Once you've settled on that number, the value of storing it once and reusing it consistently is real: a target range applied the same way to every posting's salary field, matched to whatever format that specific employer's form expects, beats reinventing an answer under pressure on each one.