Should You Put Salary Expectations on Your Resume? The Honest Answer

Here is the short answer, then the full reasoning: no, do not put salary expectations on your resume by default. Keep pay off the resume itself, and handle it in the application form field, the cover letter, or the recruiter conversation, where it belongs. The one exception is when the employer explicitly asks for salary expectations on the resume. Then include it, but do it as a single researched range on its own line, never as a single fixed figure, and never as your salary history.

Why the resume is the worst place for a number

A resume has one job: prove you can do the work. A salary figure does not prove that. What it does is hand the reader a reason to stop reading. Recruiters manage requisitions with fixed budget bands, and application systems store your compensation answer in a separate field beside your resume. When your number falls outside the band, the file can be filtered, flagged, or deprioritised before anyone weighs your experience. HireFlow's recent analysis of US hiring funnels describes the mechanism plainly: pay screening often happens before skill screening, and an out-of-band answer can act as knockout logic before resume keywords are even scored.

There is a second, subtler cost. The first number in any negotiation pulls everything after it toward itself. Psychologists call this anchoring, and it is not a theory cooked up by career coaches. In a classic 2001 study, Adam Galinsky and Thomas Mussweiler found that first offers were a strong predictor of final settlement prices. A later lab study by Todd Thorsteinson at the University of Idaho, published in the Journal of Applied Social Psychology in 2011, showed just how sticky anchors are: candidates who joked about wanting $100,000 were offered an average of $35,383, versus $32,463 for the control group given only a realistic anchor. Even a joke number moved the outcome.

Now think about what happens when you print a number on your resume. That number becomes the anchor for every conversation that follows, and it is an anchor you set before you know the full scope of the role, the bonus structure, the equity, or the benefits. Name a figure too low and you have negotiated against yourself before the first call. Name one too high and you may never get the call at all. Either way, you gave away leverage for nothing, because the resume was never the place the employer needed that information.

What the data says about pay talk

The fear that keeps people quiet about money is that asking will cost them the offer. The evidence points the other way, at the offer stage at least. A Pew Research Center survey of 5,775 US adults found that only 30% of workers asked for higher pay the last time they were hired, yet 66% of those who did negotiate got what they asked for or more. Resume Genius's 2025 Salary Negotiation and Expectations Survey found a similar pattern from the other side: 55% of American workers accepted their first offer without negotiating at all. The money left on the table is real. A working paper by Harvard's Zoe B. Cullen, Brown's Bobak Pakzad-Hurson, and UCLA Anderson's Ricardo Perez-Truglia, studying nearly 3,900 tech job seekers, found that those who countered their initial offer gained an average of about 12.45% in compensation terms, worth roughly $27,000 a year for that high-paid sample.

None of that means you should blurt out a number early. It means the negotiation matters, and it matters most when you have the most information, which is after an offer, not on page one of your resume. Robert Half's January 2026 research among 500 Australian employers found that 58% anticipated salary expectation mismatches as a hiring barrier for the year. Mismatches kill deals at both ends: candidates walk away from uncompetitive offers, and employers screen out candidates whose expectations sit outside the band. Your job is to avoid becoming a mismatch statistic before anyone has assessed your work.

The law has changed the game, and it helps you

Here is the good news: in a growing share of the US, you no longer have to guess blind. As of mid-2026, fourteen states plus Washington DC require employers to disclose salary ranges in job postings, according to multiple 2026 compliance trackers, with more states, including Virginia and Maine, joining during 2026 and Connecticut moving to proactive disclosure in October 2026. Roughly 60% of postings on Indeed now include salary information, up from just 18% in 2020. When the posting shows a range, that range is the employer's own statement of where its screening will land. Use it.

The other legal shift matters just as much. HR Dive's salary-history-ban tracker, updated in April 2026, counts 22 statewide bans and 24 local bans on asking applicants about prior pay. Salary history and salary expectations are different things, and employers in those jurisdictions can still ask what you expect. But the direction of travel is clear: your next salary is supposed to reflect the market value of the role, not whatever your last employer happened to pay you. Never volunteer your salary history on a resume. In ban states it is information the employer is not entitled to use against you, and everywhere else it is an anchor that only ever pulls you backward.

