ATS Resume Guide: How Applicant Tracking Systems Read Your Resume

The short answer

An applicant tracking system (ATS) is the software employers use to collect applications, parse resumes into structured fields and let recruiters search and rank candidates. Workday, Greenhouse, Lever, iCIMS, SAP SuccessFactors and Taleo are common examples. To get through it you need two things: a resume the software can read correctly, and one that uses the same language as the job description for skills you actually have.

Paste a job description and your resume into our free ATS resume checker to see which keywords are missing and whether your sections are detected.

What an ATS actually does

When you apply, the system:

1. Stores your application and asks screening questions such as work authorization, location or salary expectations. Failing a required "knockout" question is the most common automatic rejection.
2. Parses your resume into fields — name, email, phone, job titles, employers, dates, education and skills. This is where formatting matters.
3. Makes you searchable. Recruiters filter and search by keywords, titles, locations and skills. Some systems also score or rank applicants against the job.
4. Shows a human the result. In nearly every case a recruiter or hiring manager makes the decision, reading the parsed profile or your original file.

The popular claim that "75% of resumes are rejected by ATS" has no reliable source. The real risks are less dramatic but common: your job titles or dates end up in the wrong fields, your skills are not detected, or a recruiter's keyword search simply does not find you.

Formatting that parses cleanly

Element	Safe choice	Risky choice
Layout	Single column, top to bottom	Two or three columns, sidebars
Headings	Standard words: Experience, Education, Skills	Creative headings like "My Journey"
Contact details	In the body text at the top	Inside the page header or footer
Fonts	Common fonts (Calibri, Arial, Garamond, Georgia) at 10–12 pt	Decorative fonts, icons as text
Graphics	None, or a simple line divider	Skill bars, charts, photos, logos
Tables and text boxes	Avoid for core content	Experience or skills inside tables
Dates	"Jan 2023 – Present" or "01/2023 – Present" on the same line as the title	Dates in a separate column
File	Text-based PDF or .docx	Scanned or image-only PDF

Our resume builder produces a single-column, ATS-friendly layout and exports a text-based PDF from your browser.

Keywords: matching without stuffing

Keywords are the skills, tools, certifications and job titles in the posting. Recruiters search for them, and ranking features compare them with your resume.

Find them. Read the job description and highlight hard skills (Python, SQL, Salesforce, GAAP), tools, certifications (PMP, CPA, AWS Certified), domain terms and the exact job title. Requirements listed more than once, or under "required", matter most.

Use the employer's wording. If the posting says "customer success" and your resume says "client happiness", a search will miss you. Spell out acronyms once — "search engine optimization (SEO)" — so both forms match.

Prove them in context. A skills list helps parsing, but recruiters trust bullets that show the skill being used: "Built SQL dashboards in Looker that cut weekly reporting time from 6 hours to 1."

Stay honest. Only include what you can discuss in an interview. Hidden white-text keywords and copied job descriptions show up in the parsed text a recruiter reads.

A resume structure that works

1. Header: name, city and state, phone, email, LinkedIn (and portfolio or GitHub if relevant).
2. Summary (optional): two or three lines naming your target role, years of experience and two or three headline skills.
3. Experience: reverse-chronological. For each role: title, employer, location, dates, then three to six bullets that start with a verb and include a result.
4. Skills: grouped plainly — Languages, Tools, Certifications.
5. Education: degree, school, year. Add GPA only if it is strong and recent.

One page is normal for under about ten years of experience; two pages are fine for senior roles.

Tailoring for each application: step by step

1. Save the job description as text.
2. Run it with your resume through the ATS resume checker and note the missing keywords.
3. For each missing keyword you genuinely have, add it to a relevant bullet or to Skills.
4. Match your most recent job title to the target title where it is accurate (for example "Software Engineer (Backend)").
5. Move the most relevant bullets to the top of each role.
6. Re-run the check, then read the resume aloud — it must still sound natural to a person.
7. Export as a text-based PDF and name the file "Firstname-Lastname-Resume.pdf".

Bullets that work for the ATS and the recruiter

A good bullet does three jobs at once: it contains the keyword a recruiter searches for, it shows the skill being used, and it proves the result with a number. A simple pattern is action verb + what you did + tool or skill + measurable result.

Weak bullet	Stronger bullet
Responsible for reporting	Built weekly sales dashboards in Tableau, cutting manual reporting from 6 hours to 1
Worked on the website	Rebuilt the checkout in React and TypeScript, lifting mobile conversion by 12%
Helped customers	Resolved 40+ Zendesk tickets a day at a 96% satisfaction score
Managed projects	Led a 5-person team to ship a Salesforce migration two weeks early and under budget
Did data analysis	Wrote SQL and Python models that identified $250k of annual billing leakage

If you do not have an exact number, use a scale (team size, users, budget, volume) or a before-and-after comparison. Never invent figures — interviewers ask about them.

Skills sections: what to list and how

A skills section is the easiest place for a parser to find keywords, but it works best as a short, grouped list rather than a wall of buzzwords. Group by type — Languages, Frameworks, Tools, Certifications — and list the items the job description names first. Leave out soft skills such as "team player" or "hard-working"; nobody searches for them, and they are more convincing shown inside a bullet. Avoid rating yourself with bars or percentages, because parsers cannot read graphics and "80% Python" means nothing to a recruiter. Keep versions and certifications precise, for example "AWS Certified Solutions Architect – Associate" rather than "AWS certified", since recruiters often search for the full name of a credential.

Does the ATS brand matter?

Different systems parse slightly differently, but the same rules work everywhere. Workday often asks you to re-enter your experience in form fields after uploading a resume; check what it auto-filled, because errors there are what recruiters see. Greenhouse and Lever usually show recruiters your original file next to the parsed profile, so design matters a little more there — but a clean single-column layout still reads best. iCIMS and Taleo are older and more sensitive to tables, columns and unusual headings. Rather than guessing which system an employer uses, write one clean resume that every parser can read.

Cover letters, portfolios and LinkedIn

Cover letters are usually stored as a separate attachment and are rarely parsed for ranking, but recruiters read them for close calls; mirror two or three key requirements from the posting. Make sure your LinkedIn job titles and dates match your resume, because many recruiters check both, and some ATS import LinkedIn profiles directly. For technical roles, a GitHub or portfolio link in the header gives a human reviewer evidence that a keyword list cannot.

Common mistakes

• Putting contact details in the header or footer, where some parsers ignore them.
• Using a two-column template from a design tool.
• Listing duties ("Responsible for reports") instead of results.
• Sending the same resume to every job.
• Leaving out the exact job title or core tools named in the posting.
• Using images of text, icons for phone and email, or skill-level bars.

After the ATS: the human read

Once you are found, a recruiter usually spends well under a minute on the first read. Clear headings, numbers in your bullets, and a summary that names the target role all help. If you are weighing an offer, compare it properly: the hourly to annual salary calculator converts pay and shows take-home after tax, and our guide to W-2 vs 1099 taxes explains why a contract rate needs to be higher than the equivalent salary.

Checklist

• Single column, standard headings, no tables or text boxes for core content.
• Contact details in the body, not the header.
• Text-based PDF or .docx.
• Job title and top keywords from the posting, used honestly and in context.
• Bullets with results and numbers.
• Checked with the ATS resume checker before you apply.