Applicant tracking systems are database software. They store applications, let a recruiter search them, and sometimes rank them. Most of the fear around them comes from imagining something far more aggressive than what they really are.
What an ATS actually does
When you submit a resume, the system parses it into structured fields — name, contact details, work history, education, skills. A recruiter then searches or filters that database. On high-volume roles some systems score candidates against the posting.
The persistent myth is that "75% of resumes are rejected by a robot before a human sees them". There is no credible source for that figure. The realistic failure mode is quieter and more common: your resume parses badly, key information lands in the wrong field or nowhere at all, and you simply do not surface in the searches a recruiter runs.
What genuinely breaks parsing
- Text inside images. A resume exported as an image, or a name rendered as a logo, is invisible. This is the single most damaging mistake.
- Multi-column layouts. Parsers read in document order. Two columns can interleave into nonsense — a job title from the left column followed by a skill from the right.
- Headers and footers. Some parsers ignore them entirely. Contact details there can vanish completely.
- Tables for layout. Support is inconsistent and cells often flatten in the wrong order.
- Unusual section names. "Where I have made an impact" may not map to Experience. Use the boring words.
- Text boxes and SmartArt. Frequently skipped.
What does not matter as much as people claim
A short list of advice you can safely ignore:
- "Never use PDF." Outdated. Every current major ATS parses text-based PDF well. A PDF exported from a word processor is fine; a scanned or image-based one is not.
- "Use a plain black-and-white template." Colour, rules and restrained styling do not affect parsing. Layout structure does.
- "Keyword-stuff to beat the algorithm." Hidden white text and keyword lists are visible to any recruiter who opens the file and read as dishonest.
- "One page maximum." A length convention for humans, not a parser rule. Two pages is normal past a few years of experience.
Matching keywords honestly
Keyword matching is real, but the mechanism is unglamorous: a recruiter searches for the skills in the posting, and you appear if your resume contains them. So use the same words the posting uses. If it says "PostgreSQL", do not write only "Postgres". If it says "stakeholder management", use that phrase rather than a synonym.
Put skills in context rather than in a bare list. "Reduced weekly reporting time 40% by rebuilding dashboards in SQL and Power BI" contains the same keywords as a skills list and also gives a recruiter a reason to keep reading.
Check how your resume parses
Upload it and see what a parser extracts, which sections it finds, and which keywords from a posting are missing.
Open ATS Resume Checker Build a resumeA structure that parses cleanly
- Name and contact details in the document body, never in the header.
- A short summary, two or three lines, tuned to the role.
- Experience, reverse chronological. Job title, employer, dates on their own line.
- Education.
- Skills, as a comma-separated line rather than a graphic or rating bars.
Single column throughout. Standard section headings. Real text, not images. That covers essentially all of it.
Frequently asked
Do skill rating bars hurt me?
They parse as nothing, so the skill may be lost entirely. They also convey little — nobody knows what four fifths of a bar of Python means. Write the skill as text.
Should I tailor my resume for every application?
Tailor the summary and the emphasis of your top few bullets to the posting's language. Rewriting the whole document each time is rarely worth the hours.
Does a photo cause a rejection?
In the US, UK, Canada and Australia, leave it off — many employers discard photo resumes for anti-discrimination reasons. In much of continental Europe it remains normal. It is a regional convention, not a parsing issue.