ATS Resume Guide 2026: How Workday, Greenhouse, and AI Screeners Actually Read You

Most articles about the ATS resume still describe a piece of software that barely exists anymore. The 2017 advice (stuff in keywords, avoid columns, use Arial) is half right, half outdated, and silent on the part that actually matters in 2026: AI-powered summarizers now sit on top of every major applicant tracking system, and they read your resume very differently from the keyword scanners of a decade ago. If you want yours to land in front of a recruiter rather than in a silent reject pile, you need to understand both layers.

This guide walks through what an ATS resume is, how the big systems (Workday, Greenhouse, Lever, Taleo, iCIMS, Ashby) actually parse your file, the formats and elements that quietly kill your chances, and a before-and-after rewrite that shows the difference. No fluff, no "use a clean font" platitudes you've already read ten times.

What is an ATS resume, really?

An ATS resume is a resume formatted so an applicant tracking system can pull every important field (your name, contact info, job titles, dates, skills, education) into structured database records without losing or scrambling anything. That's it. It isn't a separate document, a different style, or a magic template. It's just a resume that survives the parser cleanly so a recruiter sees an accurate profile when they search the system.

The systems themselves are recruiting databases. Companies use them to receive applications, store candidate records, search for matches, and move people through interview stages. Workday, Greenhouse, Lever, Taleo, iCIMS, SmartRecruiters, BambooHR, and Ashby are the names you'll meet most often in 2026. Each one parses your resume slightly differently, which is exactly why a layout that looks perfect on screen can come out garbled inside the database.

The Jobscan team has tracked Fortune 500 adoption for years and pegs ATS use at over 98 percent of those companies. Among smaller employers, adoption sits closer to 75 percent. So if you're applying to a job posted online in 2026, assume an ATS is involved.

How different ATS platforms actually parse your resume

Here's where most ATS resume guides go quiet. They lump every system together, but the parsing engines are not the same product. Knowing which system a company uses (you can usually tell from the application URL) tells you what to worry about.

Workday

Workday is the giant. Walmart, Target, Bank of America, Salesforce, and most of the Fortune 100 run it. Its parser is strict and old-school. It pulls structured fields by reading section headers, then asks you to re-confirm everything in a long manual application form. If your resume PDF has columns, fancy graphics, or non-standard headers, Workday's parser drops fields silently and you end up retyping your whole job history. The system does keyword search across the parsed fields, not the raw file. So clean section labels ("Work Experience", "Education", "Skills") matter a lot. Save as PDF, single column, plain text headers, and you're fine.

Greenhouse

Greenhouse is what most mid-stage tech companies (Airbnb, Pinterest, HubSpot) use. Its parser is more forgiving than Workday's, but Greenhouse leans heavily on the recruiter manually screening. Tags and custom scorecards drive their workflow more than automated keyword filters. So an ATS resume that lands well in Greenhouse needs to look strong to a human in the first six seconds, because that's mostly who's reading it.

Lever

Lever is similar to Greenhouse in feel and audience (Netflix, Eventbrite, Yelp have all used it). Its parser handles modern formats (DOCX and PDF) well. Lever surfaces a candidate-friendly summary view to recruiters, with parsed work history, education, and a one-line snapshot of recent roles. If your resume's most recent title isn't crystal clear, Lever's snapshot can mislabel you. Keep the most recent role at the top in clean reverse-chronological order.

Taleo (Oracle)

Taleo is the system everyone loves to hate. It's old, owned by Oracle, and still used by huge enterprises and government contractors. Taleo's parser is the worst of the bunch for fancy formatting. Tables, text boxes, columns, and headers/footers all confuse it. If you're applying to a Taleo employer, strip your resume down to the absolute basics. Use a single-column DOCX, standard headings, and no creative styling. Taleo also gives the most weight to keyword matches in its automated rankings, which is where the old "keyword stuffing" advice came from.

iCIMS

iCIMS is mid-market enterprise (Microsoft has used it, plus thousands of healthcare and retail employers). The parser is decent. iCIMS is heavy on configurable workflows, which means each employer's setup varies. The safe bet: clean DOCX or PDF, structured headings, and let the file do the work.

Ashby

