11 min read
You polished one master PDF and sent it to six reqs this week. Greenhouse moved you to reviewed on Tuesday. Workday on the same bullets went silent. Lever bounced an instant auto-reply. You're not imagining it. The file didn't change. The portal's field map and keyword weights did.
Check your resume for free with each posting pasted in side by side. You'll often see the same green checks on one req and red gaps on another while the PDF looks identical on your screen. That's why one resume doesn't work everywhere, and it's fixable without rebuilding your whole career story from scratch.
Below: the symptom when a master file splits outcomes, three causes tied to portals and seniority bands, how to tell which one hit you, and forks you can run in ten minutes. Job searching is exhausting when you've already edited twice. This page is hands-on diagnosis, not a lecture on tailoring importance.
Pull up last week's applies in a spreadsheet before you read on. Note portal name, req level, and whether you got a preview or silence. That column tells you faster than guessing which paragraph failed.
Quick Wins
- Log portal name and req level for every apply this month.
- Highlight three must-haves from the posting before you touch the master file.
- Rewrite bullet one under your current role for each fork, not the whole page.
- Paste each exported PDF into Notepad and confirm employers still parse in order.
The symptom: one master file, three different outcomes
A composite operations analyst sends the same two-page PDF to a mid-level req on Greenhouse, a senior band req on Workday, and a contract role on Lever. Greenhouse shows reviewed. Workday leaves the profile blank on experience dates. Lever auto-closes on a years-of-experience knockout the form never flagged on the other two portals.
The pattern recruiters see: candidates treat silence as random bad luck when the master file never matched how that portal maps fields or weights keywords for that seniority band.
Parsers do not share one rulebook. Workday may strip header contact bars and misread table cells. Greenhouse often imports a sidebar Skills block cleanly while Workday dumps it under Education. Lever may enforce hard filters on years before your bullets get scored. I've seen the same PDF pass one preview and fail the next on field order alone. Same upload, different layer failing each time.
Human recruiters still ctrl-f the posting's top three must-haves inside dated Experience. A master file built for mid-level language can look thin when a senior req searches for scope words like led, owned, or cross-functional while the bullets still say supported and assisted.
Read how to tailor a resume to a job description when you need a thirty-minute keyword pass after you diagnose the portal layer. Tailoring comes after you know which field map failed.
Three causes when why one resume doesn't work everywhere shows up
Cause 1: Portal field maps read the same layout differently
Two-column templates put Skills in a left rail and Experience in the main column. Greenhouse may attach skills to searchable fields. Workday sometimes reads left-to-right across the page, wedging skill lines between employer names. Your keywords exist on the PDF. They are not attached to the job title you want scored.
Before: Canva two-column layout with Skills sidebar; same file uploaded to Workday, Greenhouse, and iCIMS without changes.
After: Single-column PDF, 11-point Calibri or Arial, Skills section after Experience, Month Year dates inline on each title line; minor export saved per portal when preview shows scrambled fields.
Fix: Export and paste into Notepad after each upload test. If employer blocks jumble, rebuild layout before you fork keywords. Screenshot broken portal previews when the employer shows parsed fields. That tells you whether only Skills failed or dates never imported.
Cause 2: Keyword weights shift by seniority band
Mid-level reqs search tool proof in bullet one. Senior bands search scope, budget size, team size, and stakeholder count in the same lines. A master file written at mid-level density can parse cleanly and still lose senior screens because the weight sits on words you never promoted from bullet four.
Before: Bullet one under current role: Supported monthly reporting and ad hoc analysis for finance partners.
After (senior fork): Owned Looker and SQL reporting for 8 finance directors; cut close cycle prep from 6 days to 2 by standardizing Month Year revenue models across 3 business units in FY2025.
Fix: Read the req band honestly. If the posting repeats led, owned, or director-level scope, promote your largest defensible scope metric to bullet one. Keep the mid-level fork for IC reqs. Two bullet-one variants beat one generic master sent everywhere.
Cause 3: Knockout filters differ before resume body scores
Sponsorship, clearance, salary ceiling, location, and max-years filters run on application forms that are not identical across portals. Lever may reject at submit when Workday only flags the mismatch in recruiter view. Your resume never gets keyword-scored because the form already filtered you out on apply two while apply one still shows pending.
Before: Same salary expectation and location answers copied across six portals without reading each req's remote policy or band language.
After: Spreadsheet column for knockout answers per apply; salary aligned to posted band when shown; location answer matches req city or stated remote policy before upload.
Fix: Reopen saved applications when the portal allows. Fix sponsorship, salary, and location before you fork bullets again. A perfect PDF cannot beat a hard knockout on max years when the form enforces a ceiling you already exceeded.
How to tell which cause is yours
Field map failure: Portal preview scrambles employers, dates, or Skills placement while your PDF looks fine. Fix layout first.
Seniority weight failure: Preview parses cleanly, mid-level reqs respond, senior reqs stay silent with the same file. Fork bullet one and summary scope.
Knockout failure: Instant auto-reject or closed status before reviewed, often with no recruiter view. Audit form answers before rewriting Experience.
You can hit two layers at once. Workday scrambled Skills on upload three while upload four failed on salary band. Fix layout and knockouts before you spend an hour on keyword synonyms that never reach a scored profile.
Copy-paste fork checklist per apply
Copy-paste this into your tracker row: "Portal: [Workday/Greenhouse/Lever/iCIMS] | Band: [IC/mid/senior] | Must-haves: [3 terms] | Bullet one rewrite done | Skills echo done | Knockout answers checked | Notepad test pass | Filename: Company-Role-YYYY-MM-DD.pdf."
Edge case: you apply to the same company on two portals during an acquisition. Field maps may differ between legacy Taleo and new Workday. Treat them as separate fork rows even when the job title matches.
Edge case: contract and full-time reqs for the same function. Contract postings often weight recent client names and short tenure windows. Lead with contract employer lines and Month Year ranges instead of hiding contract work in a generic consultant block at the bottom.
Pair 4: registered nurse across hospital systems
Before: One master file lists Epic, Cerner, and med-surg experience in Skills while bullet one reads provided patient care on a busy unit.
After: Fork for Epic req: Documented care in Epic on 32-bed med-surg unit; precepted 4 orientees through fall-prevention workflows. Fork for Cerner req swaps the EHR name in bullet one and Skills echo only.
Pair 5: software engineer across startup and enterprise
Before: Master file leads with maintained microservices and collaborated with product.
After (startup fork): Built Python FastAPI services for 0-to-1 billing product; shipped 14 endpoints in 9 weeks with pytest gates in GitHub Actions. After (enterprise fork): Standardized Java Spring APIs for 22 internal consumers; cut P1 incidents 40% by adding contract tests in Jenkins pipelines.
See resume keyword placement: skills vs experience when Skills light up on one checker but Experience stays generic on every portal.
Master-file habits that still waste applies
Sending one PDF without a portal column in your tracker. You cannot diagnose field maps if you do not log where each file went.
Full redesigns instead of bullet-one forks. Ten targeted minutes beats three hours reformating margins while knockouts still fail.
Assuming silence means unqualified. Scrambled previews and salary knockouts mimic rejection feelings while the body never scored.
Keyword stuffing the master to cover every portal. White text and repeated must-haves without proof fail human review and some parsers flag noise.
Ignoring seniority language on the same title. Senior and mid-level reqs share job titles but search different scope signals in bullet one.
Reusing knockout answers from last month's apply. Bands, remote policies, and sponsorship questions change per req even inside one company.
Read why ATS rejects resumes when you need the full rejection stack beyond portal differences alone.
Score each fork before second upload
Paste the job description into Score your job match after each bullet-one fork. You're checking whether must-haves moved into dated Experience for that specific req, not chasing one perfect percentage across every portal.
Run a free ATS check on the exported PDF with the posting attached. Compare results across two portals on your list this week. Gaps that repeat on every export point to layout. Gaps that move when you fork bullet one point to seniority or keyword weight, not parser failure.
Save checker output beside each fork filename so you know which version already cleared parsing for Workday versus Greenhouse before you reapply. That log stops you from uploading yesterday's master when Tuesday's fork already fixed the field map.
One plain master, a fork per portal and band
Why one resume doesn't work everywhere comes down to field maps, keyword weights, and knockouts that change by portal and seniority band. Your master file is the spine. Forks are ten-minute edits to bullet one, Skills echo, and form answers, not a new career narrative every night.
Open tonight's posting. Log the portal. Rewrite bullet one with three must-haves in the first eight words. Run a free check. Export with company and date in the filename. When the req wants a letter, generate a cover letter that names the same scope you put in bullet one.
This won't fix applying to roles where you lack core requirements. It stops qualified files from dying because Workday read your Skills block as Education while Greenhouse on the same PDF moved you forward.
And if you're tempted to send the master again because you're tired, open your tracker first. One extra fork row tonight beats another week of silence across three portals that never read the same file the same way.
Read more
Frequently asked questions
No single file fits every portal and req band. Workday, Greenhouse, Lever, and iCIMS map Skills, dates, and titles into different searchable fields. A senior band req weights years and scope differently than a mid-level posting with the same job title. One master PDF can parse cleanly in Greenhouse and still miss must-have keywords in Workday because field weights differ. Keep one plain master, then fork bullet one, Skills echo, and knockout answers per posting.
Most people need one plain master plus a ten-minute fork per apply, not twelve full redesigns. Change bullet one under your current role, echo three must-haves in Skills, and adjust summary scope for senior versus mid-level language. Save forks named with company and date so you reapply with the version that already matched that portal's field map, not yesterday's generic export.
Different portals read layout differently. Headers, sidebars, and table cells import into unlike fields. Keyword scoring also weights dated Experience lines higher than undated Skills on most corporate stacks. A file that looks matched on a checker tuned to one parser can still lose when the employer runs Workday with stricter years filters or title normalization you never saw on the first apply.
Rewrite the top of the file, not your entire career. Open the posting, circle three must-haves, and edit bullet one so each term lands in the first eight words under your current employer. Mirror exact spelling from the ad. Swap summary scope lines for senior versus individual contributor reqs. Export single-column PDF. Full rewrites burn hours; targeted forks fix split outcomes without starting from a blank page.
Run the Notepad paste test on each upload. Compare portal previews when employers show parsed fields. If employers and dates parse but keywords fail, fork bullet one and Skills echo. If previews scramble sections, rebuild layout before you tailor again. If knockout answers on sponsorship, location, or salary mismatch the req, fix the form before you blame the resume body.