How to Write a CV That Survives ATS Screening in 2026

You applied to eleven roles last month and heard nothing back from nine of them. That silence is rarely personal, and it is rarely about your experience. In most mid-sized and large companies, your CV is read first by software — an applicant tracking system — that parses the file, maps it against the job description and hands the recruiter a ranked list.

Understanding that first reader costs you an afternoon and changes your response rate more than almost anything else you can do. This guide covers what these systems really do (and what they do not), the structure that survives them, and a checklist you can run before every submission.

What an ATS actually does

An applicant tracking system is a database with a workflow attached. When you upload a CV, three things happen in sequence.

1. Parsing. The file is converted to text and split into fields: name, contact details, work history, education, skills. Each job block is separated into employer, title, dates and description.
2. Matching. The parsed record is compared against the requisition — the internal version of the job advert, which usually contains more criteria than the public posting.
3. Ranking or filtering. Recruiters either sort candidates by match score or apply knockout filters: right to work, minimum years, a required certification.

Most rejections at this stage are not the software "binning" you. They are a recruiter opening a list sorted by relevance, reading the first two pages of results, and never reaching page six. Your goal is to be legible enough to be ranked accurately.

Four myths worth deleting

Myth 1: "White text keywords trick the system." Hidden text is detected by every major platform and is treated as fraud. It also looks catastrophic when a recruiter highlights your document.

Myth 2: "You must use a plain black-and-white template." Colour, rules and a tasteful accent are fine. What breaks parsing is layout: text boxes, multi-column grids, tables and headers.

Myth 3: "The system rejects you automatically." Knockout questions reject candidates — usually the ones you answer in the application form, not the CV. The CV affects your rank, not a binary verdict.

Myth 4: "One perfect CV works everywhere." A generic CV ranks middling for everything. Two or three role-specific versions, lightly tailored per application, outperform it consistently.

The structure that parses cleanly

Use conventional section names. Parsers are trained on millions of documents that use the same handful of headings; "My Journey So Far" is charming and unparseable.

Order matters too. For anyone with more than two years of experience, the sequence is: contact details, a four-line professional summary, work experience in reverse-chronological order, skills, education, then extras. Graduates and career changers move education above experience for the first two years only.

Each role block needs four elements

• Job title on its own line — the one the market recognises, not the internal one. If your title was "Growth Ninja", write "Digital Marketing Manager (internal title: Growth Ninja)".
• Company and one-line context. "Brightpath Retail — 400-store grocery chain, £1.2bn revenue." Recruiters cannot be expected to know every employer.
• Dates as MM/YYYY – MM/YYYY. Seasons and years alone create gaps in the parsed record.
• Three to six achievement bullets, not a copy of your job description.

Keywords without keyword stuffing

Keyword matching is fuzzier than it used to be — modern systems use embeddings, so "managed a team of eight" and "line management experience" are recognised as related. But exact terms still carry weight, particularly for tools, certifications and regulated skills.

A repeatable method that takes ten minutes:

1. Paste three adverts for the role you want into one document.
2. Highlight every noun phrase that appears in at least two of them.
3. Sort them into have, partly have and do not have.
4. Make sure every "have" term appears at least once in your CV — in a bullet that shows you using it, not in a bare list.
5. Address one or two "partly have" terms honestly: "Working knowledge of Terraform (built and maintain CI pipelines for three services)."

A skills list proves vocabulary. A bullet that shows the skill producing a result proves capability. Use both, but never let the list be the only evidence.

Spell out abbreviations on first use: "Search Engine Optimisation (SEO)", "Certified Public Accountant (CPA)". Some requisitions search the acronym, some the full phrase, and you cannot know which.

Writing achievement bullets

The difference between a CV that gets interviews and one that does not is usually the bullets. Responsibilities describe the job; achievements describe you doing it well.

Use the pattern action → context → measurable result:

No numbers available? Use scale, frequency or scope instead: the size of the budget, the number of stakeholders, the volume of transactions, the geography covered. "Coordinated a 12-person cross-functional release every fortnight" is concrete even without a percentage.

Formatting traps that break parsers

• Tables. The most common cause of scrambled work history. A two-column table with dates on the left frequently parses as one run-on sentence.
• Text boxes and shapes. Many parsers ignore them entirely, so your skills section can vanish.
• Headers and footers. Contact details placed there are regularly dropped. Put your email and phone in the body of page one.
• Multi-column layouts. Reading order becomes unpredictable; one column is safest.
• Graphics as information. Skill ratings shown as five-dot meters carry no meaning in text. They also invite the question of what three dots means.
• Unusual fonts and ligatures. Stick to Arial, Calibri, Helvetica, Georgia, Garamond or similar. Decorative fonts can produce mis-extracted characters.
• The file itself. Submit .docx unless the employer asks for PDF. A PDF exported from a design tool is often a picture of text, which parses as nothing at all.

Tailoring without rewriting everything

Full rewrites per application are unsustainable. Instead, build a master document containing every role, every bullet and every project you might ever cite — three or four pages is fine, because nobody sends it. For each application you then edit three things only:

1. The professional summary — four lines that mirror the advert's own framing of the role.
2. The bullet order within your two most recent roles, so the most relevant sits first.
3. The skills line, reordered to lead with the tools this employer names.

Fifteen minutes per application, and the match score moves substantially. Keep a simple tracker — role, company, date applied, CV version, outcome — so that after twenty applications you can see which version actually produces interviews.

The pre-submit checklist

• File name: Firstname-Lastname-Role.docx, not cv_final_v7.docx.
• Contact details in the body, including city and country, and a LinkedIn URL that works.
• Two pages maximum for under fifteen years of experience; three is the ceiling for anyone.
• Conventional headings; no tables, text boxes or columns.
• Dates in MM/YYYY, no unexplained gaps longer than three months.
• Every "have" keyword from the advert appears at least once in context.
• At least five bullets across the CV contain a number.
• Copy-paste test passes cleanly into a text editor.
• Proofread by someone else, or read aloud backwards paragraph by paragraph.

None of this makes a weak match strong. What it does is stop a strong match from being invisible — which, judging by the CVs that cross a recruiter's desk every day, is the far more common problem.