How Applicant Tracking Systems Read Your Resume (And How to Pass Them)

Applicant tracking systems have a reputation problem. People talk about them as if they were secret judges that throw away good candidates for using the wrong font. Some of that fear is leftover advice from a decade ago. Some of it is still useful. The truth sits in the middle: software does screen resumes, but it is not magic, and you do not need a gimmick to get through it.

An ATS is a database. Companies use it to store applications, search them, and move people through stages. When you upload a resume, the system tries to pull out your name, dates, titles, skills, and education. Then a recruiter searches, filters, and reads. Sometimes a posting gets so many applicants that the first pass is a keyword search. Sometimes a human still opens every file. You cannot know which one you are in. You can write a resume that survives both.

This guide explains what those systems actually do, what they struggle with, and how to write so you are easy to find without turning your resume into a pile of keywords.

What an ATS Is Not

It is not a person. It will not fall in love with your beige color palette. It will not be impressed by a skill bar that says you are 80 percent proficient in leadership. It also will not always reject you because you used Garamond.

Many modern systems can read a reasonably clean PDF. Many still stumble on text inside images, charts, and complex tables. The risk is not “PDF versus Word” as a moral question. The risk is whether your content is real text in a sensible order.

If a recruiter cannot copy a sentence from your resume and paste it into an email, the ATS may not be able to read that sentence either.

How Parsing Usually Works

When you upload a file, the software tries to map sections.

It looks for headings it recognizes: Experience, Education, Skills, Summary. It looks for dates. It looks for email addresses and phone numbers. It tries to attach bullets to the right job.

If your headings are cute, the map breaks. “Where I’ve Been” might look clever. “Work Experience” parses. “My Journey” might confuse a parser. “Professional Experience” is safe.

If you put key facts in a header or footer, some systems skip them. If you use two columns, the parser may read left to right across both columns and jumble your jobs. If your name is a logo image, the system may not capture your name.

You do not need to make the resume ugly. You need to make the text linear.

Formatting Rules That Still Matter

Use a standard file unless the posting says otherwise. PDF is fine for most company sites now. If a portal specifically asks for .docx, send .docx. Do not send Pages, Google Docs links, or screenshots.

Use common section titles. Use a single-column layout if you want the least risk. Plenty of people get jobs with simple two-column resumes, but if you are applying at scale through portals, simple wins.

Do not put important information in text boxes that behave like graphics. Do not use tables to build the whole page unless you know they export as real text. Do not use icons instead of words for email and phone.

List skills as words, not charts. “Python, SQL, Tableau” can be searched. A circle that is three-quarters full cannot.

Keep dates consistent. “Jan 2022 – Present” is easier than “22 – now” or a visual timeline with no numbers.

Write for Search Without Keyword Stuffing

Recruiters search the database the way you search a folder. They type the terms from the job: “Salesforce,” “P&L,” “RN,” “OSHA,” “Spanish,” “B2B,” “Figma.”

If you have the skill and you never wrote the word, you may not come up. That is the real ATS problem for many people. Not a robot vendetta. A missing word.

Read the posting and highlight the tools, methods, licenses, and domain terms. Then, only where they are true, use those terms in your skills list and in your bullets.

If the job wants “stakeholder management” and you ran weekly meetings with clinic directors, you can say you managed stakeholders. If the job wants “Java” and you know Python, do not add Java. Getting past the search and failing the screen is not a win.

Stuffing looks like this: a skills section that repeats “project management” eight times, or a white-text block of keywords hidden at the bottom. Recruiters know those tricks. Some systems ignore hidden text. It is not clever. It reads as desperate.

A better approach is one clean skills cluster plus bullets that use the terms in context.

“Implemented Salesforce for a 9-person sales team and built the pipeline report used in Monday standups.”

That line can be found, and a human can understand it.

Match the Job Title Carefully

Some searches filter on titles. If you were “Customer Advocate III” and the world calls it “Customer Success Manager,” you have a translation problem.

Do not fake a title you did not hold. You can add a clarifying phrase: “Customer Advocate III (customer success / account support).” Or use the employer’s title and put the common language in the bullets and summary.

The summary is a good place for the target title if it is fair. “Customer success specialist with three years in SaaS support” helps both search and humans. “Seeking to leverage synergies as a rockstar ninja” helps neither.

Names, Contact Details, and Identity Fields

Put your name as actual text at the top. Use the email you check. Use a phone number with the country code if you are applying internationally.

If you have a common name, a LinkedIn URL or portfolio link helps the recruiter confirm they have the right person.

Do not put your photo in the U.S. private sector. It does not help ATS parsing and it can introduce bias. In markets where photos are still expected, follow that market, but keep the photo out of the parse-critical header if you can.

Common Ways Good Candidates Get Lost

They submit a designed resume that is actually an image.
They use a template where dates sit in a column the parser never reads.
They save the file with a name like “resume_final_use_this_one.pdf” instead of their own name.
They apply with a scanned printout.
They list skills only in a graphic.
They describe experience in paragraphs so dense that neither software nor a tired recruiter can extract tools and dates.

All of these are fixable without hiring a wizard.

A Human Still Has to Like It

Here is the part ATS anxiety leaves out. If you pass the parser and the keyword screen, a person still opens the file. Sometimes that person has 30 seconds. Your resume still needs to be a good resume: clear story, proof, no clutter.

An ATS-friendly document that is dull and generic will not save you. An ATS-friendly document that is specific and easy to skim can.

Write for the human first, then remove the formatting that software hates. That order keeps you from producing a keyword sheet that no manager wants to interview.

A Simple ATS Pass Before You Apply

Open your resume. Copy all the text into a plain text editor. If the order turns into nonsense, a parser might struggle too.

Check that every important skill appears as a real word.
Check that headings are standard.
Check that dates are next to jobs, not in a visual sidebar the copy-paste test drops.
Check that the file name has your name in it.
Check that you did not hide text or stuff the same phrase over and over.

Then tailor the skills and a few bullets to the posting. Fifteen minutes of honest matching beats a $200 “ATS certified” template with broken columns.

What to Remember

The applicant tracking system is a filing cabinet with a search bar. Your job is to be findable and readable. Use real text, real headings, real skills, and real evidence. Skip the folklore about secret fonts. Skip the hidden keyword dump.

If a person who knows your work can find your best proof in 20 seconds, and a search for the posting’s actual tools would find you in the database, you have done enough. After that, the hiring team is not a piece of software. They are people deciding whether to talk to you. Write for them.