The UK picture is different and worth knowing if you apply across the Atlantic. There is no UK law yet requiring salary ranges in postings, though the government has been consulting on pay transparency measures, and the EU's pay transparency directive is pushing the same direction for roles in member states. In practice, UK postings still hide pay more often than US ones, which makes the "what are your salary expectations" question even more common in UK applications, and even more worth handling carefully rather than on the resume.

The only three times pay belongs on the resume

1. The employer explicitly asks for it there. Some postings say "submit a resume including salary expectations" or "include salary requirements with your application." If the instruction names the resume, follow it. Ignoring a direct instruction is a worse signal than any number. Keep it to one line, near the end of the document or in a short note under your summary, and use a range: "Salary expectation: $75,000 to $90,000, negotiable based on total compensation and role scope."

2. You are applying through a portal with no other pay field. Occasionally a small employer takes resumes by email with no application form at all, and asks for expectations in the same message. In that case, put the range in the email body, not on the resume itself. The email is the negotiation document; the resume stays clean.

3. A recruiter you already trust asks for a range to match you to roles. This is not really "on the resume" at all. It is a conversation, and a range given verbally or in a reply email is far easier to adjust later than a number baked into a PDF that gets forwarded around a company.

Everything else, leave it off. In particular, never put salary history on a resume, never put a single exact figure when a range would do, and never put three different numbers across your resume, your application form, and your cover letter. Inconsistent numbers read as either careless or inflated, and both readings hurt you.

How to build a range you can defend

A defensible range has three numbers behind it, even though you only ever show two. Before you type anything into a form, do this work:

Start from the posted range, if there is one. When the employer publishes $110,000 to $130,000, your entered range should overlap that band unless you have a strong reason to sit above it and are willing to accept the risk. Entering $150,000 against a $130,000 ceiling is not ambition. It is a self-rejection.

If there is no posted range, research the market for the exact title, level, and city. Job boards, levels-style salary databases, and recruiter-posted ranges for comparable roles will give you a band. Anchor your range to the role's market, not to your last paycheck. Your last paycheck reflects your last employer's budget, your last negotiation, and possibly a pay gap you are trying to escape. None of that prices this job.

Set your floor, your target, and your stretch. Your floor is the lowest total package you would genuinely accept, not the lowest base salary you could survive on. Your target is the number you actually want. Your stretch is the ambitious-but-defensible top. The range you disclose should sit with your target inside it, usually as the upper-middle of the band, so there is room to land above your target if the employer moves, and room to concede without falling below your floor.

Keep the spread honest, roughly 10 to 20 percent. A $75,000 to $90,000 range reads as researched and flexible. A $60,000 to $120,000 range reads as if you have no idea what the job pays, and recruiters treat it that way. Precision helps too: Harvard negotiation research has long shown that precise first offers lead counterparts to make smaller counteroffers, because a specific number signals research. "£52,000 to £58,000" lands differently from "£50,000 to £60,000," even though the midpoints are close.

Price the whole package, not just the base. Bonus targets, equity, pension or 401(k) matching, paid leave, remote flexibility, and working hours all have cash value. A base salary $5,000 below your floor can still beat your target if the bonus and benefits close the gap. Saying "negotiable based on total compensation" is not a dodge. It is the truth, and it keeps the conversation open when the base alone would have closed it.

What to write in each place instead

This is where most guides stop at "don't put it on your resume" and leave you stranded in front of an actual form. Here is what to write, situation by situation:

Application form with a required salary field. Enter your researched range if the field accepts text, or the midpoint of your range if it demands a single number. If there is a notes field, add one line: "Open to discussion once role scope and total compensation are clear." Never enter zero, and never enter "negotiable" alone in a numeric field that a system may read as blank or as the lowest possible value.

Application form with an optional salary field. Leave it blank if you can, or enter your range if the posting already published one and yours overlaps it. Optional fields that you fill with a number above the band buy you nothing and cost you the screening.

Cover letter, when the posting asks for expectations. One sentence, near the end: "My salary expectation for this role is $75,000 to $90,000, negotiable based on the full compensation package." Then stop. The cover letter is not the place to justify the number with a paragraph about your rent.

Recruiter screen, when asked directly. Flip it first, once, politely: "Could you share the budgeted range for this role so I can tell you whether we are aligned?" If they insist, give your range with the same total-compensation line. If they press for a single number, give your target and add that you are flexible on structure.

