11 min read
If your PDF looks polished but the Workday preview shows missing employers, scrambled dates, or skills floating without a job title, your file isn't ATS friendly yet. The parser failed before a recruiter opened the req. That's the symptom. The rest of this page shows three causes, how to spot yours, and the fix for each.
You're not crazy when you get silence after qualified applications. You're often losing on structure, not talent. Before you rewrite bullet three for the fifth time, check your resume for free with the posting pasted in. You're checking whether the file imports cleanly, not whether you're worthy of the role.
Job searching while you're still employed is draining enough. You shouldn't have to guess whether Greenhouse read your current title. I've screened stacks where a two-column template hid the last employer entirely in the parsed view.
Below you'll see what breaks first in US portals, three root causes, quick tests to tell which one is yours, and fixes you can run tonight. When the portal asks for a letter, generate a cover letter that repeats the same job title string your resume uses so nothing contradicts on upload.
Quick Wins
- Paste into Notepad. Reading order must match your PDF.
- One column. Contact block on top, not in a sidebar.
- Standard headings: Experience, Education, Skills.
- Keywords inside dated bullets, not a keyword cloud.
The symptom: a perfect PDF and a broken preview
US corporate hiring runs through Workday, Greenhouse, Lever, Taleo, or iCIMS before a recruiter skims your bullets. The symptom isn't always a rejection email. It's often a portal preview that doesn't match the file you uploaded.
Employer names vanish, dates detach, or your most recent role drops to the bottom. You still see a clean PDF on your screen. The ATS stored a different version. Recruiters search parsed fields, not your design.
Another version of the same symptom: you pass keyword scanners but never hear back. The parser read your Skills list and missed the Salesforce bullet where you actually used it. Match scores look fine. Human screeners see an empty Experience line for a required tool.
How to know if your resume is ATS friendly in the US starts with comparing three views: your PDF, a plain-text paste, and the portal preview after upload. When those three disagree, the file isn't ready no matter how strong your background is.
For file-type failures that strip text even on simple layouts, read how resume file type impacts screening . Fix the container first, then rerun the plain-text test.
Three causes, how to tell which is yours, and the fix
Cause 1: Layout the parser reads out of order
How to tell: plain-text paste puts your phone number between two jobs, or dates appear before company names. Canva, two-column Word templates, and table-based designs cause this most often.
Before: Left sidebar holds contact info and Skills. Right column lists Experience with dates in a narrow table cell.
After: Name and email on line one. Each job as Employer, City ST on one line, Title | January 2022 to March 2024 on the next, bullets below.
The fix: flatten to one column. Move Skills under Experience or after Education. Re-export and paste again. If reading order matches how you'd read aloud, layout is no longer the blocker.
Cause 2: Non-standard headings the importer skips
How to tell: the preview shows Education but Experience is blank while your PDF has a section titled Professional Journey or Career Highlights.
Before: Section headers read My Path, Core Competencies, and Selected Wins.
After: Experience, Skills, Education. Same bullets underneath. Only the labels change.
The fix: rename sections to words parsers expect. Keep creative wording inside bullets, not in headings. Greenhouse and Workday map Experience and Education to fixed fields. Cute labels don't map.
Cause 3: Keywords parked without dated proof
How to tell: automated tools praise keyword density, but recruiters ctrl-f the tool name in Experience and find nothing. Skills lists alone don't carry tenure.
Before: Skills line lists Python, SQL, Tableau, Salesforce. Experience bullets say managed projects and supported stakeholders.
After: Bullet one under current role: Built Tableau dashboards for weekly pipeline reviews in Salesforce, cutting manual report prep from four hours to 45 minutes.
The fix: mirror three required terms from the posting inside dated bullets. Keep a short Skills section for search, but put the proof where parsers attach dates and employers.
Copy-paste block: five-minute ATS friendly check
1. Export PDF or DOCX from your editor.
2. Select all, copy, paste into Notepad or TextEdit plain mode.
3. Read top to bottom. Flag any date before its employer.
4. Upload the same file with the target posting to a checker.
5. Open portal preview if available. Count jobs imported vs PDF.
6. If counts differ, flatten layout before editing bullet wording.
Edge case: headers and footers with your name and page numbers sometimes duplicate contact info in the parsed view. Delete footer content and keep one contact block at the top.
Edge case: icons and rating bars for skill levels often paste as blank lines or garbage characters. Replace with a plain comma-separated Skills list.
How to tell if your resume is ATS friendly before you apply: run the paste test, then upload to a checker with the exact posting. If the checker shows SQL in Skills but the req asked for SQL in a data analyst role with five years, you have a keyword placement problem, not a missing skill problem.
Bullet length past three lines often gets truncated in preview panes. Split long bullets into two lines with the tool name in the first eight words of line one. Recruiters on laptops see the top half first.
Acronyms need the spelled-out form once per page when the posting uses both. Write Search Engine Optimization (SEO) on first use, then SEO alone in later bullets. Some Workday builds index only the long form unless both appear.
For title strings that don't match the posting after parsing, see how recruiters interpret job titles . Title search runs on the same parsed fields as employer names.
When the file still fails after a clean plain-text paste
A clean paste is the baseline, not a guarantee. These edge cases explain why some US uploads still break after you flatten columns.
Scanned PDFs from print shops. They're images. Taleo can't read text that isn't text. Retype into Word and export a digital PDF.
Password-protected or portfolio-linked files. Some portals strip embedded links and drop the file. Submit a plain attachment with URLs spelled in the header line.
Special characters in employer names. Ampersands and accented letters occasionally split fields. Spell the legal name simply if the preview garbles it.
Graphics under your name. Logos and headshots push contact lines down in the parse order. Recruiters still see them on the PDF, but search fields may miss your email.
Exception: federal resume builders with fixed fields are a different game. Use their boxes first, then attach a one-column PDF supplement only if the instructions allow it.
This won't fix applying to roles where your years of experience genuinely fall short. It stops a qualified background from disappearing because the importer stored an empty Experience block.
Before: Designed resume from a template site with skill bars and a photo. Plain-text paste shows dots and blank lines between jobs.
After: Calibri 11-point single column, no photo, Skills as a comma list, same bullets rewritten underneath standard headings.
Run the check on the phone you actually apply from. Mobile uploads sometimes recompress images inside PDFs. Desktop export, mobile apply is fine when the file is text-based.
Keep version names boring. Resume_Final_v7.pdf is easier to retest than a new Canva link every week. Change one variable per test so you know what fixed the preview.
If a posting asks for a cover letter upload, use the same contact header format on both files. Mismatched phone formatting between documents triggers manual review flags in some Workday builds.
When you change templates, re-run the plain-text paste even if bullets stayed identical. Layout swaps move dates silently. Treat every export as a new file, not a cosmetic refresh.
Font size below 10.5 point can OCR poorly on older scanners still used in some manufacturing and logistics employers. Eleven-point Calibri or Arial is the boring default that survives most US corporate stacks.
Hyperlinks styled as buttons sometimes paste as URL fragments without anchor text. Spell the link in plain text beside the project name: github.com/yourname/repo. Recruiters click. Parsers index the string.
Multiple jobs at one employer need separate title lines with Month Year ranges. One block that says ABC Corp 2019 to 2024 with three roles buried in bullets often imports as a single job with the wrong title in search filters.
Volunteer work belongs on the page when it carries relevant tools, but label it Volunteer or Pro Bono in the title line. Parsers that map only Experience may skip unlabeled sections unless the heading says Experience includes volunteer roles.
Run a full parser check before Submit
Upload your flattened file and the posting to HireFlow's free ATS resume checker . Confirm required terms appear in Experience, not only in Skills, and that no section imported empty.
When you're rebuilding from a template that failed the paste test, build your resume in a single-column layout so you don't reintroduce sidebar traps on the next edit.
Do this now: Paste into plain text, fix reading order, upload once, read the preview job count before you hit Submit on the req.
What to do now
How to know if your resume is ATS friendly in the US comes down to three aligned views: PDF, plain-text paste, and portal preview. When they match, you can focus on tailoring bullets instead of fighting invisible parse errors.
- Flatten to one column tonight.
- Rename sections to Experience, Education, Skills.
- Move three posting keywords into dated bullets.
- Run the plain-text paste before every new template.
- Read the preview job count before Submit.
Open the req you're targeting. Run a free ATS check , fix whatever the preview drops, and send one clean upload.
Read more
Frequently asked questions
Copy your exported file into a plain-text editor. If employer names, job titles, and dates appear in reading order without table gaps, the parser will likely read the same structure. Upload the same file to a target posting in HireFlow's checker and confirm required skills land in Experience lines, not only in a sidebar Skills box.
Not always, but left-column contact blocks and right-column dates are a common failure mode. Workday and Greenhouse often read columns top to bottom, which swaps employer order or drops dates. A single-column PDF with contact lines at the top parses more predictably than a designed template with a colored sidebar.
Follow the portal prompt. When both are accepted, DOCX usually survives reformatting better on older Taleo builds. Simple single-column PDFs export cleanly from Word when you avoid text boxes. Never upload a scan or image PDF unless the employer explicitly asks for one.
A keyword list without dated Experience proof reads hollow to recruiters after the parser passes the file. Keywords belong inside bullets under the role where you used the tool. If match tools score you high but humans pass, compare bullet one on your resume to bullet one in the posting.
Rebuild when plain-text paste scrambles section order, dates detach from employers, or the portal preview shows fewer jobs than your PDF. Wording edits cannot fix layout traps. Export a single-column Word file, re-enter dates beside titles, and test again before you apply to the next req.