What "ATS Parsing" Actually Means (and What It Doesn't)
If you've ever sent a well-crafted resume into a job portal and heard nothing back, a parsing failure may be the culprit — not your qualifications. This post explains exactly how ATS parses resume files, field by field, so you can fix structural problems before they silently disqualify your application.
An Applicant Tracking System (ATS) doesn't read your resume the way a recruiter does. It parses it — converting your file into discrete data fields: name, phone, email, job titles, employers, dates, skills, education. Each field gets extracted, labeled, and indexed in a database. Only after that extraction does a human typically see anything.
Here's what most candidates miss: a parse failure rarely produces an error message. The system doesn't bounce your application back with a warning. Instead, it silently corrupts your data. Your phone number ends up in the "name" field. Your skills section simply doesn't exist in the database. A recruiter searching for "project manager" gets zero results — even though those words appear on your resume — because the parser never extracted them correctly.
The sections below walk through exactly where resume parsing breaks down, field by field, and what to do about it.
The Contact Header: Why the First 10 Lines Are the Riskiest
Your contact block is the first data an ATS tries to extract, which makes it the first place things go wrong.
The document header trap
Most word processors let you place content in a document header — the region that repeats at the top of every printed page. It looks identical to regular text on screen, but under the hood it lives in a separate XML zone from the main body content. Many ATS parsers read only the main content stream and skip document headers entirely.
If you placed your name, phone number, or email inside the actual file-level header element — not just visually at the top of the page, but in Word's "Insert Header" region — those fields may never reach the ATS database. The recruiter sees a blank "name" record.
Fix: Copy your contact information out of the document header and paste it directly into the body of the document, above your first section heading. It will look identical on screen; the difference is structural, not visual.
Two smaller failures in the contact block
- LinkedIn URLs with tracking parameters — a URL containing a
?trk=suffix or referral tag can cause the parser to read it as a broken string. - Line-wrapped email addresses — if your email address is long enough to wrap onto a second line in the PDF, some parsers extract two separate fragments instead of one valid address.
Quick test: Copy everything in your resume and paste it into Notepad (Windows) or TextEdit in plain-text mode (Mac). If your name, phone number, or email doesn't appear at the very top in clean, readable form, something is wrong with where that information lives.
Tables and Columns: Clean on Screen, Chaos in the Parser
Two-column resume layouts look organized and pack more content onto one page. They are also one of the most reliable ways to break an ATS.
Why columns break the content stream
Most parsers read content in a single left-to-right, top-to-bottom stream — exactly the order content appears in the underlying file. A table or multi-column layout splits that stream. The parser must guess how to reconstruct the reading order, and it usually guesses wrong.
Concrete example: Imagine a two-column resume where the left column holds contact information and the right column holds a "Core Skills" list. A parser reading linearly might produce:
Jane Smith | jane@email.com | 555-0100 Project Manager Stakeholder Communication Budget Forecasting Senior Product Designer...
The job title "Project Manager" now appears immediately after the phone number, with no employer or date attached. The ATS has no way to know whether "Project Manager" is a current role, a past role, or a skill.
Specific field failures in table layouts
- Skills grids: Skills listed in a 3×4 table often lose their labels. The parser extracts cell content but not the relationships between cells.
- Detached dates: When job titles sit in a left column and employment dates sit in a right column, the dates can separate from the titles they belong to. The ATS may calculate tenure incorrectly or show an employment gap that doesn't exist.
Fix: Use a single-column layout for any resume submitted through an online portal or ATS. Save the visually polished two-column version for PDF portfolios or direct human delivery.
One important note: switching to .docx format helps, but it isn't a complete solution. A poorly structured .docx with table-based columns fails in exactly the same way. File format is not a substitute for a clean, single-column structure.
Graphics, Icons, and Text Boxes: Invisible to the Machine
Modern resume templates — especially those downloaded from design sites — frequently use visual elements that look impressive and parse as nothing.
What the parser doesn't see
In both .docx and PDF formats, content placed inside a text box, shape, drawing canvas, or graphic is stored outside the main content stream. From the parser's perspective, those elements don't exist.
Common culprits:
- Skill bars — a horizontal bar graphic rating your Python proficiency at "4 out of 5." The label "Python" and the rating are both invisible to the ATS.
- Icon-based contact lines — a phone icon next to your number, or an envelope icon next to your email, where the icon is an image and the surrounding text is embedded in a text box.
- Employer logos — decorative company images contribute nothing and can interfere with extraction.
The practical consequence is significant: a candidate who built their entire skills section inside a styled text box appears to the ATS as a person with no listed skills. Keyword searches for "SQL," "Python," or any other skill return zero results.
Fix for an ATS-ready resume format:
- Remove all text boxes. Cut the content, delete the box, and paste the text directly into the document body.
- Replace icon-based contact lines with plain text — just the number, just the email address.
- Delete all decorative graphics. They add visual weight and parsing risk, neither of which helps you.
A clean, text-only ATS resume format isn't a downgrade. It's the version the machine can actually read.
Section Headings: How the ATS Knows Where Work History Ends and Skills Begin
An ATS categorizes content by recognizing section labels. "Work Experience" maps to an employment history field. "Education" maps to a degree extraction routine. "Skills" triggers a keyword extraction pass. These mappings are built into the parser's logic.
When creative headings go wrong
Rename those sections and the mapping breaks.
| What you wrote | What the ATS expects | Likely outcome |
|---|---|---|
| "Where I've Been" | "Work Experience" | Section miscategorized or ignored |
| "My Toolkit" | "Skills" | Keywords never extracted |
| "Academic Background" | "Education" | Degree fields left blank |
The parser either puts the content into the wrong category or skips it entirely. Neither outcome helps you.
Date format inconsistencies
Mixing date formats within the same resume is a quieter failure. If one job lists "Jan 2021 – Mar 2023," the next lists "01/2021 – 2023," and a third lists just "2020," the ATS tenure calculator may produce incorrect employment durations or flag gaps that don't exist.
Fix: Standardize every date to the same format. "Month YYYY" — for example, "March 2021" — works reliably across most systems. Apply it consistently to every role, degree, and certification.
Heading styling note: Bold, plain-text section headings (bolded body text, not styled heading elements) parse more reliably on older ATS platforms. When in doubt, keep it simple.
File Format and Encoding Edge Cases That Quietly Kill Your Application
PDF vs. .docx
PDF parsing quality varies significantly by ATS vendor. Some modern systems handle embedded-font PDFs well. Others extract a character soup — fragments of text in unpredictable order. When you don't know which system a company uses, .docx is the safer default.
One case where there's no debate: scanned PDFs. If your file is a photograph of a printed page — common when someone scans an old resume — the ATS extracts zero text. It's an image. The parse failure is total.
Special characters and encoding
Older parsers — and some current enterprise systems — handle non-standard characters poorly:
- Curly quotes (
"") instead of straight quotes (") - Em-dashes (
—) used as bullet points - Non-Latin characters in names can produce corrupted strings in the extracted record
Fix: Use standard hyphens (-) as bullet substitutes, straight quotes, and export your PDF using Word's "Save As PDF" or "Export" function rather than printing to PDF via a virtual printer.
File naming
Some ATS platforms use the uploaded filename as the record label in their database. A filename containing special characters (#, &, %) can trigger upload errors on certain systems. Keep it clean: FirstName_LastName_Resume.docx works universally.
How to Check Your Own Resume for Parse Failures Before You Apply
You don't need to guess whether your resume will parse correctly. Here are four practical checks you can run right now.
The plain-text test
Copy the entire content of your resume and paste it into a plain-text editor (Notepad on Windows, TextEdit in plain-text mode on Mac). Read through the output top to bottom. Every piece of content — contact info, job titles, employers, dates, skills, education — should appear in logical reading order with nothing scrambled or missing. If sections are out of order, merged, or blank, the structure needs fixing.
The copy-order test (for PDFs)
Open your PDF, select all text (Ctrl+A or Cmd+A), and paste into a plain-text editor. If your skills appear mid-sentence inside a job description, or your dates appear before the job titles they belong to, your columns are merging during extraction.
Use an ATS scoring tool
Running your resume through ATSEye shows exactly which fields parsed cleanly and which scored low — no guesswork. The scoring engine is deterministic, not an LLM estimate, so the output tells you specifically what needs fixing. After making changes, re-score to confirm the improvement is real.
Pre-submission checklist
Before you hit submit on any application, verify:
- Single-column layout throughout
- Contact info is in the document body, not the file-level header or footer
- Standard section labels: "Work Experience," "Skills," "Education"
- All dates in the same format (e.g., "Month YYYY")
- No text boxes, shapes, or graphics
- Skills and contact info are plain body text, not embedded in icons or images
- File is
.docxor a Word-exported PDF (not a scanned image) - Filename uses only letters, numbers, underscores, and hyphens
Parsing failures are silent and fixable. You don't need a professional designer or a complete resume overhaul. You need structure — clean, single-column, text-based, predictably labeled structure. Make those changes once, and every application you send afterward starts from a position where the machine can actually read what you wrote.
Written by
ATSEye Editorial Team
ATS & resume-scoring specialists
The ATSEye editorial team writes about applicant tracking systems, resume optimization, and hiring — grounded in how our deterministic, six-layer scoring engine actually parses and scores resumes.