How ATS Systems Actually Work (and How to Beat Them in 2026)

If you've spent any time on LinkedIn lately, you've probably seen the headline: "75% of CVs are rejected by ATS before a human ever sees them." It's a great hook. It's also, in the form most people repeat it, basically wrong.

I've spent years on both sides of this — submitting CVs into the void, and sitting inside the recruiter view of Workday, Greenhouse, Lever and a half-dozen others. The reality of what an ATS does is much less dramatic than the doom-scroll version, and once you understand it you stop wasting energy on the wrong things.

This is the long version. Grab a coffee.

What an ATS actually is

Strip away the marketing pages and an ATS is three things stitched together:

• **A database** of every applicant the company has ever received.
• **A parser** that tries to extract structured fields — name, email, job titles, dates, skills — from your CV.
• **A search interface** that recruiters use to find people, mostly through keyword filters and Boolean logic.

That's it. There's no AI brain in most of them deciding "this CV is a 62 out of 100, reject." That feature exists in a handful of enterprise products, and even then most recruiters I know either ignore the score or actively distrust it. What recruiters do trust is their own search.

So the real question isn't "how do I beat the algorithm?" It's "how do I make sure I show up when a recruiter searches, and how do I make sure my CV reads cleanly when they click on it?"

What actually happens when you click Apply

Let's walk through it in slow motion.

1. You upload your CV. The ATS parser reads the file and tries to fill in fields: full name, email, phone, current title, current company, work history, education, skills.
2. If the parser fails — which it does more often than vendors admit — those fields end up empty or garbled. Your "Senior Product Manager at Spotify" might come out as title: "Senior", company: blank.
3. Your CV is stored in the company's database, tagged to that requisition.
4. A recruiter opens the requisition. Depending on volume they see anywhere from 30 to 500 applicants.
5. They almost never read every CV. They search. A typical query is a job title, a couple of must-have tools, and sometimes a city — for example, "product manager" AND (Mixpanel OR Amplitude) AND (London OR remote).
6. The ATS returns a ranked list. The recruiter clicks through the top ones, opens the parsed profile and the original CV side by side, and decides in 8–10 seconds whether to move you to phone screen.

The single biggest reason qualified people don't get interviews isn't an algorithm. It's that they didn't appear in step 5, or their CV looked like nonsense in step 6.

Myth #1: Fancy formatting will get you rejected

Half-true. The ATS won't reject you. But the parser will mangle a CV that uses two columns, a sidebar of icons, decorative headers, text in shapes, or skills shown as filled-in progress bars (those famously parse as nothing).

I once watched a recruiter open a beautiful Canva-designed CV from a candidate who, on paper, was perfect. The parsed profile said: name "Jane", title "blank", company "blank", experience "blank". The recruiter shrugged and moved on. The CV file was right there, attached. He never opened it.

Single column. Standard headings. No tables. No images. That's the rule.

Myth #2: PDFs get rejected, you must use DOCX

Outdated. Modern ATS — Workday, Greenhouse, Lever, Ashby, Workable — handle PDF perfectly well, as long as it's a real text-based PDF and not a scanned image. If you exported it from Word or Google Docs or a CV builder, you're fine. If you scanned a printed page, the ATS sees an image and extracts nothing.

There are still a few legacy systems where DOCX is safer. If a job ad explicitly asks for Word format, give them Word. Otherwise PDF is the modern default.

Myth #3: Stuff your CV with keywords

This one will actively hurt you. Recruiters can spot a keyword-stuffed CV in three seconds. It reads like spam. The "skills word cloud" trick — listing 40 tools in a tiny grid at the bottom — gets you flagged as someone who doesn't know how to communicate.

The right way to handle keywords is to mirror the job description's exact language, but only inside real bullets describing real work. If the JD says "Snowflake", and you've used Snowflake, write "Built revenue dashboards in Snowflake" — not "Snowflake. Snowflake. Snowflake."

Myth #4: There's a magic ATS score

There isn't, in most systems. The "ATS score" you see in tools like ours and competitors is a useful approximation — it estimates how well your CV matches the JD's keywords and structure — but it isn't a number the company sees. It's a coaching tool. Treat it like a fitness tracker, not a verdict.

The seven fixes that actually move the needle

After all that, here's the practical list. None of this is hard. Most of it takes 20 minutes the first time and 30 seconds per application after that.

1. Single-column layout. No tables, no sidebars, no icon headers. If you want a designed CV for sending directly to humans (recruiters at smaller companies, hiring managers via LinkedIn), keep two versions: one designed, one plain.

2. Standard section headings. "Experience", "Education", "Skills", "Projects". Not "Where I've Made Magic Happen". The parser is looking for those exact words.

3. Spell out acronyms once. "Search Engine Optimization (SEO)". Then use SEO afterwards. Recruiters search both ways and you want to match either query.

4. Mirror the JD's wording for tools and titles. If the JD says "B2B SaaS" and you've worked in "subscription software", change your wording to "B2B SaaS" — assuming it's true. If they say "Product Manager" and your title was "Product Owner", consider adding a parenthetical: "Product Owner (Product Manager responsibilities)".

5. Save as PDF from a text source. Not a scan. Not a screenshot pasted into a Word doc.

6. Put the most relevant role first within each section. If you've had two parallel roles and one is more relevant to this job, list it first even if the dates overlap.

7. Don't apply through 11 channels. Pick one. Multiple submissions create duplicate records and look spammy to whoever consolidates them.

Where AI fits in (honestly)

A tool like [ResumAI](/) does fix #4 in 30 seconds — it reads the JD, finds the keywords you can honestly claim from your existing CV, and rewrites bullets so the language aligns. It also flags formatting issues (two columns, missing standard headings) before you submit.

What it doesn't do is invent experience. If you don't have Snowflake on your CV, AI shouldn't add it. Anyone selling you a tool that fabricates skills is selling you a way to fail your first technical screen.

The honest takeaway

Beating an ATS in 2026 is 80% formatting hygiene and 20% keyword alignment. Both are easy. Neither costs money. Once you've done them, you can stop worrying about robots and go back to the actually hard part of the job hunt: convincing a human you'd be good at the work.

If you're feeling stuck, the fastest unblock is usually to put your CV side by side with the JD and rewrite three things — your summary, your skills section, and the bullets in your most recent role — to mirror the JD's language without lying. Do that and your reply rate roughly doubles. We've measured it.