How Resume Parsers Read Your Resume (And Why Yours Might Be Getting Mangled)

What Happens When You Submit a Resume

When you submit a resume to an ATS-enabled hiring system, the first thing that happens is not a human reading it - it is a parser converting your document into structured data fields.

The parser attempts to extract:

• Your name and contact information
• Your work history (company name, job title, start date, end date, responsibilities)
• Your education (institution, degree, graduation year)
• Your skills and competencies
• Any certifications, publications, or other sections

This structured data is then stored in the ATS database, searchable and rankable by recruiters. If the parser misreads your formatting and puts your job title in the company name field, or skips an entire section because it was inside a text box, that is how your information is permanently stored - and that is what the recruiter sees when they open your application.

Why Parsing Fails

Two-column and multi-column layouts

The most common parsing failure. Parsers read left-to-right, top-to-bottom. In a two-column layout, the parser often reads across both columns simultaneously, producing nonsensical combined text - for example, reading the left column's job title and the right column's education institution as a single merged field.

Text boxes

Content inside text boxes is often invisible to parsers. If your contact information, summary, or skills section is inside a text box, it may be entirely omitted from the parsed output.

Tables

Similar to text boxes - parsers typically read table content out of sequence or ignore it entirely. Skills sections presented in a three-column table are a common casualty.

Headers and footers

Content in the document header or footer (page numbers, your name repeated, contact details) is frequently skipped by parsers because it exists outside the main document body in the file's XML structure.

Graphics, icons, and images

Images are invisible to text parsers. Resumes with profile photos, icon-based skill ratings, or visual section dividers lose all the information embedded in those elements. Skill bars (a visual percentage representation of skill level) are parsed as zero content.

Unusual fonts and special characters

Parsers expect standard fonts. Unusual Unicode characters used as bullet points - arrows, stars, custom glyphs - sometimes parse as question marks or are dropped entirely, breaking the surrounding text.

Formatting Choices That Parse Reliably

How to Check If Your Resume Is Parsing Correctly

The fastest check: paste your resume text into a plain text editor (Notepad on Windows, TextEdit on Mac in plain text mode). If the text comes out garbled, with columns mixed together or sections missing, the parser will likely produce the same garbled output.

You can also run your resume through the free ATS checker, which simulates the parsing process and flags common formatting issues before you submit.

DOCX vs. PDF: Which Parses Better?

The honest answer is: it depends on the ATS. Most modern platforms handle both well - but older systems and budget ATS software parse DOCX more reliably than PDF. The exception is a clean, text-based PDF (not a scanned image PDF), which most modern ATS systems handle equivalently to DOCX.

The worst choice in any case is a PDF that was saved from a heavily designed template - especially those from Canva, Adobe InDesign, or graphic-design resume builders. These often export as image layers, not parseable text.

Run a repeatable check on the exported file

Open the ATS parser online, upload your final PDF, DOC or DOCX, and complete analysis. Run the focused text check, then open the recovered-text preview. Confirm that your contact details, recent job titles, dates and relevant skill phrases appear in a sensible order. The preview is limited to the text available to this site’s extraction workflow; it is not a simulation of the employer’s system.

Review the actual document visually too. Text checks do not inspect the original page geometry, and readable extracted text does not prove that every field will autofill correctly in a job portal. Follow the employer’s requested format and review any autofilled fields before submission. If you change the layout, export a new file and repeat the same checks, rather than checking only the editor preview.