Resume parsing errors: how to avoid them

How ATS parsing works

An ATS parser converts your resume file into structured data: name, contact details, each job title, employer, date range, and a list of skills. It does this by scanning the raw text layer of your document, not the visual layout. If the text layer is missing, scrambled, or wrapped in formatting the parser does not recognise, the data it extracts will be wrong.

Recruiters often never see a parsing failure directly. They just run a search for a skill or a job title, and your record does not appear because the field is blank or garbled. You are screened out before anyone reads a word.

File format mistakes that cause failures

The safest file format in 2026 is a plain .docx or a text-based PDF. Both are widely supported across Greenhouse, Lever, Workday, iCIMS, and SmartRecruiters. Problems arise when you use formats outside this range.

• Image-based PDFs: if you export from Canva or save a scanned copy, the file contains no text layer. The parser reads a blank page.
• Password-protected PDFs: encryption blocks the parser from accessing the content.
• .pages files: Apple Pages documents are not reliably parsed outside macOS environments. Always export to .docx or PDF before uploading.
• Google Docs shared links: some portals accept a link but cannot parse it. Download as .docx first.
• Heavily compressed PDFs: some compression settings strip the text layer. Open the file in a browser and try selecting text to confirm it is there.

Layout and design choices that break parsing

Visual design elements that look professional in print are among the most common causes of parsing failures. The parser reads text in a linear stream, usually left to right and top to bottom. Anything that interrupts that stream causes errors.

• Tables and text boxes: content inside a table cell or a Word text box is often skipped entirely or read out of order.
• Multi-column layouts: a two-column resume may be read left column top to bottom, then right column top to bottom, mixing job titles with unrelated skills.
• Headers and footers: contact details placed in a Word header or footer are frequently missed. Put your name, email, phone, and LinkedIn URL in the main body.
• Graphics, icons, and logos: skill bars, profile photos, and decorative icons add no text data and can interrupt the text stream around them.
• Unusual fonts and special characters: some parsers replace unsupported characters with question marks or drop the surrounding word. Stick to Arial, Calibri, Georgia, or Times New Roman.
• Horizontal lines as section dividers: a simple line is usually fine, but lines created with repeated special characters such as tildes or asterisks can confuse parsers.

Content and structure errors that cause misreads

Even a plain text resume can be misread if the content structure does not match what the parser expects. Parsers are trained on millions of resumes and look for recognisable patterns.

• Non-standard date formats: write dates as Month YYYY, for example March 2023 or Mar 2023. Formats like 03/23 or Q1 2023 are misread by some systems.
• Missing section labels: if you rename Experience to Career History or Skills to Core Competencies, some parsers will not categorise the content correctly. Standard labels are safer.
• Job title buried after the employer name: most parsers expect Job Title then Employer or Employer then Job Title on the same line. Putting the title on a second line can cause it to be read as a description.
• Abbreviations without the full term: write the full phrase at least once, for example Search Engine Optimisation (SEO), so keyword searches on either form return your record.
• Unexplained gaps shown as a single block: a gap with no label can cause the parser to merge two separate roles into one date range.

A quick test you can run before you apply

You do not need specialist software to catch most parsing errors. This five-step test takes about ten minutes and works for any resume.

1. Open your resume file and select all text with Ctrl+A or Cmd+A, then paste it into a plain text editor such as Notepad on Windows or TextEdit in plain text mode on Mac.
2. Read through the pasted text from top to bottom. Check that your name appears first, followed by contact details, then each role in the correct order with dates intact.
3. Look for garbled characters, missing sections, or content that appears in the wrong place. A two-column layout will show this clearly: skills will appear mid-sentence inside a job description.
4. Search the plain text for three skills you consider essential for your target role. If they are missing or misspelled, a keyword search in the ATS will not find you.
5. Upload the file to a free parser such as Resume Worded or Jobscan's resume checker and compare the extracted fields against your original. Pay attention to the job title and date fields.

How Break-In Bad handles parsing before you apply

When you enhance or build a resume through Break-In Bad, Omar checks every line against what you confirmed in the conversation and keeps your original on file. The output is a clean, text-based document structured to pass standard ATS parsers on Greenhouse, Lever, and Workday, the same platforms the agent uses to submit applications. If you already have a resume you are happy with, running it through the plain text test above is still the fastest way to catch problems before any application goes out.

Formatting rules to follow every time

Applying these rules consistently means you will rarely need to debug a parsing failure again.

• Use a single-column layout with standard section headings.
• Save as .docx or export as a text-based PDF and verify the text layer is selectable.
• Put all contact information in the main body, not in a header or footer.
• Write dates as Mon YYYY or Month YYYY throughout.
• Avoid tables, text boxes, graphics, and multi-column designs.
• Spell out abbreviations at least once per section.
• Use a common font at 10 to 12 points for body text.