ATS & applicant tracking 10 Jun 2026 CvLaunch 12 min read Updated 02 Aug 2026

How to Write an ATS-Friendly CV in 2026

Also available in: TR ES DE FR
How to Write an ATS-Friendly CV in 2026

Most CVs are never read by a human. Before a recruiter opens your application, it usually passes through an Applicant Tracking System (ATS): software that parses, scores, and filters candidates. If the software cannot read your CV, you are rejected before anyone knows you exist.

This guide explains what an ATS actually does, which formatting choices break it, how to match a job description without stuffing keywords, and how to check your CV before you send it.

What an ATS actually does

An ATS is a database with a parser attached. When your file arrives, the software tries to pull structured fields out of an unstructured document: your name, contact details, each employer, each job title, the dates you worked there, your education, and your skills. Those fields go into a record that a recruiter can search and sort.

Two separate things get you filtered out, and they need different fixes:

  • Parsing failures. The software cannot work out your layout, so fields land in the wrong place or come back empty. Your ten years of experience can be sitting in the file and still show up as a blank work history.
  • Keyword gaps. Your CV parses cleanly but does not contain the terms the role is defined by, so you rank low against other applicants.

A CV that fails on parsing is invisible. A CV that fails on keywords is visible but unconvincing. You have to solve both.

What an ATS does not do

A lot of advice online treats the ATS as a robot that auto-rejects people. That is mostly wrong, and believing it leads to bad decisions.

  • It does not usually reject anyone by itself. In most systems a recruiter still opens the shortlist. The ATS decides what order you appear in and whether you appear at all in a filtered search.
  • It does not understand meaning the way a person does. It matches strings and patterns. "Managed a team of six" and "line management experience" are obviously the same thing to a human and not necessarily to the parser.
  • It does not read your design. Effort you put into visual polish is invisible to it, and some of that polish actively hurts you.

So the goal is not to write for a machine instead of a person. It is to write for a person in a format the machine can transmit.

How your CV gets parsed, step by step

Knowing the order helps you see why certain mistakes are fatal:

1. The file is converted to plain text. Anything that is not text, such as an icon, a logo, or a chart, is dropped at this stage. 2. The parser looks for section boundaries, usually by matching headings against a list of expected labels. 3. Inside each section it looks for repeating patterns: a job title near a company name near a date range. 4. Extracted values are written into database fields. 5. The record is scored against the job requisition, mostly on skills and job titles.

Every rule below maps to one of those steps.

Layout rules that decide whether you get parsed

Use a single column. This is the single most important rule. A parser reads across the page. When you put a skills sidebar next to your work history, the text on the same visual line gets interleaved, and you end up with sentences like "Senior Analyst Python 2021-2024 SQL Acme Ltd." Once that happens, nothing downstream is reliable.

Keep text out of images. A name in a designed banner, skills shown as icons, or a rating displayed as filled circles all vanish in step one. If a fact matters, it has to exist as selectable text.

Avoid headers and footers. Many parsers ignore these regions entirely. Contact details are the most common casualty, which means a strong CV arrives with no way to contact you.

Skip tables for layout. Some modern parsers handle simple tables, plenty do not, and you cannot tell which one is on the other side. Nested tables are worse.

Use standard bullet characters. A plain dash or round bullet is safe. Decorative glyphs and emoji can come through as noise or vanish.

Choose a common font. Anything widely installed is fine. Unusual fonts occasionally cause character substitution when the file is converted.

Do not put anything in white text. Hiding a block of keywords in white on white was a trick years ago. Systems flag it now, and a recruiter who spots it will reject you outright.

PDF or Word?

Send a PDF unless the advert or the application form specifically asks for a .docx file. Modern systems handle PDF well, and it guarantees the recruiter sees the layout you built.

Two exceptions worth knowing. If the PDF was produced by scanning or exporting an image, it contains no text at all and will parse as an empty document, so always check that you can select and copy the text in your own file. And if an application form gives you a plain text box instead of an upload, paste plain text and accept that the formatting will be lost.

Section headings the parser expects

The parser finds sections by matching your headings against known labels. Creative headings break that match.

Use conventional ones: Experience or Work Experience, Education, Skills, Certifications, Languages. Avoid My Journey, Where I Have Made an Impact, or Toolbox. If you want personality, put it in the writing, not in the structural labels.

Order matters too. Put the section that makes your case first. For most people that is experience. For a recent graduate it is education.

Structure every role the same way

Consistency helps the parser find the repeating pattern, and it helps a recruiter skim. For each position include:

  • Job title
  • Company name
  • Location, if relevant
  • Start and end dates as month and year
  • Three to five bullet points

Write dates in a consistent, unambiguous format throughout, such as 03/2021 to 06/2024. Mixing "March 2021", "2021-03" and "Spring 2021" in one document gives the parser three problems to solve instead of one.

If you are currently in the role, write Present rather than leaving the end date blank.

A formula that works for every bullet

Weak bullets describe duties. Strong bullets describe outcomes. A reliable pattern is:

Action verb + what you did + the result, with a number where one exists.

Compare:

  • Responsible for managing social media accounts.
  • Grew Instagram following from 2,000 to 15,000 in 8 months, increasing inbound leads by 40%.