Ashby is the new kid (Ramp, Linear, Notion). It's an AI-native ATS with strong parsing and an emphasis on pipeline analytics. Ashby handles modern resume formats well and surfaces a parsed summary alongside the original PDF for recruiters. Of all the systems, Ashby is the most forgiving on layout, but the AI summary is also the most influential on whether you get a first look. Make sure your headline (top of resume, current role, one-line summary) reads cleanly.

The 2026 twist: AI summarizers screen before recruiters do

Here's the change you need to know about. Every major ATS now ships with, or integrates, an AI screening layer. Workday added Recruiter Agent. Greenhouse rolled out AI sourcing tools. iCIMS has Copilot. Ashby's whole product is built around AI summaries. Even smaller systems now plug into screening services like Eightfold, Paradox, or in-house GPT-based extensions.

What these AI layers do: they read every incoming ATS resume, generate a structured summary (years of experience, current title, skills, education, location), and produce a fit score against the job description. Recruiters then see the AI's take alongside the resume, and most of them admit (quietly) that they read the summary first. If the AI mislabels you, you're starting at a disadvantage before a human eyeball even touches the file.

So an ATS-friendly resume in 2026 isn't just "parser-readable". It also has to be AI-readable. The good news is that the same things that help one help the other: clear section labels, plain text job titles, dates in standard formats, no images of text, no fancy column tricks. The AI is reading the same parsed output the legacy ATS produced, just with a smarter brain on top.

The format kill-list: stuff that tanks your ATS resume

This is the part that costs most candidates real interviews. Each item below has a parser-level reason it fails, not just a vague "avoid this".

Multi-column layouts. Two-column resumes look great on paper. Parsers read top-to-bottom, left-to-right. They often slice your two columns into one stream that interleaves your skills with your job titles. Result: garbled records. Workday and Taleo are the worst offenders here.

Headers and footers. Contact info in the header? Half of parsers ignore headers entirely. Your phone number and email vanish. Move them into the body of the document, top center or top left.

Text boxes. Anything inside a text box (in Word or Google Docs) is invisible to many parsers. Same with shapes containing text. Use straight paragraphs and bullets only.

Images and logos. A photo, a company logo, an icon next to your phone number. None of it parses. Worse, some systems flag image-heavy files as low quality and downrank them.

Tables. A table for skills, ratings, or contact info breaks parsing in ways that depend on the system. Even the modern parsers stumble. Replace tables with line-based formatting.

Fancy fonts. Stick to Arial, Calibri, Helvetica, Times New Roman, Georgia, or Garamond. Custom fonts get substituted at parse time and sometimes scramble characters. Sizes 10 to 12 for body, 14 to 16 for headers.

PDFs from design tools. A PDF exported from Canva, Figma, or InDesign is often built from images of text rather than actual text. Parsers see nothing. If you must use a designed template, export as DOCX, or copy the text into Word and re-export.

Non-standard section labels. "Where I've Been" instead of "Work Experience". "My Toolkit" instead of "Skills". Parsers look for known headers. Be boring on labels and creative in the bullets.

Symbols and special characters. Ampersands inside job titles, em dashes, smart quotes, fancy bullet glyphs. Most parsers handle these now, but Taleo and older Workday tenants still misread some of them. Use plain dashes, straight quotes, and standard bullets.

Acronyms with no spell-out. "PMP" by itself works for keyword matches. "Project Management Professional (PMP)" works for both keyword search and AI fit scoring. Always include both forms the first time.

The keyword density myth, debunked

The old advice: stuff your ATS resume with keywords until you hit a magical 70 to 80 percent match rate against the job description. Keyword scanners loved it. Recruiters hated it. AI summarizers in 2026 actively penalize it.

Here's what's actually happening under the hood. Older keyword-only systems (Taleo at its dumbest setting, some legacy SAP SuccessFactors deployments) really did rank candidates by raw keyword count. So a candidate who shoehorned "customer success" 14 times into a resume could outrank a better candidate who used the phrase three times. That trick still works at a handful of laggard employers.

Everywhere else, AI screening calculates fit using semantic similarity. It groups synonyms ("client success" and "customer success" register as similar). It weights the context around a phrase, not just whether the phrase appears. And it flags suspicious density. A resume that crams "data analysis" 11 times into 600 words gets a lower fit score, not a higher one, because the AI reads it as low-quality content.

