What to type in the desired salary box
The desired salary box asks you to commit to a number before the employer has committed to one of their own, which is exactly why it feels harder than every other field on the form. Most of the time it is optional, and knowing that changes how you should approach it.
Required and optional are genuinely different categories
Across a measurement of 20 real job listings at 7 companies, application fields split cleanly into fields that are required, fields that are optional, and fields that simply do not appear at all on a given form. That split is not cosmetic. A required field blocks submission until you fill it in. An optional one does not, and treating the two the same, filling in an optional field out of habit or a vague sense that you should, gives up a choice you actually have.
Desired salary is typically one of the fields that falls on the optional side of that line. When it is optional, you get to decide whether answering it early works in your favor, rather than being forced into a number before you have any real information to base it on.
Why a number this early can work against you
Whatever you type in that box becomes an anchor for the rest of the process, whether or not that was your intention. A number on the low side can cap what gets offered later, even if your actual value turns out to be higher once the employer has met you. A number on the high side can knock you out of consideration before anyone has had the chance to see the rest of your application, especially if an automated screen is filtering on that field before a human ever looks at your resume.
Both outcomes come from the same root problem: you are being asked to price yourself against a role you do not yet fully understand, at a company whose actual budget you do not yet know. That is a worse position to negotiate from than the one you will be in later, once there has been an actual conversation about the role, its scope, and what it is worth.
What to do when the field is optional
Leaving it blank is a completely reasonable choice when the field allows it, and it costs you nothing. It defers the number to a point in the process where you will have more information and, usually, more leverage: a live conversation with a recruiter, rather than a text box on a form nobody is going to negotiate with you through. Asking a recruiter for the range, early is a much better venue for this conversation than a form field, because it is a two way exchange rather than a one way commitment.
If you would rather not leave it blank, a wide range grounded in real research is safer than a single figure, since it signals a number without pinning you to the bottom of it before any real conversation has happened.
What to do when the field is required
Some forms will not let you submit without answering, which is where the earlier framework becomes useful again: the same field by field measurement that established which parts of an application are truly required is the reason it is worth checking, rather than assuming, whether this particular field is one of them. Which application fields you can safely skip covers how to tell required from optional in general, and the same logic applies here.
When you have no way around answering, a wide, well researched range is the better move over a single number, for the same anchoring reason described above. Research the role's likely band using level, location, and company stage before you type anything in, rather than guessing at a figure with no basis behind it.
Why an automated system might be reading it first
On larger applications, a number typed into this field does not always reach a human first. Applicant tracking systems can be configured to flag or filter submissions based on fields like this one, comparing what you entered against a range the employer set internally before your application ever reaches a recruiter's queue. You will not be told this is happening, and you will not know where the internal cutoffs sit.
This is a further reason a specific number carries more risk than it might seem to on the surface. A figure that is perfectly reasonable in a live conversation, where a recruiter can ask a follow up question or explain what flexibility exists, can trigger an automatic filter with no such nuance available to it. A wide range, or no answer at all where the form allows it, avoids handing an automated step a number it might use in a way you never intended.
One more reason to keep it consistent
Whatever figure you do decide to give, whether in this field, to a recruiter, or later in the process, keep it consistent across all of them. A number that shifts between the application, the recruiter call, and the offer conversation raises questions about which one was real, even when the shift has a perfectly reasonable explanation behind it, like new information about the role's scope. Deciding on your range once, before you start filling out forms, and holding to it until you have a real reason to move, avoids that problem entirely.
The field is an early move in a longer negotiation
However you handle this box, it is worth remembering it is not the only chance you get to talk about pay, and usually not even the most important one. It sits early in a process that, if it goes well, ends with an actual offer and an actual negotiation, where you will have far more information and far more standing to advocate for a real number. Negotiating an offer without burning the bridge covers that later, higher stakes conversation in full, and a cautious answer here is mostly about not undermining your position before that conversation ever starts. Most listings will not have told you their own range by this point either, since most listings say nothing about pay at all, which is one more reason not to be the first one to commit to a specific figure.
iapplyai.app fills in application fields based on your actual resume and preferences rather than a generic default, so a field like desired salary gets handled deliberately instead of on autopilot.
