What is an ATS? How applicant tracking systems actually work in 2026

Most resume advice about ATSes is wrong. Either it overstates what the system does ("the ATS rejects 75% of resumes automatically") or it understates what matters ("formatting doesn't really matter as long as the content is good"). Both are wrong in different directions, and the result is students wasting hours optimizing for things that don't matter while skipping the formatting rules that actually do.

This post is the technically correct explanation: what an ATS actually is, what the major ones (Workday, Greenhouse, iCIMS, Lever, Taleo) actually do, and what to do about it as a student applying to internships and entry-level roles.

What is an applicant tracking system?

An ATS (applicant tracking system) is software that companies use to receive, parse, store, score, and route resumes through the hiring funnel. The term covers a wide range of products, but every modern ATS has the same five core functions:

1. Receive — accept resume submissions through a careers page or integration
2. Parse — extract structured data (name, email, work history, education, skills) from the resume document
3. Store — save the structured profile in a candidate database
4. Score — rank candidates against a job's requirements (often via keyword matching)
5. Route — move candidates between recruiter, hiring manager, and interviewer queues

The score and the keyword filter are the steps that get the most attention from job seekers. They matter, but they're a smaller part of the system than most resume-tool marketing implies.

Which ATSes are actually most common in 2026

By US market share among employers using a formal ATS:

If you're applying to a top-100 US tech company in 2026, you're almost certainly hitting Workday, Greenhouse, Lever, or Ashby. The parser behavior across these is broadly similar — they all do basic Word/PDF text extraction, structured-field detection, and keyword matching. The differences live in the ranking and routing logic, which is mostly invisible to the candidate.

