An ATS resume sounds like a kind of document, and it is not one. No recruiting system issues a format, and no template satisfies one. The phrase describes a much smaller property: the text in your file survives being imported into a company's hiring database, and stays findable there afterwards. Almost everything sold as ATS optimisation is either about that import step or about a scoring process nobody outside the company can see.
What the software does with your file
An applicant tracking system is the database a company keeps its applicants in. When your resume arrives, the system reads the file and copies what it recognises into structured fields on your record.
Two vendors describe this plainly. Greenhouse says its parser uses standard resume structure as a guide to interpret the content, and pulls out the name, email address, phone number, mailing address, current title and current company. Workday's recruiting documentation says that when a prospect uploads a resume, it parses contact information, education and experience into the prospect record. In both cases the original file is stored as an attachment as well, but the record is the part the system can sort, filter and act on.
That is the whole of what an ATS is doing to your resume at the moment you press submit. It is an import, not a judgement.
The failure mode is a blank record, not a rejection
Greenhouse is specific about what breaks the import: a resume that does not follow a standard format, or one that includes embedded images, can produce content the parser cannot interpret, and the parse fails. When that happens the resume is still attached to the candidate, and the fields are left for a person to fill in by hand.
This is duller than the folklore, and worse in a quieter way. Nothing rejected you. Your record simply arrived thin, with your name possibly missing and your history definitely missing, waiting on somebody to retype it from a PDF. Whether they do depends on how many other applications landed that week.
Why a thin record costs you weeks later
The part people miss is that the database outlives the application. Recruiters search it, including for roles you never applied to.
Lever's search is a good illustration because the behaviour is documented: a recruiter can prefix a term with Resume: so that only candidates with that word in their resume come back, deliberately excluding candidates where the word appears only in notes or interview feedback. A term you never wrote cannot surface in that search. Neither can a term you did write, if it lived inside a graphic or a sidebar that the parser dropped on the way in.
That is the real argument for using the posting's vocabulary, and it has nothing to do with fooling a filter. Our resume keyword generator pulls the terms a posting is built around, if you would rather not do the extraction by hand.
The scoring you cannot see, and why writing for it fails
What the vendors document is parsing, storage and search. What they mostly do not document is ranking, because ranking is usually configured per company: required questions, filters, a recruiter's own saved search. From outside an application you cannot tell which of those a given employer switched on, or how.
So writing for an imagined scoring algorithm is a bet you have no way to settle. Making your file readable is not a bet at all. It is the one part of this you control completely, and it pays off in every system rather than in the one you guessed about.
What "ATS-friendly" actually reduces to
- Real text, not a picture of text. If you cannot select a line with your cursor, no parser can read it either.
- One column, running top to bottom. Multi-column layouts and sidebars are read in an order you did not intend, when they are read at all.
- Contact details in the body. A header or footer is a separate region of the document and is not reliably picked up.
- Section headings a person would use. Experience, Education, Skills. A parser looking for standard structure finds standard structure.
- The file type the employer asks for. Greenhouse's own advice to recruiters uploading a resume is to use a PDF for best results, but if a posting names a format, that instruction wins.
None of this is about beating anything. It is the difference between a complete record and an empty one.
Check it rather than assume it
Formatting that imports cleanly in one system sometimes breaks in another, which is worth finding out before you apply rather than after. Run the file through our ATS resume checker to see what text actually comes back out of it.
Readability is the floor, though, not the goal. Once the file parses, the separate question is what it should say for this particular posting, which is covered in tailoring a resume to a job description.