So the right keyword approach for an ATS resume in 2026: use the exact phrases from the job description three to five times across your resume, in genuine context (a bullet describing what you actually did), and once in your skills section. That's plenty. Anything more is counterproductive.

Before and after: an ATS resume rewrite

Concrete is better than abstract. Here's a real-world rewrite, with the parser problems flagged.

Before (the version that gets filtered)

Two-column PDF exported from a design tool. Header bar with name and contact info. Skills column on the left with star ratings (graphics). Job titles in italic small caps. Section labels: "My Story", "Tools I Love", "Education & Training".

Bullet sample: "Spearheaded transformation of customer success workflow leveraging cutting-edge methodologies to deliver synergistic outcomes across the org."

What goes wrong: Workday and Taleo lose half the contact info (header). The skills column reads as a jumbled stream because parsers go left-to-right. "My Story" doesn't register as a work history label, so dates and titles end up in a generic "other" bucket. The AI summary mislabels the candidate's current role. The bullet is jargon-soaked, scores low on AI fit, and doesn't show actual outcomes.

After (the version that lands)

Single-column DOCX. Name and contact info as plain text at the top. Standard section labels: "Professional Summary", "Work Experience", "Skills", "Education". Job titles bold, in standard font.

Bullet sample: "Redesigned the customer success onboarding workflow at a 200-person SaaS company, cutting average time-to-first-value from 21 days to 9 and lifting 90-day retention from 78 to 91 percent.

What goes right: Every parser pulls clean records. The AI summarizer correctly tags the candidate as a customer success operations leader. The bullet uses the right keywords ("customer success", "onboarding", "retention") in genuine context, with concrete metrics, which both the AI fit score and the eventual recruiter respond to.

Same person, same role, two very different outcomes.

How recruiters actually use the ATS output

Worth being honest about what the recruiter's screen looks like, because most candidates picture it wrong.

When a job opens, the recruiter logs into Workday or Greenhouse and sees a list of inbound applicants, ranked by some combination of submission date, AI fit score, and source. They click into the top 20 to 50 records. For each, they see a parsed summary at the top ("Sarah Chen, Senior Product Manager, 7 years experience, MBA, San Francisco") and the original resume below.

They spend roughly six to ten seconds on the summary, glance at the resume to confirm, and either advance or reject. If the AI summary is accurate and the headline role is a clean match, the recruiter clicks "advance". If the summary is garbled ("Title: unknown, Years: 0, Skills: parsing error"), they almost never go back to read the original. They just move on.

This is why your ATS resume's job is to feed the parser cleanly, not to look prettier than the next person's. The pretty version often loses precisely because it confuses the machine, and the machine is the gatekeeper.

A five-step ATS resume template checklist

Run your current resume through this list. Each item maps to something a real parser actually checks.

1. Single-column layout. Top to bottom, no sidebars. If you have a "skills" sidebar, move skills into a section after work experience.

2. Standard section labels. "Professional Summary", "Work Experience" (or "Experience"), "Skills", "Education", "Certifications". Don't get creative.

3. Plain-text contact info at the top. Name on its own line, then email, phone, city/state, LinkedIn URL. No header bar, no icons.

4. Reverse-chronological work history. Most recent role first, with company, title, location, and dates (Month Year format) on consistent lines. The AI summary reads this layout best.

5. DOCX as the safe default. If the application accepts both, send DOCX. PDFs work for most modern parsers, but DOCX is universally readable. Save the file as FirstLast_Resume.docx for easy recruiter handling.

If you want a deeper template walkthrough, our functional resume guide covers when to break from chronological order, and our resume font guide goes into which typefaces actually parse cleanly across all the major systems.

Keywords without stuffing: the 2026 method

The right way to handle ATS resume keywords now looks like this. Pull the job description. Highlight the five to eight phrases that show up in the requirements and responsibilities sections (not the company-culture preamble). Map each phrase to a real bullet in your work history where you genuinely did the thing. Rewrite that bullet so the phrase appears in context, paired with a metric or outcome.

Example. Job posting says "experience with cross-functional stakeholder management". Your existing bullet: "Worked with multiple teams to launch product features." Better: "Led cross-functional stakeholder management across product, engineering, and design to launch four features in 2025, lifting weekly active users 18 percent."

