How to write an ATS-friendly resume

What an ATS actually does

An applicant tracking system ingests your resume file and converts it into structured fields: name, contact details, employers, dates, titles, education, and any skills it can recognise. Recruiters then search or filter against that structured data.

The parsing step is where most resumes get lost. If the parser cannot determine where a section begins or ends, it either mis-files the content or drops it entirely. That is the entire problem the phrase "ATS-friendly" is describing.

What breaks parsing

• Text inside images. A name or job title that is part of a logo or graphic is invisible to a parser.
• Multi-column layouts. A two-column layout with a sidebar on the left reads as interleaved lines of text. A parser sees the sidebar text and the main text mixed together.
• Tables used for layout. Even when a table renders cleanly on screen, many parsers flatten it into an unreadable stream.
• Text boxes and shapes. Content inside these containers is frequently dropped.
• Non-standard section names. "Where I've Worked" reads differently from "Experience". Standard headings help parsers categorise correctly.
• Headers and footers. Contact details placed in the document header are often ignored entirely.
• Icons without labels. A phone icon is not a phone number to a parser.

A structure that parses reliably

A single-column resume with clearly labelled standard sections handles almost every ATS cleanly. Section headings written in plain text, in the order a recruiter expects, give the parser an easy job.

1. Name and title at the very top, as text.
2. Contact information immediately below — email, phone, location, and links. Plain text, no icons.
3. Professional summary — two or three lines, no more.
4. Experience — reverse chronological, with company, title, dates, and bullet-point outcomes.
5. Education — degree, institution, dates.
6. Skills — a clean list, no gauges or rating graphics.
7. Additional sections — certifications, projects, languages, awards.

File format: PDF versus DOCX

Modern applicant tracking systems handle text-based PDFs well. The important phrase is text-based. A resume exported as an image or scanned PDF has no text layer and cannot be parsed.

Some older systems still prefer DOCX. If a job posting asks for a specific format, follow the instruction. Otherwise, a text-based PDF from Advoke CV’s print-to-PDF export is a safe default.

Keywords, without keyword stuffing

Applicant tracking systems often score resumes against the job description. That does not mean you should paste a list of keywords at the bottom of the page. It means you should use the same vocabulary the job posting uses where it is genuinely accurate.

• If the job says "cross-functional collaboration", use that phrase once, in a bullet that describes real cross-functional work.
• If the job lists a specific tool you use, name it explicitly rather than saying "various tools".
• Do not repeat a keyword more than two or three times. Repetition does not help and reads badly to a human.

Testing whether your resume parses

A simple test: open your PDF and try to select the text with your cursor. If you can highlight a paragraph, the text layer exists. If nothing highlights, the file is an image and no parser will read it.

A second test: paste the whole PDF into a plain text editor. If the paste produces readable, in-order text, most parsers will handle it. If the paste produces interleaved or scrambled text, the layout is fighting the parser.

Summary of the rules

• Single column, top to bottom, in the order a recruiter expects.
• Plain text for every important field, especially name, title, and contact.
• Standard section headings: Summary, Experience, Education, Skills.
• No text inside images, shapes, or text boxes.
• Text-based PDF, or DOCX if the posting asks for it.
• Keywords used once or twice, in the context of real accomplishments.