Resume Could Not Be Parsed: What It Means and How to Fix It

When you upload your resume to an ATS (Applicant Tracking System) like Workday, Greenhouse, Lever, or iCIMS, the system attempts to extract structured information from your file — your name, contact details, work history, education, and skills. This process is called parsing.

Parsing fails when the ATS can't interpret your file's structure. The most common causes:

1. Complex formatting. Tables, columns, text boxes, headers, footers, and graphics confuse ATS parsers. What looks clean to a human's eye is often unreadable to a parser that's trying to extract sequential text.

2. Wrong file format. Most ATS systems strongly prefer .docx or a standard (not image-based) PDF. Files saved as .pages, .odt, or as a scanned image PDF (where the text is actually a picture, not text) will fail to parse.

3. Infographic-style resumes. If your resume uses skill bars, icons, or decorative elements from Canva or similar tools, the ATS may not be able to extract any text from those sections.

4. Non-standard section headings. Some ATS systems look for specific labels like "Work Experience," "Education," and "Skills." Creative headings like "My Journey" or "What I Know" may confuse the parser.

1. Convert to a single-column format. Remove all tables and columns. Use plain left-aligned text for all sections.
2. Save as .docx or a clean PDF. If saving as PDF, use "Save as PDF" from Word or Google Docs — never scan a physical document. The resulting file should be text-selectable.
3. Move content out of headers and footers. ATS parsers often skip header and footer regions entirely. Put your name and contact information in the main body of the document.
4. Use standard section headings. Rename sections to "Work Experience," "Education," "Skills," "Certifications." Boring, but parser-friendly.
5. Remove graphics and decorative elements. Skill bars, profile photos, and icons should be removed entirely.

After making these changes, test your resume by using LoopCV's free AI CV Checker — it will confirm whether your resume is ATS-parseable before you apply.

Different ATS platforms have different parser tolerances. Here's what to know about the most common ones:

Workday — One of the strictest parsers. Workday's parser struggles significantly with multi-column layouts, text boxes, and PDFs created from design tools (Canva, Figma). Stick to .docx saved from Word or a single-column PDF exported from Word or Google Docs. Workday also often fails to parse content inside tables — even simple two-column tables for "Skills" sections.

iCIMS — Similarly strict. iCIMS has a known issue with PDFs that have unusual encoding or compression. If you're applying through iCIMS and your resume isn't parsing, try converting to .docx first, then re-uploading.

Greenhouse — More forgiving than Workday, but multi-column layouts still cause problems. The Greenhouse parser handles standard PDF exports well. The main issue is headers/footers — keep your name and contact info in the document body, not in a header.

Taleo (Oracle) — An older parser that is one of the least forgiving. Taleo struggles with Unicode characters, special symbols, and any layout beyond a basic single-column format. When applying to companies using Taleo, save your resume as a plain .docx without any special characters.

Lever — Generally lenient. Lever's parser is more modern and handles standard PDF and .docx formats well. Complex design elements (icons, charts) still cause issues.

SmartRecruiters — Among the most lenient parsers. Handles most PDF and .docx formats without issue, but still rejects image-based PDFs.

BambooHR — Simple parser designed for SMBs. Handles standard formats fine; fails on image PDFs and heavily formatted files.

Universal safe format: single-column, .docx exported from Word, no tables or text boxes, no headers/footers with content, no images or graphics. This format will parse in every ATS without exception.