What Is an ATS? How Applicant Tracking Systems Read Your Resume

An ATS is the software that screens your resume before a human sees it. Here's how it works, why it rejects good candidates, and how to get past it.

Around 75% of resumes are rejected before a human ever reads them. Not because the candidate was unqualified — because a piece of software couldn't parse the file, match the title, or find the right keywords.

TL;DR: An ATS (Applicant Tracking System) is the software employers use to collect, store, and filter job applications. It parses your resume into structured data, scores it against the job description, and ranks you against other applicants. If it can't read your resume cleanly, you get filtered out — regardless of how qualified you are.

Applicant Tracking Systems have quietly become the gatekeeper of almost every online application. Over 98% of Fortune 500 companies use one, and the tools have trickled down to mid-size and small employers too. Understanding how they work is the difference between landing in the "review" pile and disappearing into the "no" pile.

What does an ATS actually do?

An ATS handles the entire pipeline between you clicking "Apply" and a recruiter opening your resume:

• Collects every application into a single database.
• Parses your resume — it converts your PDF or Word file into structured fields: name, contact info, work history, education, skills.
• Scores and ranks you against the job description, usually by keyword and title match.
• Filters candidates so recruiters can search ("show me everyone with 'Kubernetes'") instead of reading hundreds of resumes one by one.

The parsing step is where most good candidates lose. If the ATS misreads your "Formation" section header instead of "Education," or can't extract your job titles because they're buried in a table, that information effectively doesn't exist as far as the system is concerned.

Which ATS platforms are most common?

You're almost never told which system you're applying through, but a handful dominate the market:

This matters because the systems behave differently. Workday and Taleo are notoriously strict — they'll penalize a resume that Greenhouse would parse fine. A resume that's "ATS-friendly" in general can still get rejected by a specific stricter system.

Why does an ATS reject qualified candidates?

The rejections that sting most are the ones where you were a good fit. The usual culprits:

• The job title doesn't match. Many systems match the exact job title against your resume. If the posting says "Senior DevOps Consultant" and your resume says "Infrastructure Engineer," you may never surface in the recruiter's search.
• Parsing failures from formatting. Tables, multi-column layouts, text inside images, headers/footers, and unusual fonts can scramble what the parser extracts.
• Missing keywords. If the role requires "CI/CD" and "Terraform" and those exact terms aren't on your resume, you score low — even if you have the experience under a different name.
• Non-standard section headings. Label your experience "Career Journey" instead of "Work Experience" and the parser may not recognize the section at all.
• Wrong file type. Some older systems choke on certain PDF encodings; a few still prefer .docx.

How do you make a resume ATS-friendly?

The fixes are mostly mechanical, and they don't require dumbing down your resume:

1. Use a single-column layout. Multi-column designs confuse parsers — they often read straight across, merging unrelated text.
2. Use standard section headings: "Work Experience," "Education," "Skills." Don't get creative here.
3. Mirror the job title. Include the exact title from the posting in your header or summary, where it's true to your experience.
4. Match keywords from the job description — the specific tools, certifications, and skills named in the posting, in the words they use.
5. Keep formatting plain. No text in images, no tables for layout, standard fonts, dates in a consistent format.
6. Submit the file type the application asks for — usually PDF is safe, but follow the form.

The hard part isn't knowing these rules — it's knowing which ones you're breaking on a specific resume for a specific job. That's exactly the gap a checker closes.

Stop guessing — see why your resume gets filtered

A score alone ("66/100") doesn't help you fix anything. What helps is knowing the precise reason: which section didn't parse, which job title is missing, which keywords from the posting you're not matching, and how each one maps to the systems likely screening you.

That's what cvlint does — it compares your resume against the actual job description and tells you the exact lines to change and why, not just a number. It's free to try, and you'll know in 30 seconds whether your resume would survive the filter.

If you want to go deeper on tooling, see our comparison of Jobscan and free alternatives.