How to write an ATS-friendly CV in 2026

To write an ATS-friendly CV in 2026, use a single-column layout, standard section headings, a normal font, and the exact keywords from the job description, then save it as a PDF. That’s most of the job. The rest is writing a CV a human actually wants to read once the software has done its part.

Now the part nobody selling you a resume template wants to admit: the famous claim that “75% of CVs are auto-rejected by a robot” is made up. It traces back to a company that shut down in 2013 and never published a single study. We read CVs for a living, and we have built tools on the other side of the hiring desk. The truth is more useful than the scare story, and it is the reason most good engineers get filtered out for reasons they could fix in an afternoon.

We are recruiters who were software engineers first. So this guide skips the myths and gives you what actually moves the needle, with examples aimed at tech roles where we spend our days.

Key Takeaways

An ATS sorts and ranks CVs; it rarely rejects them on its own. Only about 8% of recruiters configure content-based auto-rejection. A human still makes the call.

Formatting kills more good CVs than keywords do. Single column, standard headings, no tables or text boxes, contact details in the body, not the header.

Mirror the job description’s exact wording. On average, 52% of a posting’s keywords are missing from applicant CVs, even from qualified people.

For engineers, every bullet should carry a number or a decision: latency cut, uptime held, throughput gained, cost saved.

AI-written CVs now backfire. Around 43% of large employers screen for them, and nearly half of managers bin a CV they suspect was generated. Draft with AI if you want, but make it true and yours.

What an ATS actually does (and the myth to drop)

An applicant tracking system (ATS) is software that collects, parses, and organises job applications. When you upload a CV, it reads the file, sorts your details into fields (work experience, education, skills), and makes you searchable. Recruiters then filter and rank that pool. That’s the whole job. It’s a library, not a bouncer.

So does an ATS automatically reject your CV? Almost never. In interviews with 25 recruiters, 92% said their system does not auto-reject candidates on format or content. Most rejections are still made by hand. Only a small slice of employers, roughly 8%, switch on content-based auto-rejection, and usually only for hard requirements like a missing licence or a “must have 7 of 10 skills” rule.

Here is what actually filters you out: volume. In 2016, about 1 in 7 applicants landed an interview. Today it is closer to 1 in 33. A recruiter with 300 applications doesn’t read 300 CVs equally. They search, sort, and skim. Your job is to surface near the top of that ranked list, then survive a six-second human scan.

If you want roles where the recruiter reading your CV has actually written code, browse our open engineering positions. It’s a faster route than fighting an inbox of 300.

The ATS-friendly CV format (the non-negotiables)

Formatting is where most strong candidates lose. Modern parsers are good, but they still read top to bottom, left to right, and they still choke on anything fancy. Get these right and you have removed 90% of the risk.

Layout and structure

Use a single-column layout. Two-column and sidebar designs get read in the wrong order, so your skills end up scrambled into the middle of a job description. Use standard section headings the parser expects: Work Experience, Education, Skills. Get creative with headings like “Where I’ve Made an Impact” and the software may not register the section at all.

Put your name and contact details in the body of the document, not in the header or footer. Many parsers ignore headers and footers, which is exactly how people end up “applying” with no phone number the system can find.

Fonts, bullets, and the things that break parsers

Stick to a normal font: Arial, Calibri, Georgia, or Times New Roman, at 10 to 12 points. Decorative fonts contain character quirks that some parsers read as gibberish. Use plain round or square bullets, not custom icons, arrows, or checkmarks.

Avoid these, which routinely break extraction:

Tables, cell contents get read out of order
Text boxes, often treated as floating objects and skipped entirely
Icons and graphics, read as junk characters, or they swallow the line
Columns, the classic cause of scrambled output
Headers/footers for key info, frequently ignored

File type and naming

Default to a text-based PDF. Modern systems (Workday, Greenhouse, Lever, Ashby) handle PDF as well as or better than Word, and PDF is the only format that guarantees your layout reaches the recruiter unchanged. Switch to DOCX only if the posting explicitly asks for it. Name the file plainly: Firstname-Lastname-Role.pdf. Keep it to one page if you have under five years of experience, two pages for senior, staff, or principal levels.

Keywords: speak the job description’s language

This is where keywords actually matter, and not in the way the keyword-stuffing crowd thinks. An ATS does not award points for cramming. It helps recruiters find people who match the language of the role. So your job is simple: use the words the employer used.

If the posting says “cross-functional collaboration,” write “cross-functional collaboration,” not “interdepartmental teamwork.” If it says “CI/CD pipelines,” don’t call it “automated deployment workflows” and hope. The system, and the recruiter searching it, looks for the employer’s phrasing. On average, 52% of a job description’s keywords are missing from the applicant’s CV, even when the person is genuinely qualified. That gap is the opportunity.

A few rules that work:

Put your target job title near the top. It is often the first thing a recruiter searches.
Wrap each keyword in a result. “Reduced API latency 40% by tuning Postgres queries” beats a bare “Postgres” in a skills list.
For tech roles, group skills by category: Languages, Frameworks, Cloud, Data, Tools. Keep it to the 10 to 12 that matter for this role, not a 40-item wall.
Do not stuff or hide. White text, invisible keywords, and comma-soup are old tricks. Modern systems surface skills with confidence scores, and any recruiter who opens the file sees the mess instantly.

