An ATS-friendly CV is one an Applicant Tracking System can read end to end, split into sections, and match against a job ad. You do not have to give up on design; the text just has to stay machine-readable. This guide walks through it in order, from saving the file to writing the bullets.
An ATS-friendly CV is not a plain-looking CV; it is one the machine can read all the way through. Most of the damage is done at the first step, when you pick the file.
Sidebars, two columns and boxed sections look good in a browser and fall apart in a parser. Text is read left to right, so a line in the left column merges with whatever sits beside it and produces strings that mean nothing. A blank Word or Google Docs document is safer than most paid templates.
Arial, Calibri, Helvetica and Times decode correctly everywhere. Leave font embedding on when you export the PDF; without it, accented characters are encoded wrongly and a word comes out mangled in the extracted text - and no search for the correct spelling will ever find you.
Open the saved PDF and try to select a word with your mouse. If you cannot, the document is just a picture and the system will read nothing at all. If the ad explicitly asks for .doc or .txt, give it what it asks for; otherwise PDF is the safest choice.
A parser splits your CV by its headings. A heading it does not recognise means everything under it goes unclassified - which is the same as not having written it.
Experience (or Work Experience), Education, Skills, Projects, Certifications, Languages. Creative headings like "My Journey" or "What I Can Do" break the match. Put the creativity in the bullets, not in the labels.
Name, phone, email, city and LinkedIn belong at the top, in the normal flow of the page. Contact details typed into a Word header sit outside the page body and are invisible to many parsers; the record comes back flagged as missing contact information.
"01/2023 – 06/2025" or "January 2023 – June 2025" - whichever you pick, never change it mid-document. Mixed formats lead to your total experience being calculated wrongly. If you are still in the role, write "Present" rather than leaving the end blank.
This is matching, not keyword stuffing. The system compares your CV to the text of the ad; if you describe the same thing in different words, no match forms.
If the ad says "data analysis", writing only "analytics" is not enough - include both. Spelling out an acronym alongside itself is the safest form: "SEO (search engine optimisation)", "HR (human resources)".
A skills list at the end is good, but the same skills need to appear inside your experience bullets too. "Python" in a list does not show you used it; a recruiter searching for it wants to see it in context.
Bars and stars are invisible to a parser; at best the word "English" survives. Write "English — advanced (C1)", "German — intermediate (B1)" instead.
Everything above gets your CV read. This part decides what happens once it is - which is the entire point of getting past the ATS.
"Responsible for reporting processes" is a job description. "Cut monthly reporting from 3 days to 4 hours" is a result. The second tells a human something, and naturally carries more of the keywords too.
Not every bullet needs one, but none at all is conspicuous. Team size, users, percentage change, time saved. If you do not know the exact figure, give a defensible range - do not invent one.
Long lists go unread and bury your strongest bullet among weaker ones. Four or five for the most recent and most relevant role, two or three for older ones, is a good balance.
One page or two makes no difference to an ATS - it does not count pages. For a human the rule is simple: one page up to five to seven years of experience, two beyond that is plenty.
The last step is to stop guessing and look. You want to see how your CV appears to the system before you apply, not after.
Copy the contents of your PDF into any text editor. Sections that lose their order, lines that run into each other and headings that vanish all show up immediately. It is the closest view you get of what the parser sees.
You do not need to rewrite your CV for every application, but you do need to check it against the one you are targeting: which keywords are missing, which section is thin. CVision does this in the free analysis and lists the gaps.