For anyone applying this month

Write an ATS Friendly Resume That Gets Read

Most rejections happen before a person opens the file. Here is the structure, formatting, and wording that gets past the filter.

Start with a template See the six rules
A candidate reviewing a printed resume page at a bright home office desk
Formatting rules

Six choices that decide whether the ATS reads you

None of this is about sounding impressive. It is about a parser being able to find the words it is scanning for.

One column, no tables

A two-column layout looks tidy to a person and confuses most parsers, which read left to right and can merge your job titles with your dates into one unreadable string.

Standard section headings

"Experience," "Education," and "Skills" get recognised. "Where I've Been" or "My Toolkit" often do not, and the content underneath gets filed as unclassified text.

The job post's exact words

If the listing says "project management," write "project management," not "managed projects." Most ATS keyword matching is literal, not semantic.

Plain fonts, no icons

A phone icon next to your number or a star rating next to a skill can render as a broken character, or nothing at all, once the parser strips the formatting.

One consistent date format

Pick "Jan 2023" or "01/2023" and use it everywhere. Mixed formats make it harder for the system to sort your work history in order.

Contact details in the body

Information placed in a header or footer is invisible to a large share of parsers. Your name, email, and phone number belong in the main text block, at the top.

Three passes, one sitting

How to build one, section by section

Start from the listing you are applying to, not from a blank page.

  1. 1

    Read the job post for its nouns

    Underline the skills, tools, and job titles the post repeats. Those are the terms the parser was very likely configured to look for. Your resume needs to contain them, in that exact wording, somewhere true.

  2. 2

    Order the sections top to bottom

    Contact details, a two-line summary, experience, skills, education. No sidebars, no columns competing for the same horizontal space.

  3. 3

    Write bullets that mirror the listing

    Each bullet should pair one of your underlined nouns with a real result. "Managed a $40K vendor budget" beats "responsible for vendor management," and it still contains the keyword.

  4. 4

    Strip it down and read it plain

    Copy the whole document into a plain text editor with no formatting. If the section order and headings still make sense with every visual cue removed, a parser will likely read it the same way.

What I actually see

The resumes that never reach a person

I have opened resumes that arrived as a single wall of merged text because a decorative sidebar collapsed the layout. I have seen a candidate's most recent job title sitting three lines below where it should, because a text box shifted during parsing. None of these candidates were unqualified. Their formatting simply never made it to the stage where a person could judge the substance underneath. The frustrating part is how avoidable it is: the fix is rarely about experience, it is almost always about structure.

  • A two-column resume where the right-hand skills list ended up spliced into the middle of a job description
  • A skills section built entirely from graphic star ratings, which the parser rendered as blank squares
  • A candidate's strongest role buried under a creative heading the system filed as unrecognised text
A recruiter scrolling through a resume on a laptop next to a small stack of printed applications
The two-minute test

A check you can run without any tool

Before you send a resume, paste the full text into a blank document with no formatting carried over, then read it top to bottom. If your name and the section headings are still where they should be, and no line has fused two columns into nonsense, you have a reasonable signal that a parser will read it the same way a person would. It will not catch everything an automated scanner checks, but it catches the failure mode that sends the most qualified candidates straight into the reject pile: a layout that looks fine on screen and falls apart the moment the formatting is gone.

  • Works on any resume, in any file format, with no account or upload
  • Takes about as long as it took you to read this section
  • Catches merged columns, orphaned headers, and text boxes that dropped out entirely
A candidate typing a resume draft on a laptop with a page of handwritten notes beside it

Questions worth answering before you hit send

What does "ATS friendly" actually mean?
It means the file's structure, not just its content, can be read correctly by the software that pre-sorts applications. A well-written resume in a two-column table can still fail if the parser cannot follow the layout.
Do tables and columns really break parsing?
Often, yes. Many parsers read a page left to right in a single pass, so a table or a text box outside the main column can get read out of order or skipped entirely, depending on the system.
Should I copy the exact words from the job post?
For skills and tools, yes. If the listing says "stakeholder management," use that phrase rather than a synonym you think sounds better. Most keyword matching in this software is literal.
Is a PDF safe, or should I always use Word?
A simple, single-column PDF exported directly from a word processor is usually fine. The risk is not the PDF format itself, it is PDFs built from design tools that convert text into images, which most parsers cannot read at all.
Do Canva-style resume templates hurt my chances?
Frequently, because many are built with layered graphics and columns designed for a human eye, not a parser. If you like one visually, rebuild the same content in a single-column word processor document instead.
How long should an ATS friendly resume be?
One page for under ten years of experience, two at most beyond that. Length is a human readability concern more than a parsing one, but a shorter document also means fewer places for formatting to go wrong.
Does a photo or a graphic skill bar matter to the score?
A photo is usually just ignored, but a graphic skill bar is worse: parsers cannot read a shaded rectangle as "Excel, advanced," so that information often disappears completely rather than scoring lower.

Stop guessing what the filter wants

The structure is the same for every application. Only the underlined nouns change.

Start with a template Back to the six rules
Oh · Boiler
Start writing