How ATS Systems Read Your CV — and How to Pass (2026)

Before a human ever sees your CV, software does. Nearly every large employer runs an applicant tracking system (ATS), and mid-size companies increasingly do too. The ATS parses your CV into a database record, and recruiters search that database. A CV the software can't read correctly is invisible, no matter how strong your experience is.

An ATS is not a mysterious judge, though. It's a parser with mechanical, predictable rules. This guide explains what actually happens to your file, and the specific choices that decide whether you're found.

What an ATS actually does with your file

When you upload a CV, the system does three things:

1. Parses the document, extracting raw text and sorting it into fields: name, contact details, work history, skills, education.
2. Indexes it: your CV becomes a searchable record in the company's candidate database.
3. Matches and ranks: when a recruiter searches ("project management" AND "SQL"), or when the system scores candidates against a job description, your record either surfaces or it doesn't.

Two myths are worth correcting here. An "ATS rejection" is usually not software rejecting you — it's your CV never surfacing in a recruiter's search, because the parser missed or mislabeled your information. And there is no single "ATS": Workday, Greenhouse, iCIMS, Taleo and Lever all parse slightly differently, so the safe strategy is formatting that every parser handles.

What the recruiter on the other side actually sees

Your CV does not arrive on a recruiter's desk as a document. It arrives as a row in a list.

Open a requisition with two hundred applicants and the first screen is a table: name, current title, location, years of experience, and a short snippet of text with the search terms highlighted. Recruiters scan that table. The file you spent a weekend formatting sits one click away, and most rows never get the click.

Three things follow.

The fields at the top of your record carry more weight than anything further down. Your current title is one of them. If you are a delivery manager applying for a programme manager role, the row says "Delivery Manager", and the judgement about whether that is close enough happens in someone's head in about a second, without your CV ever being opened. A title line under your name stating the role you are applying for, sitting alongside your real job title, puts both strings into the record and removes the guesswork.

The record is assembled from two sources, and they can contradict each other. Part of it is parsed from your document. Part of it is whatever you typed into the application form. When a form asks for your current employer and your years of experience after you have already attached a CV containing both, it is not being redundant. Those typed fields are usually what populates the searchable record and the filters sitting on top of it. Leave them blank and you drop out of searches whose criteria you actually meet.

Recruiters search the way you would expect anyone with a search box to search. Most ATS platforms accept boolean queries, something like "programme manager" AND (prince2 OR "agile") NOT intern, matched literally against your record. This is the real reason to use the posting's exact words. It is not a superstition about pleasing robots. It is about being findable by a person typing terms into a field.

One practical consequence is worth stating plainly: the snippet the recruiter sees is drawn from wherever your matched terms appear. If your only mention of the searched skill is buried in a list at the bottom of page two, that is the sentence they read as your introduction. Terms attached to a result near the top of your CV give you a better first line than terms sitting in a keyword dump.

Formatting: where most CVs fail

Layout: one column wins

Single-column layouts parse more reliably than two-column ones. Worse, some parsers read two-column PDFs straight across, top to bottom, merging unrelated text from both columns into nonsense. If you use a designed template, keep a plain single-column version for applications.

Section headings: standard beats creative

Parsers locate your information by recognizing headings. "Work Experience", "Education", "Skills" are recognized everywhere. "Career Journey", "Where I've Made an Impact", or icons instead of words can cause entire sections to be skipped or filed under the wrong field.

Headers, footers, tables, and graphics

Text placed in the document's header or footer is lost by many parsers, so never put your name or contact details there. Tables, text boxes, logos, skill-bar graphics, and photos are at best ignored and at worst scramble the text around them. Decorative bullet characters can also confuse parsers; stick to plain bullets.

Dates: month + year, always

Most systems expect dates in MM/YYYY form. If you list only years, some parsers assign January 1st by default, which can silently stretch or shrink your employment gaps. Write "03/2021 – 11/2024", not "2021 – 2024".

File format

Submit .docx or a text-based .pdf. Avoid .txt, .rtf, and .pages, which some systems reject outright. Two traps: resume builders that export your CV as an image (a .jpg in a .pdf wrapper, unreadable to a parser), and scanned PDFs, which require OCR most ATS platforms don't reliably run. Quick self-test: open your PDF and try to select the text with your cursor. If you can't select it, a parser can't read it.

Keywords: how ranking actually works

Which terms matter depends on the role. We have listed the families that recur in architect and IT leadership postings in our guide to CV keywords for architects, and the ones that recur in infrastructure postings in the guide for system engineers and sysadmins. The mechanism, though, is the same everywhere. Recruiters search the ATS database the way you search Google, and the match is literal. If the job description says "Salesforce" and your CV says "CRM software", you don't match. If they search "project management" and you wrote "managed projects", you may not surface.

What works:

• Mine the job description. Highlight the job title, hard skills, tools, and certifications it mentions, especially anything mentioned more than once. Those are the search terms.
• Write "project management" if that's their term, then add your own phrasing alongside it. Spell out acronyms once ("Applicant Tracking System (ATS)") so both forms match.
• Put the terms where they carry weight: your title line, skills section and experience bullets, attached to real achievements rather than floating in a keyword dump.
• Don't stuff. Aiming to cover roughly 70–80% of the posting's genuine keywords keeps you searchable without tripping recruiters' (very human) spam radar. White-text keyword stuffing is detected by modern systems and reads as fraud when a human opens the file.
• Tailor every application. One generic CV cannot match every search. Adjusting your skills section and top bullets to each posting takes minutes and decides whether you surface at all. Our 10-minute tailoring routine is the shortest version that works.

A 60-second ATS self-check

1. Single column, no tables, no text boxes?
2. Name and contact details in the body, not the header?
3. Standard section headings?
4. Dates as MM/YYYY everywhere?
5. Text selectable in the final PDF?
6. Job title and top skills from the posting present, in their exact words?

If you can answer yes six times, your CV will survive parsing on every major platform. What's left is whether your content ranks well against a specific job description, which is what an ATS score measures.

FAQ

Do ATS systems automatically reject CVs?

Rarely. Automatic rejection is usually limited to knockout questions ("Do you have the right to work in this country?"). The far more common failure is silent: your CV parses badly or lacks the searched keywords, so it simply never appears in the recruiter's results.

Is PDF or Word better for ATS?

Both .docx and text-based PDFs parse well on modern systems. What matters is that the PDF contains real text, not an image of text. If the posting specifies a format, follow it.

Should I use an "ATS-friendly template"?

Any clean single-column layout with standard headings is ATS-friendly. You don't need a special product. Be careful with visual resume builders: some export designs that look great and parse terribly.

Does applying through LinkedIn or a job board change how my CV is parsed?

It can, and rarely in your favor. Quick-apply flows often hand the employer a record built from your profile rather than from the document you spent hours on, and some boards re-parse and reformat the file before passing it along. Where the company runs its own careers page, applying there is the version you control. And fill in the application form properly even when it duplicates your CV: the fields you type usually become the record the recruiter searches, so a blank field is a blank field, whatever your attachment says.

How do I know what my ATS score is?

An ATS score estimates how well your CV parses and how strongly it matches a given job description. Job4Fit's free CV Checkup gives you a score with a per-section breakdown: what parses, what doesn't, and which sections are weakest against the keywords a recruiter would search.