Most application forms hide one field that quietly decides whether a human ever reads your CV. It is the salary expectations field, and it behaves nothing like the same question asked in an interview. On a form there is no room to explain yourself, no tone of voice, and often a filter sitting behind the box.
Why the salary expectations form field is a filter, not a conversation
Applicant tracking systems treat that box as structured data whenever they can. Recruiters set a knockout threshold in the job requisition, and any application above it gets auto-tagged, pushed to a lower pile, or rejected outright before a screener opens it. Some systems match your number against a published pay band and score how well you fit inside it.
Others do something simpler and more damaging: they sort candidates by the number ascending, so a recruiter working through 300 applications sees the cheapest people first. That sort order is why a blank or unparseable answer is risky. If the system cannot read an integer, you often get treated as a null value and land at the bottom of the list or outside the filter entirely.
This is also why the common advice to always write "negotiable" is bad advice on a form. It works fine in conversation. Typed into a field that feeds a filter, it tells the system nothing and tells the recruiter you did not do your research.
The mechanics change your answer
The field comes in five shapes, and each one has a different correct play. Read the box before you write anything.
- Free text, optional. You have the most freedom here. A researched range with a currency and a period, plus one clause of context, works well.
- Free text, required. Still write a range, but lead with numbers so any parser finds them. "55,000 to 62,000 EUR gross per year" beats "negotiable depending on the full package".
- Single number, required. Give one figure near the lower-middle of your range, not your floor. You will be anchored to it, so pick something you would sign for without resentment.
- Min and max fields. The gift. Set your minimum at the lowest figure you would genuinely accept and your maximum roughly 15 to 20 percent above it.
- Dropdown of bands. Pick the band whose bottom edge you would accept. Never pick the band above your target hoping to negotiate down, because band matching is usually binary.
If the field looks like X, type Y
- Optional free text and you have no market data yet: leave it blank and research before you submit anything else.
- Required free text: a range in gross annual terms, currency named, nothing else.
- Required integer with no decimals and no text allowed: the number you would accept, not the number you want.
- Dropdown with a band that straddles your target: choose the lower band if your target sits in its top third.
- Field asks for current salary rather than expectations: in jurisdictions where that question is banned, enter your expected figure or a zero if the form forces it, then correct it in the first call.
Why a range beats a single number, and how wide to make it
A single figure gets read as a ceiling by employers and a floor by nobody. It also removes the useful ambiguity that lets a recruiter advocate for you internally. A range signals that you understand the role has a band and that you know roughly where it sits.
Keep the range tight. Anything wider than about 20 percent reads as guesswork, and the recruiter will assume you would take the bottom. A 55,000 to 65,000 EUR range is credible. A 45,000 to 80,000 EUR range says you have no idea what the job pays, which is a worse signal than a slightly high number.
The floor of your range is the only number that matters, because that is the number you will be offered.
Anchor the number before you type it
Do the research first, even if it costs you twenty minutes. Pull the posted band if pay transparency rules apply, check two or three salary aggregators for the same title in the same city, and look at what comparable roles at the same company size advertise. Then adjust for your years of experience and the specific stack or sector.
Watch the unit traps, because they cause more damage than being slightly off on market rate. Confirm whether the form wants gross or net, annual or monthly, and whether bonus is included. In Spain, monthly salaries are frequently quoted across 14 payments rather than 12, so a 3,000 EUR monthly figure can mean 42,000 or 36,000 depending on the convention. In France you will see 13th month arrangements bundled into the annual gross. Always state the unit yourself if the field lets you.
The low-number trap
Going deliberately low to survive the filter is the mistake I see most often, and it backfires in a way candidates never find out about. A number well under the band does not read as flexible. It reads as junior, or as someone who has misread the seniority of the role, and screeners drop those applications to protect the hiring manager's time.
Pay transparency laws in the EU, several US states, and increasingly elsewhere mean the employer often has to publish a band before you apply. When a band is published, your job is simple: place your range inside it, ideally in the upper half if your experience justifies it. If no band is published and the field is required, that is your signal to be precise rather than vague.
One practical habit: keep your researched range, currency, and unit saved alongside your CV so you are not re-deciding under time pressure on every form. If you are managing a lot of applications, a tool like Postulit that keeps your application data in one place makes this less of a memory exercise.
What to do on your next form
Before your next application, write down three numbers: the floor you would genuinely accept, your target, and the ceiling of the posted band if there is one. Then answer the field mechanically according to its shape, using gross annual figures with the currency spelled out. The salary interview question and the cover letter version are separate problems with separate answers, and neither one gets you past a filter that reads integers.