How ATS Works, and How to Be Machine-Readable

If you’ve applied for jobs online, your resume has almost certainly passed through an applicant tracking system, usually shortened to ATS. It’s the software employers use to collect, organize, and search applications. Understanding roughly how it works takes a lot of the mystery — and a lot of the anxiety — out of applying. The goal isn’t to trick it. It’s to make sure the software can read your resume accurately so it lands in front of a human intact.

What an ATS actually is

An ATS is a database with a workflow attached. When you apply, the system does a few things:

• Stores your resume and any form fields you filled in.
• Parses your resume — it reads the file and tries to pull out structured information: your name, contact details, work history, job titles, dates, skills, education.
• Makes applications searchable and sortable so recruiters can filter a large pile — for example, by whether a resume mentions a required skill.

A common myth is that an ATS automatically “rejects” most resumes on its own with no human involved. In reality, its main job is organizing and surfacing applications for recruiters, who make the decisions. You’ll see a lot of dramatic statistics online about rejection rates and how many seconds recruiters spend. Most of those numbers are unverifiable and widely misquoted, so it’s better to focus on what you can control: whether the software can read your resume cleanly, and whether a busy human can quickly see that you fit.

Where parsing goes wrong

The most common way a resume gets misread isn’t wording — it’s formatting the parser can’t handle. When parsing fails, your carefully written experience can end up jumbled, misfiled, or dropped. The usual culprits:

• Multi-column layouts and text boxes. A parser reads in an order it expects. Columns and boxes can scramble that, mixing your job titles and dates together or losing them.
• Tables used to lay out content. Same problem — the reading order gets confused.
• Headers and footers. Some parsers skip these, so contact details placed there can vanish.
• Images and text-as-graphics. A parser can’t read text baked into an image. A logo or a skills “infographic” is invisible to it.
• Unusual section names. Creative headings like “Where I’ve Made a Dent” may not be recognized as your experience section. Plain headings — Experience, Skills, Education — are understood reliably.
• Odd file types. A standard PDF or Word document is safest. Follow whatever the application form asks for.

None of these are about beating the system. They’re about not accidentally hiding your own information from it.

How to be machine-readable

The good news: the same simple choices that make a resume parse cleanly also make it pleasant for a human to read. You don’t need two versions.

Use a single-column layout. One clear column, top to bottom, is the most reliably parsed and the easiest to skim.

Use standard section headings. Experience, Skills, Education, Summary. Boring is readable.

Put contact information in the body, not in a header or footer element.

Use real text, not images. Every word that matters should be selectable text. If you can’t highlight it with your cursor, the software can’t read it.

Keep formatting simple. Standard fonts, normal bullet points, no tables or text boxes for content. Bold and clear spacing are fine and helpful.

Save in a standard format — usually PDF unless the form says otherwise — with a sensible filename like Firstname-Lastname-Resume.pdf.

The right way to use keywords

Because recruiters search applications for role-specific terms, the words on your resume genuinely matter. If a role requires a skill you have, make sure that skill appears in plain language — ideally the same term the posting uses. This is just good tailoring (see our post on tailoring to a job posting).

What you should not do is stuff keywords: pasting long lists of terms, hiding white text, or repeating skills you don’t actually have to match a description. It doesn’t work well — a recruiter reading the resume sees through it immediately, and it can get your application discarded by the human, which is who actually decides. The honest version is stronger anyway: list the real skills the job needs, described in words a person and a parser both understand.

A simple test

Want to know how machine-readable your resume is? Open the file, select all the text, copy it, and paste it into a plain text editor. Read what comes out. If your name, job titles, dates, and skills all appear in a sensible order as readable text, a parser can probably handle it. If the order is scrambled, chunks are missing, or something shows up as gibberish, that’s your formatting to fix — before it costs you an application.

The takeaway

An ATS isn’t a gatekeeper to outsmart; it’s a filing system to cooperate with. Give it a clean, single-column, plain-text-readable resume with standard headings and the real terms the job calls for, and it will do exactly what you want: pass an accurate picture of you along to the person making the decision. Everything past that is down to the strength of your actual experience — which is where it should be.