You're halfway through an application and hit a required box: "Desired salary." Indeed Hiring Lab's October 22, 2026 snapshot says posted wages grew 2.4% year over year in September, while CPI inflation ran at 3.7%. So the obvious move, taking your last salary and adding inflation, now puts plenty of candidates above what employers are advertising. In a couple of fields it leaves money on the table instead.
What should you put for desired salary on a job application?
Put a specific number in the top half of the posting's pay range, and adjust it for how pay is moving in your field. Don't start from your last salary plus inflation. Your desired salary is the figure the application software compares against the budgeted band for the role, so the number should come from the employer's budget, not from your grocery bill.
That gives you three cases:
- The posting lists a range and your field is hot (electrical engineering, IT systems): ask near the top of the range.
- The posting lists a range and your field is flat: aim between the midpoint and the upper quarter.
- No range is posted: build one from market data for the title, then apply the same logic.
Why "last salary plus inflation" misprices you
Last salary plus inflation is wrong because inflation tracks your costs, not what the employer has budgeted. What matters is how posted pay is moving in your field, and right now that number is above CPI in a few fields and below it across the market overall.
Take someone earning $100,000 and run the three formulas:
| Formula | Rate | Resulting ask | vs. CPI-based ask |
|---|---|---|---|
| Last salary + CPI | +3.7% | $103,700 | baseline |
| Last salary + overall posted trend | +2.4% | $102,400 | $1,300 lower |
| Last salary + electrical engineering trend | +5.6% | $105,600 | $1,900 higher |
The CPI number feels fair because your rent went up. But the employer's band tracks the posted market, and across the market that moved 2.4%, not 3.7%. For a generalist, the CPI formula lands above where posted pay has gone. For an electrical engineer it lands $1,900 under it.
The squeeze on workers is real. Hiring Lab's same snapshot says inflation-adjusted average weekly earnings fell 0.5% from August to September, which put take-home pay 0.1% below a year earlier. That's a good reason to negotiate hard once you have an offer. It doesn't tell you what to type into a field that software scores against a band.
Your field's pay trend matters more than CPI
How pay is moving in your field is the strongest signal you have, because posted pay growth is splitting by field and by wage level. Hiring Lab reports advertised wages in electrical engineering up 5.6% and IT systems and solutions up 4.7%, against 2.4% for all postings.
The split goes beyond those two fields. In Hiring Lab's September snapshot, wage growth in higher-paying occupations sped up from a 2.0% annual rate in January to 2.6% in August, while low- and middle-wage occupations moved sideways. Mechanical, civil and electrical engineering hold three of the top five sectors on Hiring Lab's job postings index (JPI).
Here's what that looks like next to the people who actually write salary bands. Counts come from Refolk's index of professional profiles (US, title match). Growth rates come from Indeed Hiring Lab, October 22, 2026. "Real" means posted wage growth minus 3.7% CPI.
| Group | US profiles (Refolk index) | Posted wage growth, yr/yr | Real posted growth |
|---|---|---|---|
| Electrical Engineer | 40,477 | +5.6% | +1.9 pts |
| Systems Engineer / Sysadmin | 46,635 | +4.7% (IT systems) | +1.0 pt |
| All posted wages | n/a | +2.4% | -1.3 pts |
| Compensation / Total Rewards pros | 5,149 | n/a | n/a |
One caveat: the Systems Engineer title match includes aerospace and defense systems engineers, not only IT.
Why bands lag in hot fields
In Refolk's index, only about 5,149 US profiles hold compensation titles (Compensation Analyst, Compensation Manager or Partner, Total Rewards Manager). That's roughly 7.9 electrical engineers and 9.1 systems engineers or sysadmins for every compensation professional, and that's counting just two fields. Sampled employers with compensation staff include Meta, Figma, Okta, Citizens and Hospital for Special Surgery.
A team that small, covering every job family, can't rewrite bands as fast as a field moves. When a field's posted pay rises 5.6% in a year, a band written before that rise is already behind. So in electrical engineering and IT systems, a number at the top of the posted range isn't greedy. It's the market catching up with a stale document.
40,477 Electrical Engineer profiles against 5,149 compensation and total rewards profiles.
Why candidates' asks are drifting above posted bands
What candidates ask for is rising faster than what employers post. The New York Fed's Survey of Consumer Expectations (SCE) Labor Market Survey, published every four months by its Center for Microeconomic Data, puts the average reservation wage at a series high of $88,387 in July. The reservation wage is the lowest pay a person says they would accept for a new job.
That figure has climbed more than $10,000 since March 2025. In March 2024 it was $81,822, so the rise since then is roughly 8%. Posted pay has been growing about 2.4% to 2.5% a year. The two series measure different things (one is a survey of what people would accept, the other is advertised wages), so treat the gap as a direction, not an exact number.
A series high in the New York Fed's July SCE Labor Market Survey, up more than $10,000 since March 2025.
The direction is what matters. If you anchor on your own floor, and your floor is rising faster than employers' bands, your number drifts above the range without you noticing. The New York Fed says the increase was most pronounced for men, college graduates and people under 45.
How ATS software reads the salary expectations field
Most applicant tracking systems (ATS) don't automatically reject you for your salary number. They score it, and an answer outside the band ranks you lower. An ATS is the software employers use to collect, filter and rank applications. Platforms like Workday and Greenhouse are where recruiters set up salary prescreening questions, as either hard knockouts or scored inputs.
According to one Workday-focused explainer, most salary prescreening questions aren't set up as hard knockout triggers. The answer feeds a scoring rubric that pushes applications outside the band down the list. Where hard knockouts do exist, they tend to sit at the top of the band. In practice:
- Inside the range: scored normally, and your resume does the rest of the work.
- Above the range: deprioritized by the rubric, and pushed further down the further out you go.
- Far above the top: may trip a knockout set at the band ceiling.
- "Negotiable" or a placeholder: gives the rubric nothing to place inside the band. A real number in the top half of the range beats it.
Because salary and resume get scored side by side, the resume half has to hold up too. A top-of-range ask attached to a generic resume reads like a mismatch. That pairing is what Refolk is built for: paste the posting, and I rewrite your own resume for it from your real history, so the document the recruiter opens supports the number you typed.
Recruiters know the filters misfire. In Greenhouse's 2025 research, only 21% of US recruiters said they were very confident their systems weren't rejecting qualified candidates. Nobody tells you your number cost you a spot. Your application just sinks down a ranked list, and what you experience is silence. You hear nothing back and blame your resume when the real cause was one field.
Salary expectations vs posted pay range: is the range real now?
Yes, posted ranges are closer to real hiring budgets than they used to be, so a number inside the range is the default answer, not a lowball. Pay transparency laws are the reason.
What's changed:
- California (SB 642) now defines the pay scale as a "good faith estimate of the salary or hourly range that the employer reasonably expects to pay for the position upon hire." "Upon hire" is the key phrase. It ties the range to what the employer expects to pay on day one.
- About 14 states plus DC have statewide pay transparency laws (trackers count slightly differently), and most of them require the range in the posting itself.
- Virginia's posting law took effect July 1, 2026. Connecticut joined on October 1, 2026.
The effect: when a posting from a covered state says $95,000 to $125,000, the employer is stating, with legal exposure, that it expects to hire somewhere in that window. Typing $140,000 doesn't signal confidence. It tells the scoring rubric you're outside the budget. Typing $96,000 tells the employer you'll take the bottom, and they'll remember that at offer time.
Inside the posted range is the default answer. The top half is where you start.
How to pick the number: a five-step method
Pick a single number in the top half of the posted range, and push it toward the ceiling when your field is hot and your fit is strong. Here's the sequence:
- Find the range. Use the posting first. If there isn't one, check whether the same employer posts the role in a pay-transparency state, then fall back to market data. For example, Indeed's average posted Electrical Engineer salary is $111,522, with a low of $71,943 and a high of $172,874.
- Check your field's pay trend. If posted pay in your field is beating CPI (electrical engineering at +5.6%, IT systems at +4.7%), move toward the top. If your field tracks the overall 2.4%, stay between the midpoint and the upper quarter.
- Score your fit honestly. A top-of-range ask needs a resume that clearly meets the must-haves. Refolk scores how well you actually fit each posting. A strong score backs up a number near the ceiling. A middling one says aim at the midpoint and let the interview earn the rest.
- Type one number, not a range. A range just hands the employer your floor.
- Leave it out of the cover letter. The number belongs in the field. The letter should be about why you want this role. Repeating a figure there only gives the employer a second anchor.
Last salary plus inflation appears nowhere in those steps. Your history shapes your leverage in negotiation, not your answer to a scored form field.
FAQ
Should I put my salary expectations on an application if the field is optional?
If the posting lists a range, fill it in with a number in the top half. Inside the band, it gives the rubric something to score in your favor. If no range is posted and you can't find solid market data for the title, leaving an optional field blank is reasonable. Bring it up at the recruiter screen, where you'll learn the band before you name a number.
Is it okay to write "negotiable" in the desired salary field?
In a required field, no. The answer feeds a scoring rubric, and "negotiable" gives it nothing to place inside the band. A specific number in the top half of the range beats "negotiable" and beats an outlier, and it doesn't stop you negotiating later.
What if my last salary was above the posted range?
Then the honest choice is whether you want this role at this band. If you do, enter the top of the posted range rather than your old salary. Hard knockouts tend to sit at the band ceiling, so a number well above it risks one, while the ceiling keeps you in the ranked pool and leaves room to negotiate on level, title or equity after an offer.
Does the number I type lock me in?
No, but it anchors the conversation. That's why a low number is the costlier mistake: it's very hard to talk an employer up from a figure you volunteered, but easy to justify the top of a range they published themselves.