The second is specific, measurable, and survives a six second skim. Start with verbs that carry weight: built, led, reduced, negotiated, automated, launched, recovered. Avoid opening with "Responsible for" or "Helped with", which describe a position rather than a contribution.

Match the keywords the job description uses

ATS scoring leans heavily on matching. The job advert is the answer key, so read it as one.

Pull out the terms that define the role: tools, methods, certifications, and the job title itself. Then use the employer's exact wording somewhere in your CV, provided it is true of you. If the advert says project management, the phrase coordinated projects may not match it. Write project management and let your bullets show what that meant in practice.

A few practical points:

  • Include both the spelled out term and the abbreviation the first time, for example search engine optimisation (SEO), because the advert may use either.
  • Mirror the job title if it is a fair description of what you did. If your internal title was Growth Ninja and the advert says Marketing Manager, write Marketing Manager (internally: Growth Ninja).
  • Watch spelling variants across regions, such as organisation and organization, and use the variant the advert uses.

Doing this per application is a short routine in itself: see how to tailor your CV to a job description.

Where to put keywords, and where not to

Put them inside your experience bullets, where they come with evidence. A skills list is useful as a summary, but a term that appears only in a list and never in your history reads as a claim without proof, and an interviewer will test it.

Never paste a block of keywords at the end of the document, hidden or not. It does not reliably help scoring and it is obvious to the human who reads next.

The list itself still has to be built with care: what skills to put on a CV covers how to choose and group them.

Quantify what you can

Numbers prove impact and survive skim reading. Add percentages, amounts, team sizes, volumes, and timeframes wherever they genuinely exist: revenue influenced, hours saved, users served, tickets resolved, error rate reduced, time to delivery cut.

If you cannot measure the outcome, measure the scope. "Supported 40 stores across three regions" is concrete even without a result attached. Do not invent figures. A number you cannot explain in an interview is worse than no number.

Keep it focused

Aim for one to two pages of relevant content. Two pages is normal and expected for anyone with several years of experience, and length has never been the reason an ATS filtered someone out.

Cut roles older than ten to fifteen years unless they are directly relevant, and compress early jobs to a single line. Every remaining line should earn its place against the advert in front of you.

How many pages that actually means, and what goes first when you have to cut, is set out in how long should a CV be.

Formatting traps that break parsing

A short checklist of the mistakes that appear most often in CVs that parse badly:

  • Two column layout with a sidebar
  • Contact details in the header
  • Skills shown as star ratings or progress bars
  • Job titles and companies inside a table
  • Section headings styled as images
  • A photo placed over text
  • Dates written inconsistently
  • A file exported as an image based PDF

For the wider list, including the content mistakes that cost interviews, see 11 common CV mistakes.

ATS myths that will not die

"Never use a two page CV." Length is a readability question, not a parsing one.

"You must hit an exact keyword percentage." No public system publishes a target, and writing to an invented threshold produces unreadable text.

"Plain text files are safest." They parse fine and read poorly. You lose all emphasis and structure for a human reader, which costs you more than it gains.

"A photo will get you auto rejected." Photos are not filtered automatically. They are simply ignored by the parser, and in some countries recruiters prefer you leave them out for fairness reasons. Follow the local norm.

A copy-ready ATS-safe CV outline

Full Name
City, Country | phone | email | LinkedIn URL

PROFILE
Two or three lines: your role, years of experience,
your specialism, and the value you bring.

EXPERIENCE
Job Title
Company Name, City | 03/2021 - Present
- Achievement with a number
- Achievement with a number
- Achievement with a number

Job Title
Company Name, City | 06/2017 - 02/2021
- Achievement with a number
- Achievement with a number

EDUCATION
Degree, Subject
Institution | Graduation year

SKILLS
Grouped by type, comma separated, using the advert's terms

CERTIFICATIONS
Name, issuing body, year

LANGUAGES
Language: level

Frequently asked questions

Does an ATS reject my CV automatically?

Usually not on its own. It ranks and filters, and a recruiter works from the result. The practical risk is not a rejection email from a machine, it is never appearing in the search a recruiter runs.

Can an ATS read tables and columns?

Some can, many cannot, and you have no way of knowing which system a given employer uses. Because the failure is silent and total, the safe choice is to avoid both for anything structural.

Should I include a photo?

It depends on the country, not on the software. Photos are conventional in much of continental Europe and discouraged in the UK, Ireland, the US, and Canada. The parser ignores the image either way.

Is a two-page CV a problem?

No. Two pages is standard once you have a few years of history. Relevance matters far more than page count.

Do headers and footers really get ignored?

Often enough that you should not risk it. Keep your contact details in the body of the document, at the top.

How do I know whether my CV passed?

You cannot see inside an employer's system, but you can reproduce the important part. Convert your own file to plain text and read what comes out. If your job titles, dates, and contact details survive in the right order, most parsers will manage it too.

Test it before you send it

The fastest way to check is to run the file through an analysis tool. CvLaunch parses your CV the way a recruiter's system does, shows you what was extracted, flags formatting and keyword problems against a specific job advert, and tells you exactly what to fix. It takes seconds, it is free, and it needs no sign up.

Ready to land your dream job?

Stop struggling with Word templates. Build a professional, ATS-friendly resume in minutes with our AI Builder.

Create Free Resume