What to Put for Salary Expectations on an Application Form

The standard negotiation advice is to avoid naming a number first, because whoever names a number first anchors the conversation, and you'd rather the anchor come from them. That advice is sound for a phone call with a recruiter. It gets applied, by habit, to a text field on an application form asking for your salary expectations, and there it stops being sound advice and starts being a way to lose ground before anyone has spoken to you at all.

A form field isn't a negotiation

Negotiation advice assumes a counterparty who can read context: a person who notices you deflected, who can be talked into moving off a number, who weighs your answer against the rest of the conversation. A required field on an application form has none of that. It's a piece of structured data collected before a human is necessarily involved at all, often compared directly against a budget range that was set before the posting went up. There's no nuance for it to register. There's a value, and a rule about what happens to applications whose value falls outside a range.

That's a different situation than the one the standard advice was built for, and it calls for a different move. Refusing to answer, or answering with something that isn't actually a number, doesn't protect your leverage here. It just interacts badly with a system that was expecting a number.

What actually happens to a non-answer

If the field is a structured numeric input, "negotiable" or a placeholder like "000" often won't submit at all, and you've just added a second pass at the form to your application. If it's free text and you write something evasive, one of two things tends to happen downstream. Some systems store it as-is and a recruiter has to open the application and follow up to get an actual figure before it moves anywhere — which is a real step, taken by a real person, that your answer made necessary instead of skipping. Others parse the field for a number, find none, and record it as zero or null, which doesn't read as "flexible." It reads as missing data, and an application with a missing required field is exactly the kind of thing that gets deprioritized in a queue of hundreds, not because anyone judged your number too high, but because there wasn't one to judge.

Either way, you haven't preserved any leverage. You've spent a step of the process not answering a question you were going to have to answer eventually, and the number you eventually give lands with less goodwill than if you'd opened with it.

Two different jobs the field is doing

It helps to know that this field is usually doing one of two jobs, and often both. The first is a hard filter: does your number fall inside the band the role was budgeted for. If it doesn't, no amount of charm in the rest of your application changes that outcome, and it's genuinely better to find that out from a form than after a screener and a first-round interview. The second job is informational: the number becomes the starting point that later comp conversations get built around, the same way it would if a recruiter asked you directly on a call. Both of these are better served by a real number than by a dodge. The filter can't act on a dodge except by discarding it, and the informational anchor still gets set either way — it just gets set later, with you having contributed nothing to where it lands.

What to put instead

Give a real range, not a single figure and not a placeholder. The top of the range should be a number you'd be genuinely glad to get, not an aspirational reach you'd need a second job offer to justify. The bottom should be a number you'd actually accept without resentment, not a lowball meant to look flexible — a bottom that isn't real is the same evasiveness as "negotiable," just dressed up as a number.

Base the range on something, not a guess. Postings for comparable roles at comparable companies increasingly list a range directly, because pay transparency requirements have made that common in a lot of places — read a handful of those before you fill out the form, for the same role title at companies of similar size and stage. Public compensation data for the role and level, and conversations with people who hold a similar title somewhere similar, round out the picture. None of this needs to be precise to be useful. It needs to be a real range you could defend if a recruiter asked how you got there, instead of a number pulled from what you'd like to be true.

Giving a number now doesn't cost you the negotiation later

The fear underneath all of this is that naming a number early gives away your floor before you have any leverage. That fear is misapplied to a form field, but it isn't crazy in general, and it's worth separating from what the form is actually asking. A range on an application form is a compatibility check, not a binding offer you've made to yourself. It tells the company whether this role and your expectations are in the same neighborhood before either of you has spent real time on the process. The real negotiation — the one where your leverage matters, where you know the full scope of the role and whether you have a competing offer, where the company has decided it wants you specifically — happens later, after an offer, in a live conversation with a person who can respond to what you say. Nothing about answering the form field plainly obligates you to accept a number anywhere in the range you gave. It just gets you to the conversation where the real negotiation happens, instead of getting your application filtered out before that conversation exists.

The version of caution that actually helps

The instinct to be careful with a compensation question is a reasonable one. It's just aimed at the wrong moment. Vagueness on a form doesn't protect you — it either bounces the form back to you or gets treated as a non-answer by a system with no room for nuance. The caution that actually pays off is upstream of the form: doing the research so the range you give is one you'd stand behind, and deciding on it before you're staring at the field, so you're not composing your negotiating position in a text box under time pressure. Decide the range once, in the abstract, and you can paste it into every form after that without relitigating it each time.