ATS resume guide
Most applications are read by software before a human sees them. This guide explains how applicant tracking systems actually parse a resume, what breaks them, and how to make sure your application reaches a person.
What an applicant tracking system actually does
An applicant tracking system (ATS) is the software employers use to collect, store, search and rank job applications. Common platforms include Workday, Taleo, Greenhouse, Lever, iCIMS, BambooHR, SmartRecruiters and Personio. Recruiters rely on these systems because a single job advert can attract hundreds of applications and no human can read them all in detail.
The important thing to understand is that an ATS does not have an opinion about your resume. It is not scoring you out of ten and deciding whether you are good enough. What it does is:
- Extract text from the file you uploaded (PDF or DOCX).
- Parse that text into structured fields — name, contact details, work history, education, skills.
- Index those fields so a recruiter can search for them with keywords or filters.
When a recruiter searches for “Python, 5+ years, Berlin”, your resume appears in the results only if the parser successfully extracted those facts. If the parser failed, your resume is invisible — not rejected, invisible. This is the problem that “ATS-friendly” formatting solves.
What actually breaks ATS parsing
The list of things that break parsers is shorter than most advice suggests. These are the ones that genuinely matter.
Text inside images
If your name, a section heading or an entire resume is rendered as an image — a PNG, a screenshot, a graphic in a PDF — the parser cannot read it. The PDF looks fine to you and to any human who opens it, but the software sees a blank rectangle. This is the single most damaging formatting mistake you can make.
Text inside tables, text boxes and shapes
Some ATS platforms handle tables well. Others read them out of order, or skip cells entirely, or duplicate the content. Text boxes and shapes have the same problem. If your experience entries are laid out in a two-column table, a strict parser may read all the dates first, then all the job titles, then all the descriptions — which is not useful to anyone.
Advoke CV avoids this entirely: no tables, no text boxes, no shapes. Every piece of content is a real HTML element rendered to real text.
Headers and footers
Content placed in the header or footer area of a Word document or PDF is skipped by most parsers. This is a common trap: people put their name and contact details there because it looks tidy. Move them into the body of the document instead.
Unusual section headings
A parser expects headings like “Experience”, “Work Experience”, “Employment” or “Professional Experience”. If your resume says “Where I’ve Made an Impact”, the parser may not recognise it as a work history section and will not extract the entries beneath it.
The same applies to education (“Education”, “Academic Background”), skills (“Skills”, “Technical Skills”, “Core Competencies”) and certifications (“Certifications”, “Licenses”). Stick to the common wording unless you have a specific reason not to.
Non-standard date formats
Use “March 2021 – Present” or “03/2021 – Present”. Avoid abbreviations the parser might not recognise (“Mar ’21”), creative formats (“Spring 2021”) or leaving dates out entirely. Consistently placed dates help the parser build a coherent work history.
Columns and sidebars (usually fine, sometimes not)
Modern ATS platforms handle two-column resumes reasonably well. Older or stricter ones may read them out of order. If you are applying through an unfamiliar portal, or you are unsure whether the employer uses a modern system, a single-column layout is the safer choice.
Advoke CV marks these templates clearly: ATS-friendly templates are all single-column, and two-column templates carry a note on their detail page explaining that they may not parse cleanly in every system.
What does not matter as much as you might think
A lot of the advice you will read is overstated. These things are commonly listed as “ATS killers” but rarely cause real problems.
- Colour. Section headings in a brand colour, accent lines and a coloured sidebar background are all fine. What matters is that the text is real text, not an image.
- Fonts. Any standard font that is embedded in the PDF or available on the reader’s system will parse. Unusual display fonts are a cosmetic risk, not a parsing one.
- PDF vs DOCX. Modern ATS platforms handle both. PDF is usually safer because it preserves your layout; DOCX is more reliable if the employer specifically asks for it.
- File names. “resume.pdf” is fine. Naming your file “Ayesha-Rahman-Resume-2025.pdf” is also fine. Nobody is scoring your filename.
- Photos. Including a photo is fine for parsing but may be discouraged in some countries for legal reasons. See the FAQ on the homepage for country-by-country guidance.
A practical ATS-friendly checklist
If you want one list to check your resume against, use this one. It is short on purpose — everything on it is something that genuinely affects whether a parser extracts your information correctly.
- Single-column layout (unless the employer is known to accept two columns).
- Standard section headings: Experience, Education, Skills, Certifications.
- No tables, no text boxes, no shapes containing text.
- No content in headers or footers.
- All text is real selectable text — nothing rendered as an image.
- Dates in a consistent format like “March 2021 – Present”.
- Contact details (email, phone, location) at the top of the body.
- Skills listed by name, not just by icon or logo.
- Job titles that match the terminology in the job advert.
- PDF exported with real text, not a scanned or image-based export.
Keywords, honestly
Every ATS has a keyword search. Recruiters use it to filter applications by skills, tools, certifications, industries and locations. If your resume uses the same words as the job advert, you are more likely to appear in the search results.
This is not an invitation to keyword-stuff. Copying a job advert into your resume in white text, or listing every technology you have ever touched, will not help — recruiters read the resume once it reaches them, and obvious keyword stuffing reads as dishonest.
The honest approach is simple: read the job advert carefully, and make sure your resume uses the same vocabulary for the things you have actually done. If the advert says “stakeholder management” and your resume says “worked with stakeholders”, use the advert’s phrase. If the advert says “React” and you have used React, say “React”. If you have not used React, do not list it.
How to test your own resume
Before you submit, open your exported PDF in a plain text editor or a tool that strips formatting. If you paste the plain text and it still reads like a coherent resume — name, contact, sections, entries, in order — an ATS parser will handle it. If the plain text is a jumbled mess, the parser will struggle too.
Advoke CV's PDF export always produces real selectable text, so this test should always pass. If it does not, something is wrong with the export and you should try again.
The bottom line
ATS platforms are not the enemy. They are administrative software that gets confused by the same things a reader with a screen reader would get confused by. If your resume uses clean structure, standard headings and real text, it will parse correctly — and it will also read better for the human who eventually opens it.
Start with an ATS-friendly template, fill it in honestly, and export. That is the whole process.