What is an ATS-friendly resume? What six vendors actually document

The short answer, and the whole definition

An ATS-friendly resume is one that hiring software can read. It needs to pull the text out and put each piece in the right place. Your name goes in the name field. Your last job goes in the work history.

That is the whole test. It is about the file working, not about how the file looks.

Most advice skips straight past that and hands you a list of design rules instead. We wanted to know who decided those rules, so we went looking for the source.

• The test is whether the text can be extracted and mapped, nothing more.
• A plain file that parses cleanly is ATS-friendly. A beautiful one that does not is not.
• No format guarantees an interview. Parsing is the floor, not the ceiling.

What we actually read

Six systems: Ashby, BambooHR, Jobvite, SAP SuccessFactors, SmartRecruiters and Workday. We read their product documentation and wrote down every specific thing they say about taking in a resume file and reading it.

That came to 32 statements. Each one is on our parsing research page with the company's own wording and a link to the page it came from. You can check any of them yourself.

The silences turned out to matter as much as the statements. Jobvite barely says anything beyond naming the parser it uses. BambooHR lists which file types it accepts and stops there. Workday's main recruiting product publishes no file format list at all. The list people quote belongs to a different Workday product.

The rules everyone repeats are not in the documentation

Here is what we found. Out of 32 statements, not one mentions two-column layouts. None mentions tables. None mentions fonts. None mentions how many pages your resume should be. None mentions icons or graphics.

That does not make the advice wrong. A simple layout is easier for a person to read, and software given less to interpret has less to get wrong. But nobody who publishes these rules points to a source, and we could not find one either.

One company says something close to the opposite. Ashby writes that its newer parser is better at reading resumes with complex layouts. That is a vendor telling you its software handles the thing everyone warns you about.

So treat the usual list as a sensible precaution. Do not treat it as a rule. The difference matters if you are about to rebuild a resume that was working fine.

What the vendors do document

What the companies do document is duller than the folklore. That is probably why it gets ignored. It is also the part worth acting on.

The clearest one is images. Ashby says an image-only PDF can fail when imported by email. SAP says PDFs that started life as a scan or a photo may not read properly. SmartRecruiters has a specific error code, UNPARSABLE_RESUME, for when the file it receives is an image. Three separate companies describing the same failure.

This is the one rule with real evidence behind it. It catches anyone who scanned a printed copy, exported their resume as a picture, or built it in a tool that turns text into graphics. There is no text in the file, so there is nothing to pull out.

The others are limits rather than design choices. SAP says a resume attached to a candidate profile cannot be a protected or secured PDF. Ashby sets a 50MB cap on uploads, and a lower 16MB point above which search and autofill stop working. SmartRecruiters has a second error code, INCOMPLETE_RESUME, for a file that does not hold enough to build a candidate record from.

Why every guide says something different

There is no such thing as "the ATS". There are dozens of products from different companies, and each employer sets its own up differently. Jobvite does not even write its own parser; it uses one from a company called DaXtra. Two jobs you apply to this week may be read by completely different software.

So no formatting rule can be universal. When an article tells you what happens inside a system without naming the system, that is worth noticing.

It also explains why the handful of documented items matter more than their number suggests. When three separate companies describe the same failure, you are close to a real rule. When nobody documents something, repeating it a thousand times does not make it one.

What to actually do with your resume

Start with one check that takes five seconds. Open your file and try to select a line of text with your cursor. If you cannot highlight the words, your resume is a picture and no software can read it. That single test catches the only failure three separate companies have documented.

After that: no password on the file, no scanned copies, and keep the file a normal size.

Use section headings anyone would recognise. Put your skills inside your job descriptions as well as in a skills list. That second one is not folklore. Workday says its core parsing skips the Skills and Languages fields, so a skill sitting only in a list may not travel.

Then check what was actually read instead of assuming. Ryzio's free ATS resume checker tells you which rules your file breaks and shows the rule behind each one.

And keep the design choices that help a human. A person reads your resume after the software does. The software was never the one you were trying to impress.

• Select text in your file. If you cannot, it is an image and will fail.
• No password protection, no scanned copies, sensible file size.
• Put skills in context as well as in a list.
• Check what was extracted instead of trusting a formatting rule.