12 min read
For most US roles, don't put salary expectations on resume PDFs. Answer compensation in the Workday or Greenhouse sidebar when the field is required, and save the real talk for after someone has read your proof. You're not being difficult. You're keeping pay out of a document that's supposed to show tools, scope, and outcomes.
Before you upload again, check your resume for free with the posting pasted in. The checker shows whether you're spending lines on pay instead of keywords the importer actually scores.
Job searching while bills stack up is stressful enough. You don't need a lecture. You need a split rule: what belongs on the file, what belongs in the portal, and what belongs on a phone call once both sides know the role is real.
Quick Wins
- Default: no desired salary line on the resume PDF.
- Required portal field? Answer there with a researched range.
- Trade the pay header for one posting keyword in your summary.
- Talk money live after mutual interest, not in bullet one.
Why salary expectations on resume waste keyword space
US hiring runs on two parallel tracks most candidates never see split apart. Track one is your uploaded resume file. Track two is the application profile: Workday questionnaires, Greenhouse custom fields, Lever compensation prompts, and the required dropdown that won't let you click Submit until something is filled.
Recruiters often see your number in the sidebar before they open the PDF. When you also paste Desired salary $88,000 under your name, you haven't added information. You've duplicated a field the system already captured and burned a line that could have held a tool from the posting.
Applicant tracking systems do not reward compensation honesty with bonus points. They match job description language to experience text. A pay line is neutral at best and costly at worst because resume space is finite on a one-page file.
Humans have a parallel problem. A number at the top anchors you before anyone has decided you're qualified. Too low and you've underpriced yourself out of habit. Too high and you've given them an easy reject without reading your Salesforce pipeline bullet.
Edge case one: the posting says include salary expectation in your resume. That's rare in private sector work, but when it's explicit, put a single clean range line where they asked for it and still don't repeat your life story in the summary. Edge case two: public-sector grade bands are published. Referencing the grade or step is efficiency, not oversharing.
Read how ATS matches resumes to job descriptions when your layout is clean but keyword overlap still feels thin after you remove the pay line.
How to handle pay across resume, portal, and live calls
Use one decision order every time you apply. Check the posting language first, then the portal fields, then what stays on the PDF. Live negotiation comes last.
Step 1: Read the posting for where pay is supposed to live
Most US corporate postings stay silent on resume pay. Some government and union postings name a grade and step. Commission sales postings sometimes expect prior earnings context.
Before: You add Desired compensation $95,000 to every header because one employer asked for it two years ago.
After: You scan each posting. No pay mention on the document means the PDF stays clean. A line that says include expected salary on resume gets one range string in the header only for that employer.
Step 2: Map Workday and Greenhouse fields before you upload
Workday often labels it Desired salary, Compensation expectations, or Current base pay. Greenhouse uses custom questions like What are your salary expectations? or What is your current compensation? Some mark the field required with a red asterisk.
Before: You leave the sidebar blank because pay feels rude, then wonder why Submit stays grayed out.
After: You enter a researched range in the portal field, keep the resume PDF number-free, and note the range in your tracker so you don't contradict yourself on the recruiter screen.
Step 3: Reclaim the header line for a posting keyword
Operations coordinator role on a regional retailer posting wants inventory planning, vendor scorecards, and WMS language in Workday.
Before: Summary opens with Seeking $72,000 base. Two bullets mention RF scanners. No WMS keyword anywhere.
After: Summary opens with Inventory coordinator with Manhattan WMS, vendor scorecards, and cycle-count ownership across 220 SKUs. Pay lives only in the sidebar field you already filled.
Step 4: Software engineer, Greenhouse form with current comp question
Platform team posting searches Python, AWS, and on-call ownership. Greenhouse asks current base salary and desired range on separate lines.
Before: Resume summary lists Current salary $118,000. Experience bullets still describe ticket fixes from year one.
After: Form fields carry your researched band. Resume summary names Python platform reliability and AWS on-call rotation. Bullets show p95 latency work the posting actually asked for.
Step 5: Registered nurse, required field but resume stays clinical
Hospital system posting requires Epic, charge nurse experience, and precepting for a med-surg unit.
Before: Header line Desired salary $78/hr. Generic patient care bullets with no charge language.
After: Portal hourly range entered once. Resume leads with RN, Charge Nurse, Epic flowsheets, precepted five orientees on a 28-bed unit. Pay never competes with clinical keywords.
Edge case: posting asks for salary history
Some legacy forms still ask what you earned at your last job. Many US states restrict salary history questions, but the form may not know your zip code.
Before: You paste last year's base into the resume summary and the Workday history field.
After: You answer only where the form requires it, focus the resume on scope, and pivot live talk toward market range for the new role's responsibilities. Know your state rules before you type anything.
Edge case: optional salary field with no asterisk
Greenhouse sometimes lists compensation expectations as optional. That is not an invitation to move pay onto the PDF.
Before: You skip the optional field and add a pay range under your email instead.
After: You leave optional fields blank unless you have a researched band ready, keep the resume clean, and wait for the recruiter screen to align on range once they've seen your Epic or Salesforce proof.
Copy-paste block: portal vs resume split
RESUME PDF (default US private sector)
• No Desired salary line in header or summary
• Summary first line = role + 2 posting keywords + scope signal
• Experience bullets prove tools (Salesforce, Epic, Python, WMS)
PORTAL FIELD (when required)
• Desired range: $X to $Y (researched for role + metro)
• Do not repeat the same range in the PDF summary
• Save the exact numbers in your application tracker
LIVE RECRUITER SCREEN
• Confirm range aligns with posting level
• Ask about bonus, equity, benefits, and hours
• Negotiate after mutual fit, not before proof
Run the split top to bottom before you tweak verbs. Portal answers and PDF proof are different containers. I've screened the same range twice on one file in Workday, and the version that moved forward spent the header on keywords instead.
For file type questions after you strip the pay line, see PDF vs Word resume for ATS . A plain DOCX with a keyword-rich summary beats a designed PDF that hides compensation in a text box.
And if you're tempted to add pay because the form feels invasive, remember the recruiter already has a compensation column in the ATS. Your job on the PDF is proof, not pre-negotiation.
Where compensation answers backfire on screen and in the parser
Duplicating pay on the PDF after you filled the sidebar. Recruiters see both. You look unaware of how the portal works. Fix: one source of truth in the form, zero on the file unless the posting demands it.
Leaving a required field blank to seem flexible. Workday won't always let you submit. Fix: enter a researched range. Flexibility is a sentence on the call, not an empty box.
Putting past salary in the summary. Old base pay rarely matches the new role's market and can anchor you low. Fix: scope bullets with budget, team size, or revenue you touched, not what HR paid you last year.
Single-number anchors. One integer gives no room to negotiate. Fix: always use a range in portal fields and live talk unless the form forces a single box.
Trading a skills line for pay. That header row could hold Manhattan WMS or Epic charge experience. Fix: delete the pay line before you upload and paste one posting keyword into the freed space.
Discussing pay in the cover letter opening. Letters should name fit and scope, not negotiate before the resume is scored. Fix: keep money in portal fields and phone screens. Use the cover letter generator for fit language, not compensation tables.
Exception: if the employer is federal, state, or municipal and publishes the grade, referencing the grade on the resume saves everyone time. That's not the same as guessing a private-sector band in your header.
Protect keywords before you answer pay in the portal
Upload your DOCX and the posting to HireFlow's free ATS resume checker . You'll see whether removing the pay line opened room for tools the job description repeats three times.
When the role is a stretch but your scope is strong, run score your job match after the keyword pass. Clean pay hygiene does not invent skills the posting requires in bullet one.
Do this now: Delete any desired salary line from the PDF, answer required portal fields with a researched range, rewrite the freed summary line with two posting keywords, then run the checker before the next upload.
What to change tonight
Salary expectations on resume files are the wrong default for most US applicants. The portal field, the PDF, and the phone screen are three different containers. Treat them that way and you stop arguing with yourself before a human reads bullet one.
- Delete pay lines from the PDF unless the posting explicitly demands them.
- Fill required Workday and Greenhouse compensation fields with a researched range.
- Spend the freed header space on two posting keywords.
- Track what you entered so live talk matches the portal.
- Run the checker after export, not before you strip the pay line.
Open the posting you want most. Run a free ATS check , confirm keywords beat compensation on the page, and submit one clean upload with the sidebar filled.
Read more
Frequently asked questions
Usually no for US private-sector roles. The resume file should prove scope, tools, and outcomes. Put a researched range in the portal field when Workday or Greenhouse marks compensation as required, and keep the PDF number-free unless the posting explicitly tells you to include pay on the document itself.
Answer the form field. A required Workday or Greenhouse compensation question is a separate data point from your uploaded resume, and leaving it blank can block submission before a recruiter opens your file. Use a researched range, not a single integer, and do not repeat the same number in your summary line on the PDF.
It steals space, not magic points. Applicant tracking systems score overlap between the job description and your experience text. A header line like Desired salary $92,000 does not add a skill the posting asked for, but it does consume a line you could spend on Salesforce, SQL, or Epic.
After there is mutual interest, usually on a recruiter screen or hiring manager call, not in the first upload. Anchor with a researched range, ask about bonus, equity, and benefits, and treat base pay as one piece of total compensation rather than negotiating from a number typed into a resume header.
Yes, but they are exceptions. Some public-sector postings publish pay bands and expect you to reference the grade. Commission-heavy sales roles sometimes expect earnings transparency. If the job post literally says include salary expectation in your resume, follow that instruction on the document, not only in the portal sidebar.