What an ATS actually does (and doesn't do)

The persistent myth is that ATSes auto-reject 75% of resumes before a human sees them. That number gets repeated everywhere — and it's wrong.

What actually happens:

The ATS parses your resume into structured fields. Name, email, phone, education, work history, skills. If your formatting is messy (two-column layouts, embedded images, non-standard headers), the parse degrades and some fields end up blank or in the wrong place. The candidate isn't rejected; the recruiter just sees a profile with missing data, which lowers the recruiter's confidence.

The ATS scores your resume against the JD's keywords. Every candidate in the pool gets a score (0-100, or some normalized equivalent). The score doesn't auto-reject — it just sorts. Candidates above a threshold get surfaced first; candidates below get pushed lower in the queue.

A recruiter or coordinator reviews the sorted pile. This is where actual rejection happens. The recruiter spends 6-30 seconds per resume on the first pass, often using ATS-provided filters (years of experience, education level, location, must-have skills) to narrow the pile.

The 75% auto-reject statistic conflates two things: (1) the percentage of applicants who don't make it past the first recruiter pass, and (2) the imagined claim that the software made the decision. Recruiters make the decision; the ATS just helps them sort.

The keyword myth and what's actually happening

Almost every ATS published in the last five years does fuzzy semantic matching, not literal string matching. "Python developer" matches "Python software engineer." "B2B SaaS" matches "business-to-business software." "Patient care" matches "clinical care."

This means literal keyword stuffing is unnecessary — and often counterproductive. A resume that lists "Python, Python programming, Python development, Python coding" four ways doesn't get a higher match score; it just looks weird to the recruiter.

What does work:

• Cover the JD's named technologies and methods at least once. If the JD mentions Python, AWS, and Postgres, your resume should contain each of those terms.
• Include the technologies in a bullet, not just the skills line. A skill listed without an example bullet reads as a self-rating, which recruiters at competitive companies discount.
• Use the JD's vocabulary in your bullets. "REST APIs" beats "web services" if the JD says REST APIs. "A/B testing" beats "experimentation" if the JD says A/B testing.

The three formatting rules that actually matter

Every additional formatting rule beyond these is folklore.

Rule 1: Single column

Two-column resumes scramble in most ATS parsers. Workday, Greenhouse, iCIMS, and Taleo all read top-to-bottom, left-to-right — not column-by-column. The result depends on the parser's heuristic: some swallow the right column entirely, some interleave the columns line-by-line, some get the layout right by accident.

The fix is non-negotiable: single column, no exceptions. Templates that look beautiful in two columns will not survive the parse.

Rule 2: No graphics, charts, skill bars, or icons

ATS parsers strip visual elements during text extraction. A skill bar showing "Python: ●●●●○" disappears from the parsed output. The remaining "Python:" with no qualifier reads as an incomplete entry.

Beyond the parsing issue, recruiters at top-tier companies actively filter against skill bars and proficiency dots — they signal an inflated self-assessment with no way to verify. Plain text skills lists are both more parser-friendly and more credible.

Rule 3: Standard section headers

ATS parsers detect section boundaries by looking for known header strings: "Experience," "Work Experience," "Employment," "Education," "Projects," "Skills," "Certifications." Creative section names like "My Story," "Adventures," or "Things I've Built" break the parser's chunking, which means the experience section gets misclassified or merged with the education section.

The fix: use the standard headers. You can be creative in the content of the bullets — not in the names of the sections.

What about file format? PDF vs DOCX

Both major formats parse correctly in modern ATSes if formatted cleanly. The historical advice was "DOCX is safer" — that's largely outdated. Workday, Greenhouse, iCIMS, Lever, and Ashby all parse PDF and DOCX equivalently in 2026.

The remaining edge cases:

• Some legacy Taleo deployments (older Oracle implementations) still parse DOCX more reliably than PDF
• Image-based PDFs (where the resume was scanned or image-rasterized) parse poorly across every ATS
• Heavily designed PDFs from Canva, Adobe Express, etc. sometimes have hidden layout layers that confuse parsers

The pragmatic answer: submit PDF unless the application portal asks for DOCX specifically. PDFs preserve formatting across browsers and printers; DOCX renders inconsistently depending on the recruiter's Word version. If the portal accepts both, PDF is the safer choice.

Why no resume tool can guarantee "ATS pass"

A category of resume tools market themselves on "ATS Pass Rate" or "ATS Score" — implying they can predict whether your resume will make it through a specific company's filter.

This is technically misleading. No consumer resume tool has access to specific ATS parsers. Workday's parsing logic is private. Greenhouse's keyword scoring algorithm is proprietary. iCIMS doesn't publish its match-score formula. The "ATS Pass Rate" reported by these tools is calculated by the tool's own internal scoring algorithm, not by the actual ATS the company uses.

What honest tools (including ours) report instead:

• Resume-JD match score — how well your resume's content maps to the JD's requirements
• Missing keywords list — which JD-named terms aren't currently on your resume
• Format issues — single-column check, standard-header check, graphics check

These are all observable from the resume + JD pair, without needing access to the company's actual ATS. They're correlated with how well the resume will perform in any modern ATS, but no tool can promise specific outcomes against Workday, Greenhouse, or iCIMS specifically.

Practical workflow: applying to ATS-driven jobs

The actual workflow that works, distilled from what recruiters and ATS engineers actually look at:

1. Start with a clean single-column resume — standard headers, no graphics, plain text skills section
2. Tailor the skills line to the JD — JD-matching keywords first, others trimmed
3. Rewrite 2-4 bullets to use JD vocabulary — natural integration, no stuffing
4. Quantify every bullet that has a number available — actual numbers, not invented ones
5. Save as PDF (unless portal asks DOCX)
6. Verify the parse before submitting — open the PDF in a basic text-extraction tool to make sure your text is readable

Step 6 is the one most students skip. The fastest way to do it: open your PDF, select all (Ctrl/Cmd + A), copy, paste into a plain-text editor. If the text comes out clean and ordered, the parse will work in any modern ATS. If it's garbled or missing sections, the resume needs reformatting.

Common ATS-related questions students ask

Beyond the FAQ at the bottom of this post, these are the questions students ask most often after reading ATS guides:

"How do I know which ATS a specific company uses?" Look at the URL when you land on the application page. Workday URLs contain "myworkdayjobs.com." Greenhouse URLs contain "greenhouse.io" or "boards.greenhouse.io." Lever URLs contain "lever.co." iCIMS URLs contain "icims.com." This isn't critical information — the formatting rules are the same across all major ATSes — but it's good to know.

"Should I include a 'References available upon request' line?" No. It's outdated and wastes space. Recruiters know references are available; they don't need a sentence about it.

"What about LinkedIn URLs and personal sites?" Include both if they're real and current. ATSes parse URLs into the candidate profile, and recruiters do click them. An empty or out-of-date LinkedIn is worse than no link.

"How do I handle gaps in my work history?" Don't lie about dates. ATSes flag overlapping or missing dates as data-quality issues, and recruiters check timelines manually. If you have a gap, address it briefly in the cover letter or summary; don't try to hide it through formatting tricks.

Where this fits in the broader job search

ATS optimization is one piece of the application puzzle. The rest:

• Tailoring — see How to tailor your resume to a job description for the keyword analysis recruiters actually run
• Bullet writing — see What is the STAR method? for the framework that makes bullets read as substantive
• Volume — for any role you actually want, plan to apply to enough roles that the variance evens out (typical 8-15% callback rate on tailored entry-level applications, though rates vary widely by industry)

The closer you are to writing your first resume, the more you'll hear about "the ATS" as the boss-level obstacle. It isn't. The actual obstacles, in order of difficulty: writing bullets that quantify what you actually did, identifying the right roles for your level, and applying to enough of them. Optimize for those first; the ATS-friendly formatting takes 15 minutes and is mostly a one-time fix.