ATS resume guide: what applicant tracking systems actually read

An applicant tracking system, or ATS, is the software layer between you and a human hiring manager. It parses your PDF, normalizes the text, scores it against the job posting, and ranks it. Most candidates lose at this layer without knowing why. The rules are simple, the failure modes are well known, and the fixes below take less than an hour.

Jobscan and others estimate that a large share of mid-sized and enterprise employers (Jobscan's Fortune 500 analysis puts it above 97% for the Fortune 500) use an ATS. The dominant systems in 2026 are Workday, Greenhouse, Lever, iCIMS, Taleo, and Ashby. Their parsers differ in detail but agree on the fundamentals.

Layout: do not lose the easy points

The single biggest reason resumes get butchered by an ATS is layout. PDF parsers walk a document top-to-bottom, left-to-right, and they assume one logical reading order. Two-column resumes that interleave content visually but not in the document tree get read in the wrong order, and important sections vanish.

• Stick to a single-column layout unless your builder explicitly proves the PDF text layer is in correct reading order. If the PDF copy-paste comes out scrambled, an ATS sees the same scramble.
• No tables, text boxes, or images for anything you want parsed. Headshots, infographic skill bars, and rating dots all get dropped. Every word that matters lives as plain text.
• Real headings: Experience, Education, Skills, Projects. Do not get cute. ATS parsers anchor on these words to figure out which fields you are filling.
• Avoid headers and footers for contact info. Many parsers ignore them entirely. Put name, email, phone, and location in the document body at the top.
• Standard fonts: Helvetica, Arial, Times, Calibri. Custom display fonts can cause OCR-style fallbacks that mangle ligatures and accents.

Keywords: write what they typed

After parsing, the ATS scores your document by counting how many terms from the job description appear in your resume, weighted by where they appear (a Skills section beats a footer) and how many times. Recruiters also run keyword filters directly against the parsed text, so the exact string matters.

The mistake people make is assuming the ATS knows synonyms. It usually does not. If the posting says "Postgres" and your resume says "PostgreSQL", you are at the mercy of whichever variant the recruiter typed into the filter. Include both once, somewhere.

Three keyword rules that work

1. Mirror the job posting's exact phrasing. If the JD says "continuous integration", write "continuous integration" once, even if you also say "CI/CD" elsewhere. The first appearance generally gets the most weight.
2. Put 5-10 hard skills in a Skills section. Matches inside a section literally titled Skills score higher. A skills line that reads "Python, Django, Postgres, Redis, AWS, Docker" outperforms the same words scattered through your bullets.
3. Repeat the most important keyword in context. If the role is "Senior Data Engineer", bullets in your most recent role should reference data pipelines, ETL, or whatever the JD anchored on. Once is barely enough; twice is the sweet spot; five is keyword stuffing.

If you want this automated, tools like CVHive score your resume against a pasted JD and list the keywords you are missing. You can do the same thing by hand in a text editor with a highlighter; the point is not the tool, it is the pass.

Your resume is not graded on creativity. It is graded on whether a stranger can open it and answer one question: does this person match the role?

Bullets: action verb, what, outcome

Every bullet should follow the same shape: a strong action verb, what you actually did, the outcome in measurable terms. ATS systems do not score for verb strength, but recruiters do, and recruiters decide whether a high-scoring resume turns into a phone screen.

• Bad: Responsible for managing the team and working on various projects.
• OK: Led a team of 4 engineers and shipped three projects.
• Strong: Led a team of 4 engineers; shipped a payments retry pipeline that recovered $1.2M in failed transactions in the first quarter.

If you do not have hard numbers for every bullet, that is fine. Use concrete scope instead. "Across our top 20 enterprise accounts" works. "In the first three months" works. The point is specificity, not invented percentages. See 11 resume mistakes for the fabrication traps to avoid.

File format and naming

• Submit a PDF unless the application portal explicitly asks for .docx. Modern ATS platforms parse PDF text layers reliably. Word documents have their own layout-shift problems across versions.
• Name the file FirstLast-Resume.pdf. Random names like "final-final-v3.pdf" show up in the recruiter's inbox and look careless.
• One page if you have less than 8 years of experience. Two pages if you have more or you are applying to a research role. Never three.

Anti-patterns that get you auto-rejected

• Skill ratings (4/5 stars next to React): unscored, distract from real keywords, signal junior.
• Photos and personal information: in the US and UK, many recruiters discard resumes with photos to avoid bias-claim risk.
• Long paragraphs instead of bullets: parsers and humans both lose interest after the second line.
• Headers like "What I do" or "My journey": the ATS does not match these to known section types.
• Buzzword soup: passionate, results-driven, team player, rockstar, ninja, dynamic. Recruiters skim past these. ATS systems do not weight them.

A 5-minute pre-submit checklist

1. Open your PDF and copy-paste into plain text. Reading order should make sense top to bottom.
2. Count keywords from the JD. 5-10 of the most important should appear in your resume.
3. Verify your contact info is in the body. Not in a header or footer. Email and phone visible above the fold.
4. Every bullet starts with a verb. And ends with a number, scope, or measurable outcome.
5. Save as FirstLast-Resume.pdf. Submit.

Key takeaways

• Layout beats wording. A scrambled two-column PDF loses before the scoring step even runs.
• Mirror the JD's exact phrasing. Synonyms are a gamble.
• Put hard skills in a Skills section. That section weighs more than a bullet buried on page two.
• Quantify outcomes where you can. Use concrete scope where you cannot.
• If you are tailoring for a specific role, read our 5-minute tailoring guide next.