What if the job posting requires salary requirements?

Comply, but put the number in the cover letter or the application form field rather than the resume, and give a researched range instead of a single figure. Add a flexibility sentence, such as noting the range is negotiable depending on the full compensation package. Ignoring an explicit instruction can get your application discarded, so do not simply skip it.

Does an ATS screen out resumes based on salary?

ATS platforms do not read salary numbers off your resume, but many applications include a required salary expectation field, and recruiters or knockout rules can filter on that answer. That structured field is where a mismatched number gets you cut, which is why researching the market range before applying matters so much.

Should I put my current salary on my resume?

No. Your salary history is private, it invites lowball anchoring, and in a growing number of US states and cities employers are not even allowed to ask for it. Your past pay also says nothing about your qualifications, which is what a resume is for. Keep every version of your resume focused on what you did and can do.

What should I write if a form forces a single salary number?

Enter the midpoint of your researched range, not your minimum. Some fields accept text, in which case a range like 70,000 to 80,000, negotiable, is better. If it forces one number, choose one you would be genuinely happy with, because it tends to become the ceiling of your offer, not the floor.

Should You Put Salary Requirements on Your Resume?

Q: Should you put salary requirements on your resume?

No, almost never. A number on your resume can only hurt you: too high can take you out of the running before anyone reads your qualifications, too low anchors your future offer beneath the budget. Salary belongs in a conversation after the employer wants you, when you have leverage. The only real exception is when a job posting explicitly requires it, and even then it usually belongs in the cover letter or application field, not on the resume itself.

The posting says "include salary requirements." Your stomach drops. Say a number too high and you are gone before anyone reads a word about your experience. Say one too low and you have just discounted yourself for the next several years. It feels like a trap because, mostly, it is one.

Here is the good news: there is a clear, defensible answer to this question, plus a small set of scripts for the exceptions. Ten minutes from now you will know exactly what to do with every version of this request.

The short answer: keep numbers off the resume

Your resume has one job: show that you can do the work. Every line should earn you a conversation. A salary number does the opposite of that job, because it gives a stranger a reason to end the conversation before it starts.

Think about the only two ways it can go:

Your number is above their budget. You are filtered out instantly. Nobody calls to negotiate with a resume. Maybe you would have accepted their range once you heard about the bonus, the equity, or the growth. You will never get the chance.
Your number is below their budget. Congratulations, you just set the anchor. If they budgeted 85 and you wrote 70, your offer will hover near 70. That gap compounds with every raise calculated as a percentage of your base.

There is no third outcome where the number helps you. Even a perfectly-guessed number merely does no damage. That is a bet with zero upside, made at the exact moment you have the least information and the least leverage. Salary is a conversation for later in the process, ideally after they have decided they want you. There is a full breakdown of when to bring up salary in the interview process if you want the timing playbook.

One more practical reason: a resume gets reused. The version with "$68,000" baked into it will be the version you forget to edit when you apply for the $90,000 role.

But what if the posting demands it?

Some postings explicitly say "applications without salary requirements will not be considered." This is usually a compliance filter: the company wants to screen out mismatches early, and sometimes wants to see whether you follow instructions.

Do not ignore an explicit instruction. But comply on your terms:

Put it in the cover letter or the application field, not the resume. The resume stays clean and reusable. One sentence in the cover letter satisfies the requirement.
Give a researched range, never a single number. "My salary requirement is in the range of $70,000 to $82,000, depending on the overall compensation package."
Add flexibility. "I am open to discussing this range based on the full scope of the role." This signals you will not blow up over a small gap.

The range should be real. The bottom number must be one you would actually accept with a smile, because employers hear the bottom of your range loudest.

Get the number right before you write anything

A range is only as good as the research behind it. Guessing from your current salary is the most common mistake, because your current salary reflects your old negotiation, not today's market.

Spend an hour on this before you apply anywhere:

Check posted salary ranges on job listings in your target role and location. Pay transparency laws now force many employers to publish ranges, which is free intelligence. Learn how to read the salary range on a job posting, because the top and bottom of those ranges mean specific things.
Cross-reference at least two salary data sources rather than trusting one site's single estimate.
Adjust for your market: remote, major metro, or lower cost-of-living region.
Place yourself honestly within the range based on your years and depth of experience.

There is a fuller method in how to research your market salary before you negotiate. The point is that "my requirement is $75,000 to $85,000" should be a statement you can defend with sources, the same way every bullet on your resume should be a claim you can defend with a story.

The application form that forces a number

Online applications are where this question actually bites. Many ATS application flows include a required "desired salary" field, and unlike your resume, that structured field can be used to sort and filter candidates.

Tactics, in order of preference:

If the field accepts text: enter a range with the word negotiable. "70,000 to 80,000, negotiable."
If it forces a single number: enter the midpoint of your researched range, not your minimum. Forced single numbers tend to become ceilings.
If it allows zero or 999: some people use placeholder numbers to dodge the question. This is risky. A zero can read as sloppy, and an absurd number can auto-reject you. Use a real midpoint instead.

Whatever you enter, write it down. You will be asked to confirm it on the phone screen, and inconsistency hurts more than any specific number. The companion guide on answering salary expectations on an application covers the phone conversation that follows.

Never list your salary history

Salary requirements and salary history are different questions, and history deserves an even firmer no.

It may be illegal for them to ask. Many US states and cities have banned salary history questions precisely because they perpetuate underpayment. You are under no obligation to volunteer what the law protects.
It anchors you to your past, not your value. If you were underpaid before, disclosure imports that underpayment into your new job.
It is nobody's business. Your last employer's budget decisions are not evidence about your abilities.

If a form asks for salary history, leave it blank where possible, enter zeros if it forces numeric input, and be ready to say on a call: "My previous compensation was tied to a different role and market. For this position, my expectation based on the market is X to Y." Calm, honest, done.

What belongs on your resume instead

Every square inch you might have spent on salary should carry evidence of value, because the strength of your eventual negotiation is built on the resume, not written into it:

Quantified accomplishments. Real numbers about work you did are the raw material of every raise and offer conversation.
Skills that match the posting. The keywords the ATS and the recruiter are scanning for.
Scope. Team sizes, budgets you managed, volume you handled. Scope is what justifies the top of a salary band.

A resume that proves value earns you the leverage to negotiate. A resume that names a price gives that leverage away on page one.

Make sure the value actually gets through

Here is the quiet failure mode: you keep salary off the resume, you load it with genuine accomplishments, and then the ATS parser garbles the formatting and half your evidence never reaches a human. Your negotiating position was built on bullets nobody read.

Before your next application, run the free Bounce scan at careerbounce.io. It shows you exactly what the hiring bots extract from your resume: which skills registered, which history parsed, what got lost. It is free, private, and runs entirely on your device, nothing is uploaded. Fix what the bots misread, keep your number for the conversation where it belongs, and walk into that conversation with a resume you can defend line by line. That combination will not guarantee an offer, nothing honest can, but it puts every dollar of your real value on the table.