The ATS-Friendly Resume Format (with a Simple Checklist)

The layout

One column, top to bottom, in reading order. That single rule prevents most parsing failures. A sidebar looks efficient but a parser may read the sidebar and the main column in the wrong order, interleaving your skills with your job titles.

Headings and sections

Use the section names recruiters and parsers expect: a short summary, Work Experience, Education, Skills, and optional Certifications or Projects. Put them in that order. The parser maps your content to fields by these headings, so plain wins.

Type and spacing

• A common, legible font — the default in any resume template is fine. Decorative fonts can render as missing glyphs.
• Real bullet characters, not images or wingdings.
• Enough white space to scan; dense walls of text lose the reader even after they pass the ATS.
• Dates in a consistent format on every entry (e.g. “Mar 2021 – Present”).

File and export

Export a text-based PDF unless the posting asks for Word. Name the file clearly — “Firstname-Lastname-Resume.pdf”. Never upload a screenshot or a flattened design export; the text has to be selectable.

What the parser actually does

An applicant tracking system does not “see” your resume the way a person does. It extracts the text, splits it into sections using your headings, and then tries to file what it finds into fields: name, contact details, employers, job titles, dates, education, skills. Every formatting rule in this guide exists to make that extraction boring and predictable.

Trouble starts when the text is not where the parser expects it. Content inside tables, text boxes, headers and footers, or images can be skipped or read out of order, and some systems drop it entirely. A resume can look perfect on screen and still arrive in the recruiter’s database with a blank employer field.

Contact details

Put your name and contact line in the body of the page, at the top, as plain text. Do not tuck them into the document header, and do not replace “Email” or “Phone” with small icons the parser cannot read. Include a phone number, an email address, your city and region, and a profile link such as LinkedIn written out as text or as a normal link.

Jobs, titles and dates

List each role as its own entry: job title, employer, location, and dates, in the same order every time. If you held several roles at one company, give each title its own line with its own dates rather than merging them. Use the real job title; if your internal title was unusual, you can add the common equivalent in brackets so a search for the standard title still finds you.

Skills and acronyms

List skills as plain text, in a short list or separated by commas, and group them if the list is long (for example, Tools, Languages, Certifications). Spell out an acronym the first time and give the short form in brackets, such as “search engine optimization (SEO)”. A recruiter may search for either form, and writing both costs you a few characters.

Test your own file

You can check parsing yourself in a minute. Open your exported PDF, select all the text, and paste it into a plain-text editor. If the words come out in reading order with your sections intact, a parser will most likely cope. If sections are scrambled, missing, or interleaved, fix the layout before you apply. Resumade’s free ATS checker runs a similar check and tells you which sections it could read.

The checklist

• Single column, standard headings, in the expected order.
• Selectable text — you can highlight every word.
• No tables, text boxes or images holding real content.
• Consistent dates and a legible font.
• The hard skills from the job description appear, in context.
• Exported as a text-based PDF (or Word if requested).