What an ATS actually does with your resume, and what it does not

Before a recruiter ever opens your resume, software usually reads it first. An applicant tracking system, or ATS, pulls the text out of your file and sorts it into fields like contact details, work history, education, and skills. This step is called parsing, and it happens whether your resume looks perfect on screen or not.

Parsing is where most of the damage happens. If the software cannot correctly identify where one section ends and another begins, it can misfile your experience, drop your contact details, or jumble your work history out of order, all before anyone has read a single word of what you actually did.

Once your resume is parsed, most systems rank it against the job requirements a recruiter has set up. This ranking is relative. There is no universal passing score, your resume is simply compared to everyone else who applied for that role.

Most parsers read a document the way we read a book, left to right, top to bottom, in one continuous stream. A two-column layout or a table breaks that assumption. The software often reads straight across the page instead of down one column at a time, which mixes unrelated lines together into something unreadable.

The fix: use a single-column layout for your entire resume. If you want a clean visual layout, use simple line breaks and bullet points instead of a table.

Many ATS platforms only scan the main body of a document. Anything placed in a header, footer, or floating text box, like your name and phone number inside a designed header, can be invisible to the parser. Jobscan's own research on this found that roughly a quarter of ATS platforms fail to pick up contact information stored this way.

The fix: put your name, phone number, email, and location in the main body of the document, not in a header or footer.

The software looks for familiar words to classify your content, things like Experience, Education, and Skills. A creative heading like My Journey or Where I Have Been might read beautifully to a person, but it gives the parser nothing to match, so that section can be skipped or filed incorrectly.

The fix: stick to plain, expected headings. Save the personality for your summary and your interview.

A logo, a headshot, or a set of star ratings for your skills might look sharp in a PDF, but none of it is text. Parsers cannot read pictures, so any information locked inside an image is simply gone as far as the system is concerned.

The fix: describe your skill level in words, for example Advanced or 5+ years, instead of graphics, and keep photos and icons out of the document entirely for roles based in the US and most other markets.

The PDF versus Word debate has cooled off. Most modern systems handle both reasonably well, as long as the file has real, selectable text. What still causes real damage is a scanned or image-based PDF, made by photographing or scanning a printed resume. There is no text layer at all for the software to extract, so the whole document can come through blank.

The fix: if a job posting does not specify a format, a text-based .docx is the safest universal choice. If you use PDF, export it directly from Word or Google Docs, never from a scanned image.

Different ATS platforms have different known weak points. This is not a reason to guess which system a company uses, it is a reason to avoid the riskiest formatting choices across the board.

Parsing behavior changes as vendors update their software, so treat this as a general risk map, not a guarantee for any single application.

Myth: you need a perfect ATS match score to get noticed. There is no universal passing score. Most systems rank you relative to other applicants for that specific role, so a well-tailored resume with a solid, honest keyword match will consistently beat an artificially inflated one.

Myth: 75% of resumes are automatically rejected by ATS before a human ever sees them. This is one of the most repeated numbers in job search advice, and it does not hold up. Investigations have traced it back to a 2012 marketing claim from a small resume company that closed down the following year, with no published methodology behind it. More recent surveys of ATS software suggest the large majority of applications are still reviewed by a person, and most platforms do not auto-reject candidates purely for formatting or missing keywords.

Myth: stuffing keywords in white text tricks the system. This trick stopped working years ago. Modern parsers can detect hidden text, and getting caught can flag your application rather than help it.

Myth: a paid ATS-friendly template guarantees you will pass. Parsability depends mostly on the underlying file structure, not the price tag. A plain, well-organized document you build yourself with a single column and standard headings performs just as well as most premium templates.

The origin of the most repeated of these claims is traced in full in where the 75% number came from. If you want to know what an employer has to tell you when software screens your application, that is in AI in hiring: what you are entitled to know.

We did not run our own parsing test, and this guide does not pretend to. It reads published research and links every figure to where it came from, which is listed in full at the end of this page.

Two of those figures are weaker than they look, and it would be dishonest to quote them without saying so. The 7.4 second scan comes from eye tracking 30 recruiters, which is a small sample and a vendor study. The 88% is employers describing what they believe their own software does, not a measured rejection rate. We have kept both because they are the best available, and labelled both because they are not conclusive.

One figure we removed. An earlier version of this page claimed that 25% of ATS platforms miss contact details placed in a header or footer. We went looking for the study behind it and could not find one, so it is gone. The underlying advice stands on its own: parsers read the document body, and a header is not reliably part of it.

Our own resume score is an AI estimate of how well a resume is likely to parse and match. It is not a test against any employer's ATS. Nobody outside Workday, Greenhouse or Taleo can run one, and anyone who says they do is describing something they cannot do.

The filter that genuinely ends an application on its own is not parsing at all: see knockout questions.