11 min read
You've run spell-check twice. Your friend said the file looks clean. You still get silence after upload, and the portal preview shows your dates glued to the wrong employer. That's not a typo problem. That's a parser problem most proofreading advice never mentions.
A resume proofreading checklist for US job applications has to catch what recruiters see in ATS preview: smart quotes in company names, broken date ranges, table cells read out of order, and symbols that strip to blank fields. Check your resume for free with the posting pasted in and you'll often find zero spelling errors while Experience imports empty in Workday.
Below is a teardown pass, not a grammar lecture. You'll see the bar your file is judged against, before/after pairs across roles, what broken versions share, and a copy-paste checklist you can run in twenty minutes tonight. Job searching is exhausting. This page is about fixing what the upload box actually reads.
Quick Wins
- Paste PDF text into Notepad and read employers and dates top to bottom.
- Replace smart quotes and curly apostrophes with straight ASCII characters.
- Standardize every date as Month Year to Month Year on its own line.
- Screenshot portal preview fields before final submit when the employer shows them.
What a resume proofreading checklist for US job applications must catch
Generic advice says read aloud and fix commas. US corporate portals care whether parsers can build a work history object. Recruiters open profiles where half the experience block is blank even though the PDF looked polished. The failure is almost always invisible to spell-check.
The bar your file is judged against: every employer name, job title, and date range imports in order; bullets stay attached to the right role; contact info sits in the body, not a header that strips; and must-have keywords from the posting appear in plain text a machine can search.
Typos matter when a human reads quickly. Parser breaks matter when nobody reads at all. A misspelled skill might survive. A date range trapped in a table cell often becomes Present attached to your internship while your current role shows no end date.
Smart quotes are a quiet killer. Word converts O'Brien or "client-facing" into curly characters. Some PDF exports turn them into boxes or split tokens. Parsers then store half a company name or drop the line entirely.
I've screened files where grammar was perfect and Workday showed three employers merged into one block because the template used a two-column date layout. The candidate proofread for typos for an hour. Two minutes of Notepad paste would have caught it.
Read resume turns into gibberish after upload: causes and fix when preview text scrambles completely. This checklist targets the subtle breaks that still look fine on screen.
Before/after pairs: parser proofreading across roles
Pair 1: Operations analyst (broken dates in table)
Before: Job title in left column, 01/2021 to 03/2024 in right column inside a Word table. Notepad paste shows Acme Corp March 2024 Senior Analyst January 2021 out of order.
After: Senior Operations Analyst, Acme Corp, January 2021 to March 2024, then bullets below on plain lines. Paste order matches read order.
Pair 2: Registered nurse (smart apostrophe in employer)
Before: St. Mary's Medical Center with curly apostrophe from auto-format. Portal preview shows St. followed by blank employer field.
After: St. Marys Medical Center or St. Mary's with straight apostrophe retyped in plain text. Employer imports as one string.
Pair 3: Software engineer (symbol bullets)
Before: Bullets start with → or ✓ copied from a template. Notepad shows empty lines or question marks before each achievement.
After: Standard hyphen bullets. Built React checkout flow reducing cart abandon 12% in Q3. Plain ASCII only.
Pair 4: Project manager (mixed date styles)
Before: First role Jan 2020 to Present, second role 2017 to 2019, third role 06/2014 to 12/2016. Parser attaches Present to the oldest job.
After: Every role uses January 2020 to Present, January 2017 to December 2019, June 2014 to December 2016. One style, one line each.
Pair 5: Customer support lead (contact in header/footer)
Before: Phone and email in a footer bar on every page. Preview imports zero contact fields.
After: Name, city, phone, email, linkedin.com/in/handle as plain body lines under the headline. Footer removed.
Pair 6: Marketing coordinator (skills in sidebar)
Before: Two-column Canva layout with Skills in a colored sidebar. Experience paragraphs merge with Education in paste test.
After: Single-column export, 11-point Calibri, Skills as one comma line after Experience. Section headers spelled Experience and Education exactly.
Copy-paste US proofreading pass (parser first)
"Notepad paste: employers in order, dates intact, no blank squares. Straight quotes only. Month Year dates consistent. Contact in body. Single column. Section headers standard. Portal preview screenshot saved. Must-haves ctrl-f from posting. Filename: Company-Role-2026-09.pdf."
Run parser checks before grammar polish. Fixing a comma while dates still import wrong wastes another upload slot.
Edge case: career gap with honest dates
Do not hide gaps with Present on an old role. Parsers and humans both flag overlapping Present lines. List end dates honestly. A gap with clean fields beats merged employers that look like fabrication in preview.
Before: Left consulting role as Present while unemployed 2024 to 2025.
After: Independent Consultant, January 2022 to June 2024, then gap, then new role with accurate start month.
Edge case: international company names with accents
Accents sometimes survive, sometimes strip. If preview shows mojibake, retype the employer in ASCII or add the ASCII form in parentheses once. Do not leave a character that becomes a blank employer line.
Edge case: PDF exported from design tool
Canva and similar tools often produce image-heavy PDFs. Notepad paste returns nothing useful. Rebuild in Word or Google Docs plain, then export text-based PDF. Proofreading the pretty file is pointless if there is no text layer.
Pair 7: Financial analyst (numeric dates only)
Before: 2019, 2020, 2021, 2022 as standalone lines with no month, company name on a separate page break.
After: Financial Analyst, Horizon Capital, January 2019 to December 2022, with month anchors on every role so tenure filters compute correctly.
Pair 8: Teacher (bullet numbering auto-format)
Before: Word auto-numbering restarts at 1 for each school role. Paste test shows 1. 1. 1. before bullets with no employer between.
After: Manual hyphen bullets under each school name. Fifth Grade Teacher, Lincoln Elementary, August 2020 to June 2024, then plain bullets.
Twenty-minute proofreading order
Minutes one to five: export PDF and Notepad paste. Read employers top to bottom. Flag any line where dates appear before company names.
Minutes six to ten: search for curly quotes and replace. Search for special bullets and replace with hyphens. Confirm phone uses digits, not letters.
Minutes eleven to fifteen: open portal preview if available from a prior application. Compare each job field to your source file. Screenshot mismatches.
Minutes sixteen to twenty: ctrl-f three must-have skills from the posting inside pasted plain text. If they only appear in a sidebar that stripped, move them into bullets.
Read how to tailor a resume to a job description after parser proofreading passes. Keywords only help when fields exist to hold them.
What weak proofreading passes still miss
Proofreading only in Word print view. Print view hides whether text layers export. Always paste into Notepad or TextEdit plain mode.
Trusting green spell-check lines. Grammar tools ignore table order, smart quotes, and header/footer contact bars.
Skipping portal preview. When Taleo or Workday shows parsed fields, that preview is the proofreading surface that matters most.
Fixing typos while leaving icon skill rows. Star ratings and progress bars strip to blanks. Plain comma-separated Skills survive.
Using en dash and hyphen interchangeably in dates. Pick Month Year to Month Year or Month Year – Month Year and stick to one pattern. Mixed punctuation splits date tokens.
Proofreading once for all employers. Greenhouse and Taleo previews differ. Keep a plain master and spot-check preview on the portal you apply through this week.
Relying on a second pair of eyes for grammar only. Friends catch awkward sentences. They rarely run Notepad paste or read ATS preview unless you ask specifically for parser order.
Leaving LinkedIn URL as a button shape. Button links in PDF often strip. Write linkedin.com/in/yourhandle as plain text on its own line.
See resume upload mistakes that instantly disqualify you for file-type and mobile-upload failures beyond proofreading.
Verify parser proofreading before upload
After the checklist pass, upload the same PDF and posting to HireFlow's free ATS resume checker. You're confirming parsed employers and dates match what you see in Notepad, not chasing a perfect grammar score.
Use job match score on the corrected file when must-haves still miss after fields import cleanly. Parser fixes come first; keyword gaps come second.
Keep the checker screenshot beside your plain master PDF. When a similar req opens next month, you'll know which employer lines already parsed clean without repeating the full teardown from scratch.
Parser proofreading before grammar polish
A resume proofreading checklist for US job applications that stops at spell-check leaves parser breaks on the table. Run Notepad paste, kill smart quotes, standardize Month Year dates, and read ATS preview when you get it. Then worry about commas.
Open your last upload preview tonight. If employers or dates look wrong, fix layout before you tailor keywords. Run the free resume check on the corrected export before you apply again.
This won't fix applying to roles you're not qualified for. It does stop a qualified file from dying because Present landed on the wrong job title in preview.
When the req asks for a letter, generate a cover letter in plain text with the same dates and employer names you verified in preview. Mismatched dates between letter and resume trigger manual rejections even when parsing passes.
Save a folder called parser-clean with the date in each filename. Next week you'll reach for the version that already passed Notepad and preview, not the designed export from month one of your search.
Read more
Frequently asked questions
Spell-check catches typos. It does not catch smart quotes, en-dashes pasted as symbols, table layouts that scramble employers, or Month Year ranges that import as one blob. Run a plain-text paste test and read the portal preview when the employer shows parsed fields. Those two steps catch parser breaks spell-check never sees.
Use Month Year on one line per role: January 2022 to Present or March 2019 to June 2023. Avoid MM/YYYY in one cell and Present in another column. Avoid year-only ranges when the posting asks for full tenure. Consistent Month Year left-aligned in the body survives Workday, Greenhouse, and Taleo imports better than mixed numeric styles.
Word and Google Docs convert straight apostrophes to curly quotes. PDF text layers sometimes export them as odd characters. Parsers read those as garbage in company names or bullet lists. Replace curly quotes with straight quotes before export, or retype employer names in plain ASCII. A name like O'Brien with a smart apostrophe can split a field in preview.
Proofread both when you can. Your PDF may look perfect while the preview shows blank experience or dates attached to the wrong employer. Screenshot the preview, fix the source file, and reupload once. The preview is what recruiters often open first in legacy systems.
Twenty minutes for a plain single-column file: five for Notepad paste order, five for date and employer consistency, five for smart quotes and symbols, five for keyword spot-check against the posting. Add ten if you use tables or a designed template. Parser proofreading is faster than rewriting bullets after silent rejections.