We covered the recruiter side of this in our guide to what a technical interview should actually test, and the same principle applies to CVs: match the substance, not just the surface.

What recruiters look for after the ATS (the human half)

Pass the parser and you have earned about six seconds of human attention. This is the half the resume-tool blogs skip, because they only know the software. We sit on the hiring side, so here is what we actually do with your CV.

We scan for impact, not duties. “Responsible for maintaining the deployment pipeline” tells us nothing. “Cut deploy time from 25 minutes to 4 by moving the pipeline to GitHub Actions” tells us you understand the work and its value. Every bullet should carry a metric or a clear decision: latency, uptime, throughput, cost, user growth, scope.

For engineers specifically, we look for:

Quantified outcomes in each bullet, not a list of technologies you sat near
A clean skills section grouped by type, matched to the role
Links that prove it: GitHub, a portfolio, a notable project. We do Google you, and for developers that means we check your code.
Honest depth. Listing Kubernetes is easy. We can tell within two questions whether you have run it in production or just added it to pass a filter.

That last point matters more than any formatting tip. As former engineers ourselves, we read CVs the way a hiring manager does, because we have been the hiring manager. We are not matching keywords. We are looking for someone who can do the job and defend the claims on the page.

The 2026 curveball: AI-written CVs and how they backfire

Here is the newest way to get filtered out, and it is one most guides have not caught up with. Writing your entire CV with ChatGPT is now a liability, not a shortcut.

By the first half of 2026, 76% of hiring professionals had seen AI-generated applications, and 49% of hiring managers say they automatically dismiss a CV they believe was written by AI. Enterprise systems shipped AI-content classifiers in late 2025 that downgrade CVs matching generic AI phrasing. Around 43% of large employers now use some form of AI detection. When 100 of 300 applications open with “spearheaded cross-functional initiatives to drive strategic alignment,” recruiters notice the pattern fast.

There is a sharper risk too: invented detail. Generative tools hallucinate. They will happily add a certification you do not hold, a tool you have never touched, or a metric you cannot defend. That is fine until an interviewer asks you to walk through it.

Use AI as a drafting assistant if you like. Then rewrite it in your own words, cut anything you cannot back up in person, and check every number is true. AI fluency is a real asset in 2026, but you show it through outcomes you delivered, not by letting a model invent a career for you.

Your ATS-friendly CV checklist

Run your CV against this before you send it:

Single-column layout, standard section headings (Work Experience, Education, Skills)
Contact details in the body, never in the header or footer
Standard font, 10 to 12 point, plain bullets, no icons
No tables, text boxes, columns, or graphics holding key information
Text-based PDF, named Firstname-Lastname-Role.pdf (DOCX only if asked)
One page under five years’ experience, two pages for senior and above
Exact keywords from the job description, including the job title near the top
Every bullet carries a metric or a decision, not just a duty
Skills grouped by category and trimmed to what the role needs
Every claim is true and defensible in an interview, AI-assisted or not

Beat the parser, win the person

An ATS-friendly CV in 2026 is not about tricking a robot. It is about clearing a simple technical bar so a human can find you, then giving that human a reason to keep reading. Format clean, mirror the job’s language, prove your impact with numbers, and never write a claim you cannot defend out loud.

The “75% auto-rejected” story keeps people optimising for the wrong enemy. The real one is volume and vagueness. Fix the formatting, match the words, quantify the work, and you have already beaten most of the field, because most of the field is still padding bullets and fighting an imaginary bot.

If you are an engineer who would rather have a recruiter who reads your CV the way an engineer does, that’s the whole reason we exist. See our open roles or tell us what you are looking for, and we will only put you forward where you genuinely fit. No CV floods, on either side of the desk.

Frequently asked questions

Does an ATS automatically reject CVs? Almost never. In recruiter interviews, 92% said their system does not auto-reject on format or content. Only around 8% of employers switch on content-based auto-rejection, and usually only for hard requirements like a missing licence. A human still makes the call.

What file format is best for an ATS? A text-based PDF. Modern systems (Workday, Greenhouse, Lever, Ashby) parse PDFs as well as or better than Word, and PDF is the only format that guarantees your layout reaches the recruiter unchanged. Use DOCX only if the posting explicitly asks for it.

How long should my CV be? One page if you have under five years of experience, two pages for senior, staff, or principal levels. Recruiters scanning 300 applications skim, so density and clarity matter more than length.

Should I use AI to write my CV? Use it as a drafting assistant, then rewrite in your own words. Around 49% of hiring managers automatically dismiss a CV they suspect was AI-generated, and 43% of large employers use AI-content detection. Cut anything you cannot defend in person.

What font and size should an ATS-friendly CV use? Stick to Arial, Calibri, Georgia, or Times New Roman at 10 to 12 points. Decorative fonts can be misread by parsers as gibberish. Use plain round or square bullets, not icons or arrows.

How to Write an ATS-Friendly CV in 2026