Same fact, but now the AI fit scorer sees the exact phrase, the recruiter sees a tangible outcome, and you've boosted both signals at once. Do that for five to eight phrases per application and you've done more than 90 percent of candidates ever do.

Frequently asked questions about ATS resumes

How do you know if your CV is ATS friendly?

Two quick tests. First, copy and paste your resume from the PDF into a plain text editor. If the text comes out clean, in the right reading order, with no garbled characters, the parser will likely handle it fine. If it scrambles or drops sections, fix the layout. Second, run it through a free ATS scanner like Jobscan, Resumeworded, or our own resume review service. These tools simulate the parsing step and flag specific issues.

What does an ATS resume look like?

Single column, plain text, standard section headers (Summary, Experience, Skills, Education), no images or graphics, reverse-chronological, contact info at the top in plain text. It looks, frankly, a little boring. That's the point. The visual elegance lives in the writing, not the styling.

Is 75 a good ATS score?

It's okay, not great. Most ATS scanner tools (Jobscan, Resumeworded, Enhancv's checker) consider 80 percent and above strong, 70 to 80 acceptable, and below 70 worth fixing. A 75 means your resume hits most of the job description's signals but is missing a few keywords or has a couple of formatting issues. Tighten the bullets and you can usually push it to 85 in 15 minutes.

What's a good ATS score for a resume?

Aim for 80 percent or higher on a Jobscan-style match against the specific job description. Above 90 is excellent. Below 70 means the resume isn't tailored enough, or the formatting is breaking the parser. The score is per-job, not absolute, so a strong resume can score 90 for one role and 60 for another.

Do I need a different ATS resume for every job?

You need a tailored version, not a totally different document. Start from a master resume that has every role, project, and accomplishment. For each application, copy the master, trim to the most relevant 10 to 15 bullets, and adjust the wording in the summary and skills section to mirror the job posting's exact phrases. Twenty minutes per application, max, once you have the master built.

Are PDF or DOCX better for an ATS resume?

Both work for modern parsers. PDF is safer for visual fidelity (the recruiter sees what you intended). DOCX is safer for parsing (every system reads it without exception). If the application form lets you choose, send DOCX. If it says "PDF only", make sure your PDF is text-based, not image-based. You can check by opening the PDF and trying to select the text. If it selects as text, you're fine.

Do ATS systems actually reject resumes automatically?

Some do, most don't. Taleo and a few SAP SuccessFactors setups still auto-reject below a keyword threshold. Workday, Greenhouse, Lever, and Ashby don't auto-reject. They rank candidates and let recruiters do the cutting. So your resume rarely gets nuked by a robot, but it can get buried under a hundred better-tailored ones, which is functionally the same thing.

Can I use ChatGPT to write my ATS resume?

You can, with care. ChatGPT (or Claude, or Gemini) is good at rewriting bullets to match a job description's phrasing. It's bad at inventing facts, and AI screeners on the recruiter side are getting better at flagging generic AI-written prose. Use AI to refine your wording. Don't use it to fabricate experience or generate the entire resume from scratch.

The bottom line on ATS resumes in 2026

An ATS resume isn't a separate species of document. It's a regular resume that's been formatted to feed cleanly into the parser the employer happens to use, with content tuned to score well against both the AI fit summary and the human recruiter who reads it next. The format rules are mostly the boring ones: single column, plain text, standard headers, real text not images. The content rules have shifted, though. Old-school keyword stuffing now hurts more than it helps, because the AI layer reads context, not just word counts.

If you do five things right (single-column layout, plain section labels, reverse-chronological structure, real metrics in your bullets, and the job posting's actual phrases used in genuine context), your ATS resume will outperform most of the field. The rest is iteration: tweak per job, track which versions get callbacks, and keep refining.

If your current resume keeps getting filtered and you can't tell whether it's the format, the keywords, or the content, our team rebuilds ATS resumes for a living. Our resume writing service handles the parser-friendly formatting and the bullet rewrites in one pass, with a tailored version per role you're targeting. We've shipped thousands of these across Workday, Greenhouse, Lever, Taleo, iCIMS, and Ashby, and we know exactly which formatting choices each system rewards.