Salary Expectations on Resume or Cover Letter (2026)

The result is a strategy gap. Applicants are still pretending they’re playing a game where the employer has all the salary information and the candidate has none — when in many states it’s the opposite. Some applicants now lowball themselves below a posted range. Others enter “99999” into a salary field that screens against a hard cap, and never reach a human. Others volunteer salary history in states where employers can’t legally ask for it. The frame this guide uses: a four-quadrant decision matrix based on what the posting shows, what the form demands, and where you’re applying from.

Below: the data on what’s actually changed, the legal split between salary history and salary expectations, the four-quadrant matrix for where to put a number (or not), three cover-letter scripts that work in 2026, four scenarios for the dreaded “desired salary” application field, and the six mistakes that quietly cost candidates the most.

Two different waves of legislation reshape this conversation. One wave forces employers to publish a salary range. The other wave forbids employers from asking about a candidate’s prior pay. They’re often confused with each other, but they cover different ground and create different obligations. Here’s the rough lay of the land in 2026 — verify your specific state before applying because rules shift quickly.

Counts compiled from public compliance trackers (Paycor, Hunton, Jackson Lewis, HR Dive, GovDocs). State-by-state details and effective dates change frequently \u2014 check the specific statute for the state you\u2019re applying in before relying on this map.

Most applicants treat these as the same thing. They’re not. One is about your past. The other is about your future. The legal treatment is different in many states, and the negotiation consequences are different too. The cleanest mental model: history anchors you to what you used to earn; expectations anchor you to what the role you want is worth. Volunteering history in a state that bans the employer from asking gives away a protection the law tried to give you.

The single most useful frame: cross two questions. Does the job posting show a salary range? And does the application form demand a number to advance? Four cells, four postures. Find your cell and use the script in it.

When a posting explicitly requires salary requirements in the cover letter, three phrasings outperform the alternatives. The pattern: a researched range, a flexibility caveat, and a redirect to the full package. Avoid single-number anchors and avoid prior-salary references — the first traps you, the second telegraphs that you didn’t do market research.

The application form is where most candidates trip. Recruiter folklore from a few years ago — “type 99999, the system understands” — assumed a human reads every entry. That isn’t a safe assumption today. Many ATS platforms route or screen applications based on the salary number itself, which means “99999” can fail an employer’s salary filter the same way any number above the role’s posted range would. The right move depends entirely on what the form will accept.

The mistake isn’t naming a number. The mistake is naming a number that has no anchor — to the posted range, to the market, or to the role itself.

The frame to carry into every application: the salary field stopped being a trap somewhere around 2023 and became a context-dependent decision. The four-quadrant matrix tells you which posture to take. The salary-history-vs-expectations split tells you which question you’re actually being asked. The cover-letter scripts and field scenarios give you the language. The mistakes list tells you what most candidates still get wrong. Use the right tool for the cell you’re in, and the question stops being scary.