7 min read
You've probably heard that missing keywords kill applications. That's real, but it's rarely the first failure.
When a file arrives scrambled, recruiters see blank phone fields or jobs listed out of order. Check your resume for free on the exact PDF or DOCX you'll upload, then walk this checklist group by group.
Job searching is already draining. This won't turn a stretch role into a yes. It stops a qualified single-column file from dying because a skills table ate your dates.
Tonight you need a pass/fail audit you can finish in one sitting. We'll start with structure, then contact, then the keyword layer that only works when text extracts cleanly.
Layout and reading order
Decision rule: if paste order looks wrong to you, assume the ATS sees the same shuffle.
- Two columns or sidebar skills: parsers often read one full column before the other. Skills can land under the wrong employer.
- Tables for alignment: even invisible grid lines break sequence in Taleo and older Workday builds.
- Text boxes and floating objects: contact details export last or not at all.
- Icons and skill bars: replace with spelled-out tools in a plain Skills section or in bullets.
- Headers and footers: move name, phone, and email into the body. Many imports skip margin zones.
Before: a Canva-style template with a photo strip and a right rail of tools.
After: one column, 11-point Calibri or Arial, black text, standard headings.
Before: skills live in a sidebar table the parser reads after Education.
After: skills appear as a short list under Experience or in plain bullets tied to each role.
For table-specific traps, read why tables break US ATS parsing before you rebuild the same grid in a new color.
Contact block and file type
- Phone format: use digits with a clear label or a standard US pattern parsers recognize.
- Email in body: not inside a shape or footer linked to the page edge.
- LinkedIn URL: full https link on its own line, not buried in a icon row.
- File type: match the posting. When silent, many enterprise Workday flows prefer DOCX; Greenhouse often accepts a clean PDF if text highlights.
- Scanned PDF: if you cannot select text, the ATS treats it like a photo. Re-export from source.
I've screened stacks of these in Workday and Greenhouse, and the files that import cleanly almost always use boring contact lines at the top of the main column.
When phone fields import empty, see why ATS can't read your phone number sometimes for header fixes that do not require a new template purchase.
Experience lines recruiters expect to extract
- Standard headings: Experience, Education, Skills. Creative labels slow section detection.
- Title | company | dates on one line: avoids dates attaching to the wrong role.
- One date style: pick Month Year or MM/YYYY and keep it through the file.
- Bullets as real sentences: start with a verb, name the tool once, show scope.
- No nested tables inside jobs: promotions belong as separate entries or clear subheads in plain text.
Copy-paste job header pattern:
Senior Analyst | Northwind Health | Mar 2021 to Present
• Built weekly margin dashboards in Looker, cutting manual Excel pulls for finance
Align exports with Workday resume format guidance for 2026 when the employer uses that portal, especially on the post-upload field review screen.
Common resume mistakes that trigger ATS rejection after the file parses
Only run this group after paste order passes. Keywords cannot rescue a file whose current title never imported.
- Skills list without proof: mirror posting language in the first bullet under your current job, not only in a comma line.
- Synonyms only: if the posting says "Salesforce," say Salesforce in a bullet that shows use, not only "CRM."
- Stale master: one generic file sent everywhere leaves role-specific tools out of searchable text.
- Keyword walls: gray skill clouds and dense comma paragraphs read like stuffing and bury real accomplishments.
For where keywords actually show up in search, read resume keywords that actually increase interviews after layout is stable.
Verify before submit
Run tools on the upload file, not your design master. You want confirmation that sections imported, then a keyword pass against the posting.
Run the free ATS check against the job description after paste-test passes. Formatting errors should surface before you burn an application on a scrambled export.
Optional letters still need the same title strings as the resume. Draft one with the cover letter generator when the posting allows a note.
Score your job match once contact and Experience text look intact. Fix gaps in bullets under your current role, not in a sidebar table.
Fix order for tonight
Sequence: paste test, flatten columns, repair contact, normalize job headers, then tailor bullets for the posting. Skipping straight to keywords on a two-column file repeats the same silent rejection.
If every export needs surgery, rebuild once in Build your resume and stop re-fighting the template on each application.
Read more
Frequently asked questions
Formatting usually comes first. If the parser cannot read your contact block or job titles in order, keyword matching never gets a clean string to score. Fix layout and paste order, then mirror the posting in your current role bullets.
Not always, but they are a common failure point. Many parsers read left column top to bottom, then right column, which can attach skills to the wrong employer or drop dates. A single column is the safer default for Workday and Greenhouse uploads.
Fix the source layout in Word or Google Docs, then export the format the posting requests. Run a paste test on the file you will upload. A pretty PDF with scrambled copy-paste order fails the same way a Word file with hidden tables does.
Select all text in your upload file, paste into a plain editor, and search for your phone number and latest job title. If either is missing or out of order, repair structure before you spend time on keyword swaps.