The application wants a number before it shows you the upload button. The September jobs report showed average hourly earnings up just 3.0% year over year, the slowest since May 2021, and Indeed's posted-pay tracker is running even cooler at 2.5%. Employers' budgets slowed down, and most job seekers' habits didn't. That gap is where a form field rejects you.
What should you put for desired salary on a job application right now?
Type a single number that sits inside the posted range, closer to the top if your fit is strong, and never above the posted maximum. If there is no range, start from your current pay and add what the market actually moved (about 2.5% on Indeed's posted-wage tracker), not the reflexive 10%.
Why the September jobs report changes the number
The report confirmed that pay is no longer rising fast enough to justify a big automatic bump in your ask. Payrolls rose 29,000 against the 84,000 economists surveyed by Dow Jones expected, and unemployment ticked up to 4.2%.
The wage line is the one that matters for the salary box:
- Average hourly earnings rose 0.1% in September, putting the 12-month gain at 3.0%, the lowest since May 2021 (CNBC, SHRM).
- It was the sixth straight month of wages tracking below inflation (NBC News).
- Heather Long of Navy Federal put it bluntly: "Wage growth fell to a new 5-year low and is being wiped out entirely by inflation."
The slowest pace since May 2021, and the sixth straight month below inflation.
Here is the mechanism. Indeed's tracker shows posted wages up 2.5% over the year ending August 2026, so the bands you're applying into are moving slowly. Your expectation, meanwhile, is usually built from your own last raise, a friend's offer, or a salary guide written for a different market. The salary field is where those two numbers meet, and the employer's number wins.
How the desired salary ATS knockout question actually works
A knockout question is an application question whose answer can automatically advance, hold, or reject a candidate based on a rule a recruiter sets in advance. In Workday, Greenhouse and Lever, your answer to "desired salary" or "expected compensation" is saved as structured data, which means it can be compared against a threshold without anyone opening your resume.
How common is that kind of automation? Greenhouse's 2025 AI in Hiring Report found:
- 53% of U.S. recruiters have handed most screening to AI or ATS systems.
- Only 21% of U.S. recruiters said they were very confident their systems were not rejecting qualified candidates.
Read those two numbers together. More than half of recruiters have handed most screening to software, and roughly four out of five aren't very confident it's getting things right. A salary rule is the easiest one to set ("reject if expected salary exceeds band max") and the hardest to audit, because rarely does anyone go back through the rejected pile to check whether a strong candidate typed $8,000 too much.
So treat the expected salary field on an application as a filter question first and a negotiation opener a distant second. Negotiation happens with a human. The field decides whether you ever meet one.
Why "last salary plus 10%" gets you knocked out
"Last salary plus 10%" fails because the band moved about 2.5% while your ask moved 10%, and the rule only compares the two. With bands rising that slowly, a 10% bump is far more likely to land above the posted maximum than inside the range.
The band moved 2.5%. Your ask moved 10%. The rule only compares the two.
Pay transparency laws make this worse, not better. In states that require ranges, the posted maximum isn't a soft opening position. California, since January 2026, defines a posted range as "a good faith estimate of the salary or hourly range that the employer reasonably expects to pay for the position upon hire." When the employer has formally stated what it expects to pay, a number above the top reads as "outside budget," and a rule can act on that without guilt.
The map of where that applies keeps growing:
- Connecticut's Public Act 26-12 took effect October 1, 2026.
- Virginia and Maine began requiring ranges in July 2026.
- Boostpoint's tracker counts 13 states plus DC with posting requirements. Other trackers count more, possibly because they include states where ranges are only available on request.
If the posting shows a range, you aren't guessing anymore. Use it.
Your wage tier decides how much room you have
High-wage roles have some room above the midpoint this fall. Middle-wage roles have almost none. Indeed Hiring Lab's September snapshot shows posted pay in traditionally higher-paying occupations accelerating from a 2.0% annual rate in January to 2.6% in August, while low- and middle-wage occupations moved sideways.
That split is recent. In May, Indeed reported low-wage jobs once again seeing faster posted-wage growth (2.7%) than higher-paying ones, so a salary guide from early 2026 may point you the wrong way. The posting in front of you doesn't lag.
Now layer on how many candidates each recruiter has to get through. In Refolk's index of professional profiles (US, pulled October 2026), I mapped two large occupations onto Indeed's tiers as an illustration (not an official classification):
| Group | US profiles | Per recruiter |
|---|---|---|
| Software Engineer (high-wage tier) | 353,826 | 3.6 |
| Administrative Assistant (middle-wage tier) | 528,606 | 5.4 |
| Recruiter / Talent Acquisition | 97,319 | baseline |
| SWE + Admin Assistant combined | 882,432 | about 9.1 |
Administrative assistants outnumber software engineers 1.49x in the index, and each recruiter faces roughly 5.4 of them against 3.6 engineers.
Versus 3.6 software engineers per recruiter, in a tier where posted pay has gone flat.
That combination is the non-obvious part. The middle tier has the flattest budgets and the most candidates per recruiter, which is exactly the setup where a rule does the first read. An engineer applying to Google, Figma or Microsoft (common employers in the index's software engineer sample) who types a number slightly above band may still get a human look, because that band is rising and the pool per recruiter is thinner. An operations coordinator or executive assistant who does the same is more likely to be filtered silently.
Practical translation:
- High-wage tier (engineering, senior data, senior product): aim in the upper part of the posted range when your fit is strong. Don't go over the max.
- Middle-wage tier (admin, coordinator, many operations and support roles): aim at or slightly above the midpoint. The ceiling isn't moving, and you need the first read more than you need the last $2,000.
How strong is "strong fit"? Guessing is how people over- or under-ask. Refolk scores how well your actual history matches each posting, which tells you whether you're a candidate who can defend the top of the band or one who should sit near the middle and win on the interview.
Hourly and contract applicants are the most exposed
Hourly workers and contractors are the likeliest to type a number above band, because hourly posted pay is growing far slower than salaried pay. Indeed found posted wages for salaried roles grew 2.9% between the first quarters of 2025 and 2026, while hourly roles grew only 1.7%. Hourly postings in software, data and marketing showed negative wage growth.
| Pay type | Posted wage growth, Q1 2025 to Q1 2026 |
|---|---|
| Salaried roles | 2.9% |
| Hourly roles (all) | 1.7% |
| Hourly software, data, marketing | Negative |
If you're a contractor quoting last year's rate into an "expected hourly rate" field, you may be asking more than a band that actually went down. Before you apply:
- Pull up the posted hourly range and treat its max as a hard ceiling.
- If your old rate is above that max, decide before applying whether you'd take the top of the band. If yes, type the top. If no, skip the posting.
- Don't convert a salaried number into hourly (or the reverse) in your head. Use the unit the field asks for, or a rule may compare $95 against $95,000 and do something strange.
Should you type 0, 999, or "negotiable"?
No. Placeholder answers are a gamble on a filter that even its owners don't trust, and you can't see which way it breaks. The advice out there contradicts itself:
- An iHire career advisor suggests typing "000" or "999" when the field requires a number.
- Jobstrack warns that some applicant tracking systems reject the submission outright when "negotiable" goes into a numbers-only field.
Think about what each placeholder does to a rule. "999" can parse as $999, which is under any minimum and may flag you as a data error or a mismatch. "0" can trip a "missing required answer" rule. "999999" sits above every maximum. With only 21% of recruiters very confident in their filters, you have no reason to believe anyone will notice your clever answer and rescue it from the reject pile.
Give a real number. It's the only answer whose behavior you can predict.
The one exception is a free-text box, where a human is probably reading. There, a range anchored to the posting plus a short qualifier works: "$118,000 to $126,000, depending on total compensation."
What to type, field by field
Match your answer to the type of field and whether a range is posted. Here is the playbook for how to answer salary expectations on an online application:
| Field you see | Range posted? | What to type |
|---|---|---|
| Single number, required | Yes | One number inside the range: upper part if high-wage tier and strong fit, near midpoint if middle tier |
| Single number, required | No | Current base plus about 2.5% (Indeed's posted-wage growth), rounded |
| Min and max fields | Yes | Your floor as min, the posted max (or just under) as max |
| Hourly rate | Yes | At or below the posted hourly max, even if last year's rate was higher |
| Free text | Either | A tight range plus one qualifier about total compensation |
A few rules that hold across all of them:
- Base salary only, unless the field says otherwise. Don't add bonus or equity into a base field. A rule comparing your $150,000 "total" against a $135,000 base max will reject you.
- Round numbers. $120,000 reads as a considered anchor. $123,450 looks like a typo to a human and still parses fine for a machine, so there's no upside.
- Be consistent. If you apply to two roles at the same employer, use the same logic for both. Two very different numbers at one company look like guessing.
- Re-check the posting date. A range from a posting that's been up since spring may reflect a budget set before the latest wage data.
The salary number is only one of the answers an ATS can act on before a human gets involved, and the resume itself gets screened against the posting too. Getting the resume to match each posting is the work Refolk takes off you: paste the posting, and you get your own resume back, rewritten for it, with a fit score that tells you how hard you can lean on the salary number.
FAQ
What should I put for desired salary if the job posting shows no range?
Start with your current base salary and add roughly what posted pay actually grew, about 2.5% on Indeed Hiring Lab's tracker, then round. If you're in a high-wage occupation where posted pay accelerated to 2.6% by August, you can lean slightly higher. If you're in a middle-wage occupation where pay has gone flat, stay close to your current number and negotiate after the first interview.
Is it better to ask too low than too high in the expected salary field?
Slightly low is safer than high at the screening stage, because a number above the band is the condition most likely to trigger a desired salary ATS knockout rule. A number well below the band carries its own risk, since a recruiter can read it as a seniority mismatch. The safest zone is inside the posted range, which is also the number you can most easily negotiate up from once a human is involved.
Do pay transparency laws mean I should always ask for the top of the range?
No. In states like California, the posted range is the employer's good-faith estimate of what it expects to pay, so the top is generally reserved for candidates who match the role closely. Ask for the top only when your history clearly covers the whole posting. Otherwise aim nearer the midpoint, get through the filter, and make the case for more money in conversation, where a human can weigh it.