8 min read
The req closes at midnight. You've got the posting open in one tab, your resume in another, and a checker result that shows a red formatting flag plus a keyword gap for SQL. You can't tell which one to fix first, so you start swapping synonyms and the score barely moves. That's the trap. The checker isn't ranking you against other humans. It's telling you what the parser could read.
Check your resume for free with no job description pasted first. You'll see whether tonight's problem is layout, section order, or wording inside Experience. Most candidates skip that blank scan and waste an hour on keywords while a two-column header still dumps Skills above their current title.
Corporate portals in Workday, Greenhouse, Lever, and iCIMS all build a candidate record from extracted text. When extraction scrambles, keyword edits don't stick where matchers look. When extraction is clean, gap flags usually mean three must-have terms from the posting never landed in bullets recruiters actually read.
Below you'll walk a five-pass workflow in the order parsers expect. Job searching is draining enough without editing the wrong layer. If a gap needs context after bullets are accurate, draft two lines with the cover letter generator once parse flags clear.
Quick Wins
- Blank scan first. No posting pasted until layout flags are gone.
- Paste test: contact, Experience, Month Year dates, then Skills.
- Mirror three must-have req terms inside bullet one under current role.
What an ATS checker scores before you edit a line
A checker compares extracted text to a job description, not your design intent. It does not know you led a team of twelve if that line sat inside a text box the parser skipped. It only scores what entered the text stream: contact fields, job titles, dates, section headers, and bullet text in read order.
Most tools bucket warnings into three layers. Formatting means tables, columns, icon skill bars, or graphics broke extraction. Section order means headers weren't recognized or blocks appeared out of sequence. Keyword gaps mean posting terms never showed up in parsed Experience text, even if they're visible on your PDF.
Those layers have a repair sequence. Layout and section order are prerequisites. Keyword gaps are tailoring work on top of a readable file. Treating a match percentage like interview odds sends you chasing a perfect bar while bullet one still never attached to your current employer in the backend record.
A checker won't tell you whether you're qualified for the role. It tells you whether the file you plan to upload can be read and compared to the posting text. That's still worth fixing before you hit submit on a role you actually fit.
For what each category means in plain language, read what free ATS resume checker results mean . For layout failures that show up as formatting flags, see resume formatting errors that break ATS parsing .
Five-pass order to optimize resume with ATS checker tonight
Work the passes below on the export you'll submit. Don't alternate between an old Word file and a PDF you haven't paste-tested. Each pass has a stop rule so you don't loop all night.
Pass 1: Blank scan (no posting)
Upload your file with the job description field empty. Note every formatting and section-order flag. If either bucket is red, stop. Do not paste the posting yet. A keyword gap on a scrambled upload often disappears once layout fixes because terms were trapped in a sidebar the parser skipped.
Before: Blank scan flags "unreadable table" and lists Python under formatting while your title sits in a right column.
After: Blank scan shows no formatting flags. Python still missing because you haven't pasted the posting yet. That's expected.
Pass 2: Paste test
Open the upload file, select all text, paste into Notepad or a plain text editor. Read order should be contact, summary if you use one, current job title, Month Year dates, bullets, then older roles. Skills and Education belong after Experience unless you're a new grad with thin work history.
Before: Paste test dumps Skills above Experience because a sidebar read first.
After: Paste test reads contact, summary, "Senior Analyst, Acme Corp, March 2022 to Present," then bullets in order.
Pass 3: Layout and header repair
Rebuild as a single-column DOCX when the portal allows it, or a text-based PDF exported from Word. Use plain headers: Summary, Experience, Education, Skills. Put phone and email on separate lines at the top with no icons. Every role needs Month Year start and end dates. Remove tables used only for spacing.
If the posting accepts only PDF, export from Word after you strip columns, not from Canva or a template site with icon skill bars. A designed PDF can look perfect on screen and still flatten bullets into the wrong employer block on import. Save the boring export as the file you'll checker-test and upload.
Re-run the blank scan. Pass 3 is done when formatting and section-order warnings clear. If flags remain, you haven't fixed the layer the parser complained about. Don't move to keywords yet.
Pass 4: Posting paste and keyword gaps
Paste the full job description into the checker. Highlight three must-have terms from the req: tools, certifications, or scope words repeated in the posting. Place them inside Experience bullets under the employer where you used them, not only in a Skills row.
Before: Gap list shows "stakeholder management" missing though you ran exec readouts for two years.
After: Bullet two under current role opens with "Stakeholder management for six product pods, weekly exec readouts to VP level."
For how matchers weight overlap once fields are clean, read how ATS matches resumes to job descriptions .
Pass 5: Bullet one under current role
Recruiters ctrl-f the current block first. Bullet one should open with scope or a metric in the first eight words. Example for an ops role: "Owned vendor onboarding for 14 SaaS tools, cutting ticket backlog 22% in Q2." Mirror one must-have term from Pass 4 in that opening line when it fits honestly.
For career changers, bullet one under the most recent relevant role matters more than a keyword-rich summary. If your current title doesn't match the req, bullet one should still show transferable scope: tools, team size, or budget you controlled, tied to the employer dates above it.
Re-run the checker with the posting still pasted. Stop when formatting stays clear and gap flags shrink to nice-to-have terms you don't actually have. Chasing every synonym on a clean parse is how Skills footers get stuffed.
Copy-paste: five-pass checker workflow
{`ATS checker passes (run in order):
[ ] Pass 1: Blank scan. Note formatting + section-order flags only
[ ] Pass 2: Paste test. Contact, Experience, dates, bullets, Skills
[ ] Pass 3: Rebuild single column; re-scan until layout flags clear
[ ] Pass 4: Paste posting. Mirror 3 must-haves in Experience bullets
[ ] Pass 5: Rewrite bullet one. Scope or metric in first eight words
[ ] Final scan on the exact file you'll upload tonight`}
Wrong-layer fixes that burn an hour
Starting with keywords on pass one. Synonym swaps on a two-column file don't move terms into Experience text the matcher reads. Fix paste order, then tailor bullets.
Checking a different file than you'll upload. A clean scan on Monday's Word draft doesn't help if Friday's PDF still has icon skill bars. Always recheck the export in your hand when you click submit.
Chasing 100% after parser health is clean. Diminishing returns show up as invented titles and keyword stuffing. Stop when contact info, dates, and three must-haves land in bullets you'd defend on a phone screen.
I've screened stacks of these in Workday and Greenhouse, and the candidates who rerun a checker ten times without a paste test usually still have Skills floating above Experience while they tweak synonyms nobody will read.
Ignoring blank-scan formatting because the match bar looked fine. A 78% score with a table warning means overlap on broken extraction. Fix layout before you trust any percentage.
Editing the summary instead of bullet one. Summaries parse, but matchers and recruiters weight the current job block heavier. A keyword-rich summary won't rescue a thin bullet one under your latest employer.
Recheck the export you'll upload tonight
Run all five passes on the file you plan to submit, not a template you mean to rebuild later. Rename the export with today's date after Pass 3 so you don't grab an old version from Downloads.
Run a free ATS check blank first, then with the posting pasted after layout clears. Read categories in order: formatting, section order, keyword gaps.
When gaps persist on a clean parse, score your job match on the same posting to see which must-have terms still sit outside Experience bullets.
This won't fix applying to roles where you lack core requirements. It stops a qualified file from dying in the parser because you optimized keywords before the upload could read your current title.
Stop when parser flags clear, not at 100%
The fastest way to optimize resume with ATS checker output is fixed order: blank scan, paste test, layout, posting keywords, bullet one. Fix formatting before synonyms. Re-run on the export you'll actually upload.
Open tonight's posting, work the five-pass checklist, and check your resume for free on that same file. That's how you stop treating a health report like a rejection letter.
Read more
Frequently asked questions
Run a blank scan first with no job description pasted. Formatting and section-order warnings on a blank scan mean layout problems, not missing keywords. Paste the posting only after the paste test reads contact, Experience, and dates in order. Otherwise you chase synonym swaps while columns still scramble your current title.
Three passes is enough for most files: blank scan, scan with posting after layout fixes, final scan on the export you'll upload. More runs without changing the file usually mean you're tweaking wording instead of fixing parser flags. Stop when formatting clears and three must-have terms sit inside Experience bullets.
No. A higher score after a clean parse means more posting overlap in extracted text. It does not predict interviews. A file can parse cleanly at 72% and outrank a stuffed 95% file where keywords landed in a Skills footer the matcher weights lightly. Fix readability first, then mirror must-haves in bullet one.
The exact PDF or DOCX you'll submit to the portal tonight, not an older Word draft or a designed Canva export you plan to fix later. Rename the file with the date you rebuilt layout so you don't accidentally recheck a broken version from Downloads.
