How to write an ATS-friendly resume without falling for the myths
The internet has convinced a lot of people that a robot reads their resume, scores it, and throws it away before any human sees it. That fear sells resume products, keyword tools and "ATS scans". It is also mostly wrong, and writing your resume around the wrong fear produces a worse resume.
Here is what an applicant tracking system actually is, what it genuinely cannot read, and where the real advice ends and the folklore begins.
What an ATS actually does
An applicant tracking system is software a company uses to collect, store, search and organise applications. When you upload a resume, the ATS parses it — pulls the text into fields like name, work history, skills and education — so a recruiter can search and filter a large pile of candidates.
That is the important part: an ATS is a tool for a human recruiter, not a judge. Surveys of recruiters consistently find that the systems do not silently auto-reject resumes; a person decides who moves forward. The "97% of resumes are rejected by a robot" statistic that circulates has no credible source behind it.
So the goal of an "ATS-friendly" resume is not to trick a scoring algorithm. It is simpler and more honest: make sure the software can read your resume cleanly, so that when a human searches, you show up — and when they open it, it looks like a resume, not a puzzle.
What genuinely breaks parsing
These are the formatting choices that actually cause an ATS to mis-read or drop your information. They are worth avoiding:
- Text inside images. A resume saved as an image, or a name/heading rendered as a graphic, is invisible to the parser. It reads no text from a picture.
- Critical information in the header or footer. Some parsers ignore the very top and bottom margins of the page. Your phone number and email belong in the body, not only in a header.
- Complex multi-column tables. Text laid out in table cells or heavy multi-column grids can be read out of order, so your job titles and dates get scrambled. A clean single-column layout is the safest, and even a simple two-column design is fine as long as the reading order is logical.
- Non-standard section names. Call it "Experience", "Work Experience" or "Employment", not "Where I've Made a Dent". The parser looks for the sections it recognises.
- Unusual fonts or heavy graphics that a parser stumbles over, and dense icons standing in for words (a phone glyph is not the word "phone").
None of this requires a special template. It requires a resume that is text, in a normal order, with the sections named plainly.
The file format question, settled
For years the advice was "never send a PDF". That is outdated. Modern ATS parse text-based PDFs well, and a PDF has the advantage that it looks the same everywhere. The real rule is narrower: send a text-based PDF (one you exported from a document, where you can select the text), not a scanned or image PDF. If a job posting explicitly asks for a .docx, send that — following the instruction is its own signal.
Keywords: the real part and the folklore
The real part: recruiters search the ATS for skills and titles. If the posting asks for "financial reporting" and your resume only says "reporting", you may not surface in that search. So mirror the actual language of the job description — the specific tools, skills and titles it names — using the words that are genuinely true of you.
The folklore: keyword stuffing, hidden white text, pasting the whole job description in a tiny font, or cramming a "skills cloud" of every buzzword. A human reads the resume after the search, and stuffing reads as exactly what it is. It does not raise a secret score, because there is usually no secret score.
Write the resume in real sentences, describe what you did with the numbers that show scale, and make sure the important terms from the posting appear naturally because they are true.
A short, honest checklist
- One clear layout, single column (or a clean two-column with logical reading order).
- Standard section names, in a standard order.
- Contact details in the body of the page, not only the header.
- A text-based PDF — or
.docxwhen the posting asks for it. - The job description's real skills and titles, mirrored where they are true of you.
- Achievements with numbers, not a wall of adjectives.
- No text baked into images, no keyword stuffing, no template so elaborate the parser trips on it.
The honest limit
A clean, well-written resume gets read fairly. It does not manufacture experience you do not have, and no formatting trick substitutes for matching the role. "ATS-friendly" is a low bar you should clear so the real contest — whether your experience fits the job — happens on its merits.
If you want a resume that is clean, single-column-safe and parser-friendly by default, our free CV maker builds one from 78 designer templates — no sign-up, and you can print, save a PDF, or download the file. It handles the formatting so you can spend your time on the words, which are the part that actually decides.

