The Definitive Guide to an ATS-Friendly Resume
What applicant tracking systems really do, which formatting choices break parsing, and how to build a resume that both software and recruiters read correctly.
Published · Updated · 9 min read
In short: Most employers use an applicant tracking system (ATS) to store, search and filter applications. Your resume has to be easy for software to parse and compelling for a human to skim. Use a single-column layout, standard headings, keyword-rich content mapped to the job description, and a text-based file. Avoid tables, columns, text boxes, graphics and headers/footers.
Table of Contents
- What ATS actually do (and don't)
- Formats and features that break parsing
- Which file type to send
- How recruiters search, and how you align
- Structure: an ATS-friendly blueprint
- Content that gets indexed and read
- Design and formatting
- Before and after: the same role, two ways
- File-handling traps
- AI screening and what it changes
- Common myths, debunked
- Make your resume ATS-friendly in 45 minutes
- International notes
- Final checklist
What ATS actually do (and don't)
An ATS ingests your file, parses the text into fields (name, title, dates, employers, education, skills), indexes that text, and lets recruiters search and filter candidates. In modern workflows it is far more a database and workflow hub than a robot bouncer. Recruiters run keyword searches (often with Boolean logic like AND, OR, NOT) and quick filters (location, years of experience) to build a shortlist, then read the resumes themselves.
Important: A persistent myth says "the ATS auto-rejects most resumes without human eyes." That is not how these systems are configured in practice. The real risk is not appearing in a recruiter's keyword search, or being parsed so badly that your key facts never surface in the candidate record. Vendors' own documentation describes their products as repositories and filtering tools; people still make the call.
Formats and features that break parsing
Parsing engines are good at text, mediocre with complex layout, and bad at images. The most common failures happen when:
- The resume is an image — a scanned PDF or a screenshot, with no searchable text underneath.
- The layout uses tables, columns, headers/footers or text boxes. Contact details in a Word header is the classic one: the parser never sees your email address.
- The document relies on graphics, logos or word art to carry information a parser can only read as text.
- Section headings are creative. "My Journey" is not a heading a parser recognises; "Work Experience" is.
- Dates are ambiguous.
Jan '21–Presentand2021-are both harder to normalise thanJan 2021 – Present.
Pro tip: Greenhouse, one of the most widely used ATS vendors, documents these exact issues in its help centre and names them as causes of an unsuccessful resume parse. A clean single-column layout with no decorative structures is the safe choice everywhere.
Which file type to send
Follow the posting first. If it names a format, send that format. If it doesn't:
- Text-based PDF is the safe default. Every major ATS accepts PDF, and a PDF renders identically for the human reader. The only requirement is that it is a real PDF, not a scan or an image export.
- DOCX is a fine alternative and is what you should send when an employer explicitly says "Word document preferred". Some legacy portals and staffing-agency middleware still prefer it.
- Never send a scanned PDF, a photo, a Pages/ODT file, or anything the portal doesn't list on its upload control.
Quick check: Open your PDF, try to select and copy a paragraph. If you can't select the text, it's an image and no parser will read it. Export a fresh PDF from your editor instead.
ForgeMyCV exports a single-column, text-based PDF — the format described above. There is no DOCX export.
How recruiters search, and how you align
Recruiters search their ATS with keywords taken from the job description. If those terms aren't in your resume as plain text, you don't appear in the results — which is why tailoring beats one-size-fits-all applications.
Start by underlining the exact nouns and phrases in the posting: tools, frameworks, certifications, regulatory terms, domain vocabulary. Weave them into your resume where they are true.
Use synonyms and expansions. If a posting says "ETL" and you wrote "data pipelines", add "ETL" once where it fits. Expand acronyms at least once — "SOC 2 (System and Organization Controls 2)". Recruiter searches are literal and benefit from exact matches.
Structure: an ATS-friendly blueprint
A reliable, parseable structure you can adapt to any industry:
Name and contact (top of the body, not in a header)
- Full name on its own line.
- City/metro and country, phone, a professional email, LinkedIn or portfolio URL.
- No icons; write URLs out as text. Nothing in headers, footers or text boxes.
Professional summary (3–5 lines)
- One paragraph naming your role, your scope and what differentiates you.
- Include three to five role-relevant keywords from the posting.
Core skills (a scannable list, not a table)
- A short, comma-separated list grouped by theme —
Languages: …,Cloud: …,Analytics: …. - No star ratings, progress bars, shapes or multi-column tables.
Work experience (reverse-chronological)
- Company — Location (Month YYYY – Month YYYY)
- Job title on its own line
- Three to six bullets per role, each starting with a strong verb and ending in a measurable outcome
- Role-relevant keywords and tools inside the achievements, not bolted on
- Identical date formatting in every role
Education
- Degree, institution, graduation month and year (or "in progress").
- Relevant coursework or honours if you are early-career.
Certifications and awards
- Issuer and year. Use the exact certification names that appear in job ads.
Optional: projects, publications, community
- Bullets with scope, technologies and outcome.
Content that gets indexed and read
An ATS won't notice your tasteful colour palette, but it will index your nouns. Pair those nouns with evidence of impact so the person who opens the file is convinced in six seconds:
- Tie achievements to business outcomes: "Cut cloud spend 23% by rightsizing EC2 instances and moving batch jobs to Graviton."
- Quantify scope: "Managed a $2.4M portfolio; mentored five analysts."
- Name the stack and the context: "Replaced a nightly ETL job with near-real-time Kafka and Flink ingestion, cutting data latency from 9 hours to 4 minutes."
Avoid keyword stuffing. An over-stuffed resume is obvious to a human reader within seconds, and the keyword density buys you nothing that a natural mention wouldn't.
Design and formatting
- Layout: single column, left-aligned. No tables, columns or text boxes.
- Fonts: common system fonts, 10–12 pt body, 13–16 pt headings. Consistency matters more than the typeface.
- Bullets: plain round bullets or dashes. No custom glyphs or emoji.
- Spacing: whitespace between sections helps skimming and costs nothing in parsing.
- Headings: conventional labels only — "Work Experience", not "What I've Done".
- Graphics: none. No logos, charts, shapes, emoji or profile photos.
- Links: spell URLs out so the ATS stores them and a recruiter can click them.
- Length: one to two pages. Two pages is defensible for senior individual contributors and managers if every line earns its space.
Before and after: the same role, two ways
What an ATS struggles with
Professional Journey
2019–2022 Managed cross-team projects
Custom heading, ambiguous dates, a responsibility with no scope and no outcome, and — in the original document — the dates sat in a second table column that the parser merged into the wrong field.
What parses and reads well
Work Experience
Project Manager — Acme Logistics, Rotterdam (Mar 2019 – Aug 2022)
- Ran delivery for five product teams across three countries, 40+ engineers.
- Cut average release cycle time from 21 days to 17 by moving QA into the sprint.
- Introduced a shared intake process that reduced mid-sprint scope changes by a third.
Same person, same job. The second version puts a recognisable heading, a normalised date range, a title, a scope and three measurable outcomes into fields the system can index.
Check your own file first. Upload your current resume to the free resume checker — the basic structure check runs without an account and tells you whether your headings, dates and contact block parse cleanly.
File-handling traps
- Follow the posting's instructions before any general rule.
- Never upload an image of a resume. Scanned PDFs and photos break parsing outright.
- Keep contact details in the document body so the parser captures them.
- Check the application portal — Greenhouse-powered postings list the accepted file types on the upload control itself.
- Name the file plainly:
FirstName-LastName-Resume.pdf. Version numbers and dates in filenames end up in recruiter inboxes.
AI screening and what it changes
Modern ATS ecosystems integrate screening tools that score resumes against must-have and nice-to-have criteria derived from the job description. That doesn't change your strategy — align with the posting's language and show clear evidence that you meet the criteria. It does raise the cost of vague wording and missing keywords.
It is worth knowing that these scores are noisy. When HackerRank open-sourced its own resume-screening agent, running the same resume through it repeatedly produced markedly different scores, because much of the rubric is LLM-judged and subjective. Treat any "ATS score" — including ours — as a checklist of things to fix, not a verdict.
Common myths, debunked
- "The ATS automatically rejects me." It stores, parses and helps recruiters filter. People review the shortlist. Your risk is poor parsing and weak keyword alignment, not an algorithmic veto.
- "PDFs never work." Text-based PDFs are handled well by every mainstream system. Image-only or heavily designed PDFs are the ones that fail.
- "Fancy templates help me stand out." Decorative layouts hurt parsing and rarely impress anyone. Stand out with achievements.
- "If I paste in every keyword, I'll rank first." There is no ranking to win. Over-stuffing reads badly to the human who eventually opens the file.
Make your resume ATS-friendly in 45 minutes
Step 1 — Analyse the job description
Highlight required skills, tools, certifications and domain keywords. Map each one to something you have actually done.
Step 2 — Normalise structure and headings
Replace creative labels with "Professional Summary", "Work Experience", "Education", "Skills", "Certifications".
Step 3 — Flatten the layout
Remove columns, tables, text boxes and graphics. One left-aligned column.
Step 4 — Rewrite bullets for outcomes
Turn responsibilities into achievements with numbers, scope and the tools you used.
Step 5 — Add missing synonyms and acronyms
If the posting says "ETL", "Okta" or "SOC 2", make sure those exact terms appear where they are true.
Step 6 — Standardise dates
Mon YYYY – Mon YYYY or Month YYYY – Present, identically in every role.
Step 7 — Move contact details into the body
Delete header and footer elements; email, phone and LinkedIn go at the top of the page as plain text.
Step 8 — Export and verify
Export a text-based PDF, reopen it, and confirm you can select the text.
International notes
- US resumes: one to two pages, no photo, no date of birth. Reverse-chronological is expected.
- Europe and elsewhere: "CV" usually means a resume-length document rather than an academic CV. Follow local norms, but the parsing rules still apply because the major ATS vendors are global.
- Europass: the standard Europass export is a two-column, table-heavy layout. It is fine for public-sector portals that ask for it and a poor choice for a private-sector ATS.
Final checklist
- Single-column, plain-text layout — no tables, columns or text boxes
- Conventional headings and one consistent date format
- Keywords and synonyms from the posting, inside real achievements
- Contact details in the document body, not in headers or footers
- A text-based PDF (or DOCX when the posting asks for Word), verified by selecting the text
- No graphics, logos, icons or photos
Bottom line
An ATS-friendly resume is not a gimmick or a magic template. It is a clear, conventional document that a parser can index flawlessly and a recruiter can understand in seconds. Remove the structural obstacles, align your language with the posting, and put measurable impact in front. The tech behind ATS keeps changing; those fundamentals don't.
Next steps: run your current file through the free resume checker, then rebuild it on a single-column template. Related reading: what an ATS-friendly resume is, 15 critical ATS mistakes and single column vs two column.