ATS-friendly resume: how applicant tracking systems read it

An ATS-friendly resume is one that a hiring system can read without guessing: a single column, standard section headings such as Experience and Education, and a real text file rather than a scan or a photograph. No outside tool can show you the score a company's own system gives your resume, because you cannot see that system from outside.

Many companies, especially mid-sized and large ones, use software to collect applications. The name for that software is an applicant tracking system. It is where your resume lands when you press apply, and it is the reason a person who never sees your file can still search for you months later.

There is a lot of folklore about these systems. Some of it says a robot reads your resume and rejects it. Some of it says the software is a myth and only people read anything. Neither is quite right, and the difference matters because it decides which formatting choices are worth your time.

Is my resume ATS-friendly?

Run through this list before you send a file. Every item is covered in more detail below.

• One column of text, so the page is read in the order you wrote it.
• Standard section headings, spelled the usual way: Experience, Education, Skills.
• Dates written the same way in every role, such as Mar 2021 - Present or 03/2021 - Present.
• Your name, email and phone number in the body of the first page, not in a header block.
• A real text file exported as .pdf, not a scan or a photograph of a page.
• No tables used for layout, and nothing important inside an image, an icon or a shape.
• Plain bullets, not emoji or symbol ones.

Our free resume checker compares your resume with one job post for keyword overlap, and it does not check ATS formatting.

What a tracking system is for

A tracking system is an application database with a hiring process attached to it. Its job is to keep every candidate in one place, record who reviewed what, and make the process auditable. That is the product the company bought.

Two features come with it that affect you:

• Storage and search. Applications are kept as records. A recruiter can search those records by keyword, so a resume that is filed today can be found in six months.
• Structured fields. The system tries to fill in your name, your email, your current employer and your dates from what you attached, so the recruiter sees a scannable summary next to your file.

In most setups, the decision about who to interview is made by a person. Job portals work in a similar way: recruiters can search profiles and resumes by keyword, so the words on your page matter there too.

Does a robot reject your resume?

In most systems, people make the decision to interview. The software stores, sorts and searches. Two exceptions are worth knowing. Some employers add screening questions to the apply form, such as years of experience or notice period, and set the system to filter out answers that miss their limit. And some systems can rank applicants by how well they seem to match the job. How much weight a company gives either one varies, and you cannot see it from outside. So write for both: answer form questions truthfully and carefully, and make your resume easy to read for a person and for a parser.

What does happen is quieter and more mechanical:

1. Your resume is parsed into fields, and the parse can be wrong.
2. A recruiter filters or searches the pile, usually by a keyword or a location.
3. A recruiter reads the top of each remaining result.

A bad parse is the real risk. If the software reads your employer's name as your job title, or your dates as a single block, your record looks confused next to somebody whose file parsed cleanly. Nobody rejected you. You were simply harder to read.

What the parser can and cannot do

A parser turns a document into a list of labeled fields. It works well on a simple, single-column page and badly on anything it has to guess about. These are the choices that decide which group you are in.

Formatting that survives

• One column. If you want a two-column look, keep the content in one column and change the spacing.
• Standard section headings, spelled the usual way: Experience, Education, Skills.
• Dates written the same way in every role: Mar 2021 - Present or 03/2021 - Present, not both.
• Your name, email and phone number in the body of the first page, not in a header block.

Formatting that costs you

• Text inside an image, an icon or a shape.
• Section names that a parser does not recognize.
• Tables for anything other than actual tabular data.
• Emoji or symbol bullets instead of a plain dash or a round bullet.
• Colored text where the color carries meaning on its own.

The apply form matters as much as the file

The form is where the structured fields come from, and it is usually the part people rush. Two habits are worth having.

Fill in every field yourself if the form lets you. When a form asks for your current title and your dates, type them even if it has already guessed. A field you leave to the guess is a field that can be wrong in a way you never see.

Keep the resume you upload and the resume you send by email the same file. Two versions of your history is how a recruiter ends up with a record that contradicts the attachment.

What to do with this

Make one resume that a parser can read without guessing: one column, plain headings, consistent dates, nothing important inside an image. Then tailor the words, not the layout, for each job. The layout work is done once; the words are the twenty minute edit.

If you want to see which of your lines already match a job before you send anything, a matching tool can show you that against real openings. Start with a 7-day free trial, no card needed.

A clean file will not win you the job, but it means the file that gets read is the file you wrote. That part is in your hands.