The resume itself, when forced. One line, at the end, after everything that proves your value: "Salary expectation: $75,000 to $90,000 (negotiable based on total compensation and role scope)." No history, no hourly breakdowns, no "currently earning" line. And if the posting asked for expectations but did not specify the resume, put the line in your email or cover letter and keep the resume clean.

The mistakes that cost people interviews

Undershooting to look flexible. A senior candidate naming a junior salary does not look easy to hire. Recruiters read it as a level mismatch, or assume something is wrong with the candidacy. Price the role, not your desperation.

Overshooting without proof. A range 30% above the posted maximum, attached to a resume whose bullets do not show senior scope, reads as disconnected from reality. If your range is ambitious, your bullets have to earn it first. That means scope numbers in your experience section: team size, budget, revenue, users, outcomes. A resume that proves senior impact can carry a senior number. One that does not, cannot.

Contradicting yourself across documents. Your form says $90,000, your summary says $75,000, your LinkedIn headline implies something else entirely. Application systems store all of it, and inconsistencies get flagged. Pick one range and use it everywhere until the negotiation moves it.

Answering the history question when you do not have to. "What are you currently earning?" is not the same as "what are your expectations?" In the 22 ban states, the first question is off limits, and in the rest it is still a question you can decline politely: "I would rather focus on the value of this role. My expectation for this position is..." Keep the conversation on the future job, not the past one.

Treating "negotiable" as a complete answer. On its own, "negotiable" tells a recruiter nothing they can route your file with, and some systems treat a blank or vague answer as a failed knockout question. Pair flexibility with a range, always.

The 30-second decision test

Before you submit anything, run this check:

1. Did the employer explicitly ask for salary expectations on the resume itself? If yes, add one researched range line at the end. If no, leave the resume salary-free.
2. Does the posting publish a range? If yes, make sure your range overlaps it. If yours sits entirely above it, either adjust or accept that you are likely screening yourself out.
3. Is your range built from market data for this title, level, and city, not from your last paycheck? If not, redo the research before you submit.
4. Is the same range on every document and form? If not, align them now.
5. Could you defend this range in one sentence tied to the role's scope? If not, your bullets need strengthening before your number needs raising.

If you pass all five, submit with confidence. The number is no longer a gamble. It is a researched position, placed where it can be negotiated, on a resume that gets to do its real job first.

Frequently asked questions

Should I put salary expectations on my resume if the job posting asks for them? Yes, but only when the posting asks for them on the resume itself. Use one researched range on a single line near the end of the document, and add that it is negotiable based on total compensation. If the posting asks for expectations generally, put the range in the application form or cover letter and keep the resume clean.

Is it better to give a range or a single salary figure? A range, almost always. A single figure caps you if it is too low and screens you out if it is too high, with no room to move. A 10 to 20 percent range signals research and flexibility while keeping your target inside the band.

What if the application form requires a salary number and will not accept a range? Enter the midpoint of your researched range, and use any notes field to add that you are open to discussion once role scope and total compensation are clear. Never enter zero, and avoid entering your current salary as a substitute for an expectation.

Can an ATS reject me automatically for salary expectations? Yes, in effect. Many portals let recruiters filter or flag candidates whose stated expectations fall outside the budgeted band, and some treat out-of-band answers as knockout logic that removes the file before a human reads it. Treat the salary field as a screening step, not an afterthought.

Should I ever include my current salary on my resume? No. Current pay is history, not an expectation, and it anchors every later number to your last employer's budget. In the 22 US states with salary-history bans, employers cannot ask for it at all. Everywhere else, decline politely and redirect to the expectations range for the role in front of you.

What if my salary expectation is above the posted range but I really want the role? Apply anyway only if your range overlaps the posted band or you are willing to flex on total compensation. If your floor sits above their ceiling, be honest with yourself: the gap is a real mismatch, not a negotiation waiting to happen. A polite application noting flexibility on structure costs nothing, but do not expect the band to move for a candidate the employer has not met yet.

Want to check whether the rest of your resume is working as hard as your salary research? Run it through the free ATS resume checker and see how it scores against a real posting before you send it. And if you are still building the document itself, read what "ATS-friendly" really means and how to find resume keywords without stuffing them first. A resume that proves senior scope is what lets a senior number survive screening.