CV tower · floor

ATS friendly resume template: what that actually means

Search for an ats friendly resume template and you will be told a great deal about algorithms, scores and secret keyword thresholds. Almost none of it comes from the companies that build these systems. This floor starts from what they publish themselves, because it is both duller and far more useful.

What actually breaks the parse

Greenhouse, one of the systems your document is fed into, on why a resume fails to parse.

There is also a hard limit that has nothing to do with design: “Greenhouse Recruiting can’t parse resumes larger than 2.5MB.” A single high-resolution photograph will take a document past that on its own.

Read that list again and notice what it is not. There is nothing about keyword density, nothing about a score, nothing about a percentage of applications being silently discarded. Every item is a layout decision — and most of them are exactly the decisions that make a template look designed.

And what it is looking for

SkillsJob titlesYears of experience Start and end datesCompany names

That is the list Greenhouse publishes, and it says it does not extract fields beyond it. Which reframes the whole exercise: an ATS-friendly template is not a template that pleases an algorithm. It is a layout that lets five ordinary pieces of information be read. Everything in the list above breaks one of the five — usually the dates, or your own name.

This is the part that changes how you choose a template. The two-column layout with a shaded sidebar, the name in a decorative header, the skills shown as little rating bars: those are the features that sell templates, and they are the features on the failure list. A plain document with ordinary headings, dates in the text and your name on the first line is not a compromise. It is the version that survives being read.

None of which means the document should be dull for the human who eventually opens it. Both things are true at once — the parser reads it first, a person reads it second — and the conflicting advice around this subject nearly always comes from arguing about only one of them.

The neighbouring searches show how unsettled this is. Ats resume and ats friendly resume are people trying to work out what the standard even is. Ats resume checker and ats resume template are people looking for a tool to tell them. And one query in this cluster is worth quoting on its own, because it is the honest question underneath all of them: is resume worded’s ats score accurate. Scores are the part of this subject with the least published evidence behind it, and that has a floor of its own below.

Where to start

Four ways in.

“I am choosing a template.”
Start at the layout
“I want to know how it is read.”
Go to how parsing works
“A checker gave me a score.”
Read scores and checkers
“I need to write the content.”
That is what goes in it

The layout

Formatting decisions, judged by whether a parser can read them. Every item here traces back to something a system vendor has published.

Columns, tables and text boxesThe three layout features named most often in parse failures, and what to use instead.Being built
Where your name goesContact details in a header or text box are a documented failure. First line, plain text.Being built
File format and sizeDocument rather than image, and the 2.5MB ceiling one photograph can breach.Being built
Fonts, icons and rating barsThe decorative features that sell templates, read as what a parser sees.Being built
Free templates that passWhere the usable ones are, and which visual choices to avoid whatever they look like.Being built

How parsing works

A short, unglamorous explanation of what happens to your file after you press send. Knowing it removes most of the anxiety.

What is extractedSkills, titles, years, dates, employers — and the vendor statement that it stops there.Being built
What an ATS is forA filing system for applications first, a filter second. The order matters.Being built
Systems differGreenhouse, Workday and the rest do not behave identically, and none of them publish everything.Being built
Languages and charactersNon-English documents, accents and non-Latin scripts, where parsing gets harder.Being built

Scores and checkers

The busiest commercial corner of this subject, and the one with the least published evidence. Handled sceptically, and openly so.

What a score is measuringWhose rules, calibrated against what — and why two checkers disagree about one document.Being built
Checkers, read honestlyWhat each publishes about its method, and what it keeps of the CV you upload.Being built
The claims with no sourceThe famous percentages, traced back as far as they actually go.Being built
Keywords, carefullyMatching the language of the advert without writing something a person will not read.Being built

What goes in it

Once the layout is out of the way, the document still has to say something. This is the wing that decides whether a person calls you.

Structure and orderSections, order and length, and what changes with years of experience.Being built
Writing about what you didTurning responsibilities into results, which is most of the actual work.Being built
Gaps and awkward historyHandling time out, short stays and redundancy without apology.Being built
Tailoring per applicationWhat genuinely needs changing each time, and what does not.Being built

What this tower will not do

It will not quote a statistic without a source. The best-known numbers in this subject — the proportion of CVs supposedly rejected before a human sees them — are repeated everywhere and attributed almost nowhere, and this floor will say so rather than repeat them.

It will not promise that a layout guarantees anything. Vendors publish what breaks parsing; none of them publish a template that passes.

And it will not rank the checkers yet. That needs one real CV, in several layouts, through each of them, with the scores and the contradictions published side by side. What holds instead is simple: the parsing facts on this page are quoted from an applicant tracking system’s own documentation.

Where this page got its facts

  1. Greenhouse Support — Unsuccessful resume parse, on what causes a parse to fail and the file size limit — support.greenhouse.io, read 21 August 2026.
  2. Greenhouse Support — Talent Matching data processing, on the fields extracted from a resume — support.greenhouse.io, read 21 August 2026.

Written by Alberto Gulotta

Founder and editor of AI Tools Primer, writing from Palermo, Italy. Thirty-five years of taking computers apart, starting with a Commodore 64 — the long version is on the about page.

Something wrong on this page? Write to aitoolsprimer@gmail.com and it gets fixed.

Independence and limits

No affiliate links and no paid placements anywhere on this site. Nobody pays to appear here, and no company has seen this page before you did.

This is general information, not professional advice. Where a page touches money, health, safety or the law, it names its source and the date it was read — and your situation may still differ. See the privacy page and the cookie policy.