Why your CV is being rejected by ATS systems

A CV that reads cleanly to a human eye can still get filtered out by an applicant tracking system before any human sees it. The filtering is not arbitrary, but it is invisible, and the patterns that trip it up are not the ones most candidates worry about.

This guide walks through the five most common reasons CVs are rejected by ATS systems, and the simple fixes that get you through.

The header that the ATS cannot read

The most common rejection happens before the parser even reaches the body of the CV. A name and contact block built in a text box, an image, or a multi-column header is invisible to most ATS engines. The parser sees a blank space where the candidate's name should be, and the record gets created without a name to match.

The fix: place your name, phone, email, and city as plain text at the top of the document. No tables. No images. No two-column layouts in the header.

Section headings the parser does not recognise

ATS systems look for specific section labels to organise the document into structured fields. Common labels: Experience, Work Experience, Education, Skills, Certifications, Summary.

Creative variations cause problems. "My Story" instead of Summary. "What I Have Built" instead of Experience. The system fails to map the section to its expected field, and the content does not surface in the recruiter's filtered view.

The fix: use the standard labels. The creativity belongs in the content, not the section names.

Tables and multi-column layouts in the body

A CV that uses tables for structure or splits the page into a two-column layout often parses as a single column of jumbled text. The achievement that read cleanly in your design tool now appears half a paragraph away from the role it belongs to.

The fix: keep the body in single-column flowing text. Use bullet points and indentation, not tables and columns, to organise the content.

Missing keywords from the job description

Most ATS systems score CVs against the job description using keyword matching. A senior CV that uses elegant phrasing throughout but never repeats the actual words in the posting will score lower than a less polished CV that mirrors the language.

The fix: read the job description carefully. Identify the five to ten phrases that recur. Make sure they appear in your CV verbatim, in the contexts where they belong. Not stuffed into a skills list. Used naturally inside achievement statements.

File format problems

PDFs are usually safe, but a PDF exported from a design tool with embedded text in vector outlines is unreadable to most ATS engines. Word documents with embedded fonts, scanned images, or password protection have the same problem.

The fix: export your PDF as standard text-based PDF. If you are unsure, open the file in a basic PDF reader and try to copy a paragraph of text. If the copied text reads correctly, the ATS can read it too.

What an ATS-friendly CV does not have to give up

The five fixes above do not require giving up on design. A clean, well-typeset, single-column CV with standard section labels and ATS-readable text can still look like a finished document, not a stripped-down template.

The discipline is in the layout choices, not the visual quality. The CVs we write hold to ATS-friendly structure and earn the design points back through typography, spacing, and the content itself.

If your CV has been getting filtered without explanation, walk through the five points above. The fix is usually small, and the difference in callback rate is large.