10 min read
You typed a reasonable salary range. The portal said application received. Two hours later, rejected. No human ever opened your resume. That's not bad luck. That's how hiring systems handle salary data when your form answer sits outside the req band or fights with a number the parser pulled from your file.
Most job seekers treat pay as a negotiation that happens later. ATS platforms treat it as structured data that can hard-stop your profile before keyword scoring runs. You won't get a phone call to explain a typo. The row just disappears from the recruiter queue.
Before you tweak bullets again, check your resume for free and confirm your file isn't leaking old compensation figures into fields recruiters compare against your application answers. If you're applying through Workday tonight, you need the form and the PDF telling the same story.
This page explains where salary lives inside Workday, Greenhouse, Lever, and similar tools, which inputs actually trigger filters, and how to fix mismatches you can control tonight without guessing what a recruiter really wants to pay.
Quick Wins
- Search your resume PDF for dollar signs and delete pay from bullets unless required.
- Screenshot every compensation question before you submit; answers are hard to edit later.
- Match form range to posted band when the employer shows one.
- Reopen a rejected application and compare form salary to any parsed resume numbers.
The symptom: silence right after you name a number
How hiring systems handle salary data starts with a split most candidates never see. Your resume upload feeds one pipeline. Your application form feeds another. Recruiters often get a side-by-side view: structured compensation fields on the left, parsed resume text on the right. When those disagree, some configs auto-archive you before anyone reads bullet one.
The symptom looks like every other rejection. Status stuck at submitted. No interview invite. Maybe a generic email hours later. You assume fit was wrong. Sometimes fit was fine and a pay field killed the row in the recruiter queue.
Screening reality: I've filtered Workday lists on compensation out-of-band before I opened a single PDF. The resume never got a chance to argue.
Salary data also shows up in places you did not intend. Headers with "desired $95K." Summary lines with "seeking six figures." Old bullets that mention "managed $2M budget" beside a current-pay question. Parsers grab digits. Forms store intent. Filters compare both.
Greenhouse often stores compensation answers in candidate profile fields recruiters sort on. Lever ties custom questions to pipeline stages. Workday bundles pay into the applicant record beside visa and relocation flags. iCIMS can feed HRIS exports where pay history follows internal transfers. The vendor changes. The pattern does not: typed numbers become sortable columns.
When you wonder why a strong resume vanished, check whether anyone could sort the req by "expected compensation" descending and never scroll past your row. That is a normal Tuesday workflow, not a conspiracy against your formatting.
Read how salary signals affect screening for the recruiter-side filter stack beyond raw form fields.
Three causes and how to tell which one hit you
Where each platform stores pay (and what parsers ignore)
Workday application flows usually ask compensation after resume upload. The file parses into experience blocks. Pay questions write to separate numeric columns. Recruiters building a list view can hide the PDF entirely and sort on expected salary alone.
Greenhouse custom application questions map to profile properties. Some companies require current and expected on every req. Others hide pay until late stage. Either way, the answer you type is searchable metadata, not buried prose.
Lever resume parsing focuses on employers and skills. Salary in a summary may land in a notes field without structure. That is worse for you: unstructured high numbers look like demands, not calibrated ranges.
None of this replaces keyword matching on skills. It runs parallel. You can pass skill rank and still fail a compensation knockout in the same submission.
Cause 1: Knockout on expected compensation
Workday and Greenhouse often attach required questions to each req: desired salary, current salary, willingness to relocate, visa status. Compensation answers map to numeric fields with min and max bands set by the hiring manager. Type above max and the workflow can reject automatically.
How to tell: Instant rejection email or status change within minutes. No "reviewed" timestamp. Req had a visible range you exceeded. Other applications at similar companies with lower typed numbers get further.
Fix: Target reqs whose posted band overlaps your floor. When no band posts, research title plus city on job boards you trust, then type a range whose top end still fits the role level. Do not copy a dream number from a senior title when the req is mid-level.
Before: "Desired salary: $140,000" on a coordinator req capped near six figures in the posting footnote.
After: "Desired salary: $92,000 to $105,000" aligned to the listed band and your proof level.
Cause 2: Resume text conflicts with form answers
Upload parsers extract unstructured snippets into candidate notes. A bullet that says "earned $78K plus bonus" beside a form where you typed $95K expected reads like inflation or error. Some teams flag inconsistency for compliance review rather than interview.
How to tell: Rejection after a delay, not instant. Portal showed parsed preview with old pay visible. You remember typing a higher expectation in the form. Recruiter never viewed profile according to portal timestamps.
Fix: Strip compensation from resume body unless the employer demands it on the file. Align current and expected fields with what you will say on a phone screen. Re-export PDF and reapply once when the req allows.
Before: Summary line "Seeking $110K+" plus form current pay $72K and expected $115K.
After: Summary focused on scope; form current $72K, expected $88K to $96K with no duplicate numbers in bullets.
Cause 3: Band logic you cannot see from outside
Enterprise setups import internal grade tables. Your answer may be legal and market-normal but still flag as above grade for that location. Recruiters see a warning icon before open. Low priority reqs never get cleared.
How to tell: Posted range looked fine. You typed inside it. Peers with referral codes advance. You stay submitted.
Fix: You cannot hack hidden grade tables. Widen search to employers who post transparent bands, ask the recruiter the range early when you have a human line, and keep proof bullets strong so a hiring manager can argue for an exception when pay flex exists.
Copy-paste compensation audit
"Ctrl+F resume for $ and K; remove pay from summary; note posted band; set form range inside band; current pay matches last W-2 truth; expected top within band; screenshot submitted answers; one reapply with clean PDF if allowed."
Edge case: range required but you will negotiate
Type a range whose floor you would accept if offered today. "Negotiable" in a free-text box is fine when optional. Empty required numeric fields block submit. Padding the top by thirty percent above band still triggers knockouts on strict reqs.
Edge case: remote role, location-based bands
Some systems map your home address to a geo tier. Same title pays differently in Omaha versus San Francisco. Read the fine print on remote reqs. A band listed for HQ may not apply to your state. Adjust typed range to the location field you select, not the city you wish paid more.
Edge case: equity and bonus on top of base
Forms often ask base salary only. If your real ask includes bonus or RSUs, put base in the numeric field and mention total comp in a cover letter or recruiter email after human contact. Do not type total comp into a base-salary box unless the label says total.
Edge case: currency and international applicants
US reqs expect USD. UK postings may want GBP. A typo on currency multiplies your ask in the system's eyes. Double-check the symbol beside the field before submit.
Composite: operations analyst reapply
Before: Resume header "Salary requirement $85,000." Greenhouse form expected $102,000. Auto-rejected overnight.
After: Header removed. Form expected $82,000 to $90,000 inside posted band. Status moved to reviewed in three days.
Composite: nurse applicant, current pay field
Before: Per-diem rate in a bullet, annualized incorrectly by parser. Current pay question answered with hourly rate.
After: Bullets describe patient load and Epic workflows only. Current pay entered as annual base. Expected range matches union scale research for that facility system.
Where pay answers break screening
Putting salary history on the resume "for transparency." Forms already ask. Duplicate numbers create conflict fields parsers love to surface.
Typing the same number in current and expected fields. Recruiters read that as no room to move or as careless clicking. Use a range on expected when allowed.
Ignoring required compensation questions to speed apply. You cannot submit. When optional, skipping may still rank you lower on completeness scores some teams sort by.
Using annual figures when the form asks hourly. Unit mismatch can flag as out of band. Read the label beside the box.
Assuming cover letter overrides the form. Structured fields win in filters. A letter line about flexibility does not rewrite your typed max.
Reusing old application answers on new reqs. Workday sometimes pre-fills prior expected salary from your candidate profile. That number may be wrong for today's band. Clear and retype per req.
Listing budget ownership as personal salary. "Managed $4M P&L" is scope. It is not your W-2. Parsers do not always know the difference.
Applying up-level with down-level pay asks. Low expected pay on a senior title can signal mismatch the other direction. Match level, band, and proof.
Read how to answer desired salary on US applications for scripts when humans ask, not only robots.
Verify file and match score before the next apply
Salary fixes do not replace parsing fixes. Run your clean PDF through the checker with the posting pasted so keyword gaps do not stack on top of compensation knockouts.
Run a free ATS check on the same file you plan to upload. Then score your job match against the req text so you are not fighting pay filters on a role where your skills already miss must-haves.
What to do tonight
How hiring systems handle salary data is blunt: structured form fields beat resume prose, and mismatches beat both. Pull your last five applications, compare typed compensation to any dollar sign still in your PDF, and stop reapplying with conflicting numbers.
Target bands you can defend. Keep proof bullets about work done, not old pay earned. When silence follows a high ask, fix the form and file together before you rewrite your entire career story.
Read more
- Why salary expectations trigger early rejection
- Workday resume format 2026
- Generate a cover letter when the posting asks for flexibility on comp in prose
Frequently asked questions
Most ATS platforms weight salary from dedicated application fields, not resume body text. A number buried in a summary rarely drives keyword rank. It can create mismatches when your form answer differs from resume text. Keep pay discussion in the form unless the employer explicitly asks for it on the file.
Many systems run knockout logic on compensation fields before resume scoring finishes. You may get an instant rejection or a status that never moves to reviewed. Lowering the form number without changing role fit rarely helps. Target reqs inside your range or roles with posted bands that overlap your ask.
Parsers sometimes pull dollar figures from bullets or headers into unstructured notes. Recruiters may see those snippets beside structured form answers. If you list old pay in a bullet and type a higher expectation in the form, the profile looks inconsistent. Align numbers or remove pay from the resume entirely.
Blank required fields block submission. Optional fields left empty may still prompt recruiter follow-up. When the field is required, use a researched range tied to the posting location and title. Never type zero or a joke number unless you want an auto-filter to fire.
Some enterprise setups flag outliers against internal bands or imported benchmark tables. Others rely on recruiter judgment after import. You cannot see which mode a company uses from outside. Treat every compensation question as a hard filter until you know otherwise.