7 min read
You're about to upload again and you don't trust the file. Fair. Most resumes look fine on screen and still import as scrambled text in Workday or Greenhouse.
Score tools are useful for keyword gaps. They won't always catch a two-column layout that dumps your skills above your name, or a phone number trapped in a header the parser skips.
Tonight's job: ten minutes, three manual checks, one upload-ready file. You'll know it's working when the paste test shows your name on line one and your current job title before your college degree.
Check your resume for free after the manual tests. Use the checker for keyword alignment once parsing is clean.
Work through the grouped checklists below in order. Parser problems first, keyword fit second.
Quick Wins
- Paste all resume text into Notepad. Name should be line one.
- Ctrl+F your phone number inside the PDF or DOCX. Zero hits means fix contact placement.
- Read headings top to bottom. Experience must come before Education on a standard US file.
What score tools miss
An ATS checker reads your file as stored text and compares it to a job description. That's valuable for keyword gaps. It doesn't always replay how Workday or Taleo orders that text when fields auto-fill on upload.
Parser failures hide in plain sight. I've screened hundreds of files where the keyword score looked fine but the paste test showed the skills block landing above the candidate's name.
The three checks below catch what scores skip: reading order, searchable contact data, and section labels the parser expects. Run them on the exact file you'll submit, not a prettier version you keep for email.
For a faster gut check, see how to tell if your resume is ATS-friendly in 60 seconds . This page goes deeper on section order and searchability before a high-stakes upload.
How to check if your resume is ATS-friendly: three manual tests
Block ten minutes. Open the posting you're applying to. Keep that window beside your resume file. Work through paste, search, and section order before you touch wording.
Checklist 1: the paste test
Open your upload-bound PDF or DOCX. Select all text. Paste into Notepad or TextEdit with no formatting. You're looking at the parser's view, not the designed view.
- Line one: Your full name, not a logo, icon, or blank row.
- Lines two to five: Email, phone, city/state on separate readable lines.
- Job blocks: Company, title, and dates stay together. No random skill words between roles.
- Bullets: Each bullet on its own line, in the order you wrote them.
- No gaps: No huge blank stretches where a sidebar used to sit.
Checklist 2: the search test
With the same file open, use Ctrl+F (or Cmd+F). Search for your phone number, your email domain, and one required skill from the posting. Each search should return at least one hit in the body text.
| Search term | Pass | Fail |
|---|---|---|
| Phone number | Found in main body text | Zero hits (often stuck in header/footer) |
| Email address | Full address searchable | Split across lines or inside an image |
| Posting keyword | Appears in summary, skills, or a bullet | Only inside a chart, icon, or text box |
| Current job title | Exact title string is findable | Title merged with company on one garbled line |
Checklist 3: section-order check
Read only the heading lines in your paste-test output. Standard US order is contact block, summary or profile, experience, education, skills. Creative labels and sidebars scramble this sequence. You're not picking the prettiest layout. You're confirming the parser reads your career story in the order a recruiter expects.
Flag any heading that isn't a word recruiters search for in their ATS filters. "Professional Synopsis" might sound sharp, but Experience and Education are what parsers map to database fields.
- Headings: Use Experience, Education, Skills. Skip "My Journey" or "Where I've Been."
- Experience first: For most roles, current job appears before your degree block.
- Skills placement: Skills section after experience is safer than a skill cloud above your name.
- Date format: Same Month Year pattern on every role (Jan 2022 to Mar 2024).
- Single column: No second column of text in the paste output.
Copy-paste block: what a passing paste test looks like
First 15 lines after paste (passing example)
Jordan Lee [email protected] | 555-018-4420 | Denver, CO linkedin.com/in/jordanlee SUMMARY Operations analyst with 4 years in Salesforce reporting and SQL dashboards. EXPERIENCE Operations Analyst, Northline Logistics, Jan 2022 to Present • Built weekly SLA dashboards in Looker, cutting manual reporting 6 hours per week • Owned Salesforce case routing rules for a 12-person support team Business Analyst, Clearpath Retail, Jun 2019 to Dec 2021 • Migrated inventory reports from Excel to SQL, improving stock accuracy
Before: Two-column Canva PDF. Paste test lists Python, Tableau, and SQL before the candidate's name.
After: Single-column Word export. Name on line one, skills section after experience, keywords still present in bullets.
Before: Phone number in a Word header. Search test returns zero hits in the body.
After: Phone on line two under the email. Search finds it, and Workday auto-fill populates the phone field.
Before: Section titled "Career Highlights" with jobs listed under "Academic Background" mixed in.
After: Standard Experience and Education headings. Section-order check reads top to bottom without jumping.
When a portal lets you preview extracted fields, run that as a fourth check. If employer names land in the education field, go back to the paste test and flatten tables before you apply elsewhere.
Save a screenshot of a passing paste test if you're tailoring multiple versions this week. When a new template sneaks in a text box, you'll spot the scrambled order immediately instead of guessing why applications went quiet again.
File name matters less than file content, but rename the upload to Firstname-Lastname-Role.pdf before you attach it. Recruiters searching their inbox thank you, and you won't accidentally send resume-final-v3 to a Greenhouse requisition.
Parser traps that pass a score
Chasing match percentage before layout. A 90% keyword score means nothing if your dates imported as one merged string. Paste first, keywords second.
Testing the wrong file. You designed a PDF for networking and uploaded a different DOCX to the portal. Run all three checks on the upload file only.
Icons and skill bars. They look modern in preview. Plain text shows blank space where proficiency should be. Replace bars with a simple Skills list or keyword bullets.
Headers and footers for contact info. Many parsers drop them. If search can't find your phone, move it into the body even when the template looks cleaner with a header.
Image-based PDFs. Select-all copies nothing useful. Re-export from Word or Google Docs with selectable text, then rerun the paste test.
Trusting a designed template without testing. Canva and similar tools export beautiful files that fail all three checks. Build your upload version in Word or Google Docs, run the tests, then keep the designed PDF for email introductions only.
See also why fancy layouts break parsing for sidebar and table failures that still earn green scores on keyword tools.
Verify before upload
Manual checks confirm the parser can read your file. Tools confirm you're pointing at the right posting language. Use both, in that order.
Run the free ATS checker on the same PDF or DOCX that passed the paste and search tests. Fix layout flags before you celebrate a match score.
Then score your job match against the live posting. You'll see which required terms still sit only in the skills list instead of a bullet where a recruiter expects proof.
If the portal also asks for a short note, generate a cover letter in the same plain formatting so both documents parse cleanly in one session.
Your 10-minute rule
If you wouldn't upload without proofreading a cover letter, don't upload without these three checks. Paste, search, section order. Two minutes each, one clean file.
- Paste test: name on line one, jobs in order, no sidebar junk.
- Search test: phone, email, and one posting keyword are findable.
- Section-order check: standard headings, experience before education.
A readable file won't guarantee an interview. It does stop a qualified background from dying before a human opens the profile. That's the bar worth ten minutes tonight.
Read more
Frequently asked questions
A checker can flag missing keywords and some layout risks, but it won't always show scrambled reading order or header-only contact info. Run the paste test and section-order check in this guide first. If plain text looks wrong, fix layout before you chase a match percentage.
Use whatever format the portal requests. For your own check, test both exports if you're unsure. Open the file, select all text, and paste into Notepad. If one format pastes cleanly and the other drops your phone number or shuffles sections, submit the clean one.
Run all three tests every time you tailor for a new posting or change layout. A single new text box or sidebar can break parsing on an otherwise fine file. Five minutes before upload beats a week of silence.
These checks only confirm the file is readable. They don't fix fit, timing, or competition. If parsing is clean and keywords sit in real bullets, shift to targeting, referrals, or a stronger top-third hook. The file isn't the only variable.