ATS-Friendly CV Guide, a formatting blueprint for resumes that pass applicant tracking systems

A while back a friend asked me to fix her CV. She had applied to 60 jobs over three months and heard nothing back. Not rejections. Silence. Twelve years of marketing experience, solid track record, graduated from a good school. She thought she was cursed.

I opened her PDF, hit Ctrl+A, copied everything, and pasted it into Notepad. What came out was a scrambled mess. Her name was on line 47. Her phone number was split across two columns. Her most recent job title was welded to a skill bullet from three years ago.

The CV looked gorgeous in Word. To an ATS parser, it was nonsense.

So this post is the manual I wrote for her that afternoon. Every formatting rule, every section spec, every quirk of every major ATS system I could find. Not the philosophy of why ATS exists or why recruiters use it. That stuff is covered in our other post about the story side. This one is the dry technical reference you bookmark and keep open while you build.

Fair warning: it is long. You can skim the sections you need. The headings tell you what is where.

What “ATS-Friendly” Actually Means

Strip the jargon away. An ATS-friendly CV is just a CV that a piece of software can read without garbling the contents. Every major hiring platform (Workday, Greenhouse, Lever, iCIMS, Taleo, SmartRecruiters) feeds incoming PDFs through a parser that tries to extract your name, email, phone, job titles, companies, dates, and skills. If the parser succeeds, your CV gets scored. If it fails, you become an empty profile at the bottom of the pile.

So the goal is simple. Build a CV that three different audiences can read without complaint:

  1. The ATS parser (machines, extremely literal)
  2. The recruiter browsing ranked results (humans, scanning fast)
  3. The hiring manager pulling up your file (humans, reading properly)

Good news. The rules that make a CV parser-safe are the same rules that make it readable for humans. You do not have to choose.

The 7 Silent Killers

These are the specific formatting choices that quietly torpedo applications every day. None of them look broken to the human eye. All of them break ATS parsers.

01

Multi-Column Layouts

Tables and side-by-side columns look clean to a human and turn into word salad for an ATS. The parser reads left to right across rows, mixing your job title with a skill from the sidebar and your dates with your education.

The Fix Use a single column that flows top to bottom. Boring is safe. Boring gets through.

02

Text Boxes for Layout

Designers love text boxes because they anchor content exactly where you want it. Many parsers ignore everything inside a text box, so your contact info or skills list effectively does not exist.

The Fix Keep text in the main document flow. No floating boxes, no side panels, no fancy anchored frames.

03

Creative Section Names

Renaming 'Work Experience' to 'My Career Journey' or 'Professional Story' makes the parser miss it entirely. It looks for specific header strings it was trained on.

The Fix Stick to Work Experience, Education, Skills, Certifications, Languages, Summary. Always.

04

Contact Info in Headers or Footers

Many ATS systems skip document headers and footers completely during parsing. Your name and phone number live there, they become invisible to the system.

The Fix Put your name, email, phone, and location in the first line or two of the main body. That's it.

05

Custom Fonts and Fancy Characters

Decorative fonts often fail to embed properly, producing little boxes or question marks. Unicode bullet points like stars or checkmarks get dropped entirely.

The Fix Arial, Calibri, Helvetica, Georgia, Times New Roman. Standard round bullets. Predictable is safe.

06

Inconsistent Date Formats

Mixing 'March 2022', '03/2022', and 'Mar. 22' in the same CV confuses parsers trying to calculate your tenure. Some systems score you lower if dates look jumbled.

The Fix Pick one style. 'Month Year to Month Year' is safest across every system. Use it everywhere.

07

Embedded Images or Logos

Your photo, company logos, graphical skill bars, icon bullets. None of them parse as text. If your contact info is inside an image banner, it vanishes.

The Fix Text only for anything important. Keep any decorative images separate from the content the parser needs.

The ATS-Safe Format Specification

If you just want exact numbers to follow, here they are. This spec is based on what parses cleanly across every major ATS I have tested.

📐
Baseline Specs

Page size: US Letter (8.5" × 11") or A4, depending on your region.
Margins: 0.5" to 1" on all sides. Avoid under 0.5".
Font: Arial, Calibri, or Helvetica at 11pt body, 12pt section headers, 18-22pt name.
Line spacing: 1.15 for body, 1 for dense sections, 1.5 between sections.
Length: 1 page if under 10 years experience. 2 pages max otherwise.
Columns: Exactly 1. No exceptions.
File format: PDF with selectable text. Not Word unless the posting says so.
File name: FirstName_LastName_CV.pdf. No spaces, no special characters.

Build Guide, Section By Section

Here is the exact order and content each section needs, in the order they should appear on the page.

1. The Header

Keep this in the main body, not in a document header. Four lines max:

  • Line 1: Your full name, bold, 18-22pt
  • Line 2: Job title you are targeting (not your current one unless they match)
  • Line 3: Phone · Email · City, Country
  • Line 4: LinkedIn URL (cleaned up, no tracking params) · Portfolio URL if relevant

No photo. No graphic banner. No clever typography. The parser wants clean text at the top of the document.

2. Professional Summary

Two to four lines, directly after the header. This is prime keyword real estate for both the parser and the human. The parser weights early content more heavily in its scoring.

Mention your target role, years of experience, and two or three concrete strengths that match the job description. Natural language, not a keyword list. We have a detailed guide on summaries here if you want deeper help.

3. Work Experience

Most recent job first. Each entry follows the same structure every time:

📋
Work Entry Template

Line 1: Job Title | Company Name | City, Country
Line 2: Month Year to Month Year (or Present)
Then: 3-6 bullet points, each starting with a strong verb and ending with a measurable outcome where possible

Use the same pipe-delimited structure for every job. Consistency helps the parser categorize correctly. If one entry uses pipes and another uses commas, some parsers get confused on the inconsistent one.

4. Skills

A flat list of skills, grouped by category if you want. No proficiency bars, no star ratings. The parser cannot see graphics.

Example format that parses reliably:

Parser-Friendly Skills Format

Technical: Python, SQL, JavaScript, Node.js, React
Tools: Git, Docker, AWS, Jira, Figma
Languages: English (native), Spanish (conversational)

If the job description names a specific tool, make sure it is in your skills list (if you actually have experience with it). Parsers often give exact-match skill listings higher weight than inferred ones.

5. Education

Same pattern as work experience. Degree | Institution | Year. Relevant honors or coursework only if you are early career.

6. Certifications, Languages, Projects

Optional sections. Keep them lean. For every certification, spell out the full name once along with any abbreviation: “Project Management Professional (PMP).” This doubles your keyword matches.

Before and After: How ATS Parsers See It

These are real parsing examples. Same content, different formatting, radically different outcomes.

The Header Problem
ATS Reads This As

[header region ignored] Senior Product Manager | 8 years experience...

ATS Should Read

Jane Smith | Senior Product Manager | jane@email.com | +1-555-0100 | New York, NY

What happened: When your name sat in a Word document header, the parser skipped the entire region. A hiring manager opened her application and saw no name at all. Moving it into the body made her searchable again.
🧩 The Two-Column Disaster
ATS Reads This As

Senior Marketing Project Digital campaigns Google Manager 2022 Analytics Led team...

ATS Should Read

Senior Marketing Manager | Acme Corp | New York | March 2022 to Present. Led digital campaigns, managed Google Analytics...

What happened: The two column layout caused the parser to read across the table row, scrambling the title, date, skills, and job summary into one mess. Single column fixed it instantly.
The Creative Header
ATS Reads This As

[No work experience section detected]

ATS Should Read

WORK EXPERIENCE [followed by correctly parsed job history]

What happened: The candidate used 'Where I've Made My Mark' as their work section header. The ATS looked for 'Work Experience', 'Employment History', or 'Professional Experience', found nothing, and scored the candidate as having zero work experience.

ATS System Deep Dive: The Big Five

Each major platform has slightly different parsing quirks. You do not always know which one a company uses, so the safest bet is to optimize for the strictest. But knowing the differences helps when you can tell from the application URL which system is running.

Workday

Common at Large enterprises, Fortune 500

QuirkStruggles with complex layouts. Sometimes parses a PDF differently than the same content in a Word doc.
TipSubmit as PDF. Keep it to one column. Triple check that dates are in consistent 'Month Year' format.

Greenhouse

Common at Tech companies, startups

QuirkMore forgiving than most. Handles tables decently. Strong on skills extraction.
TipStill avoid tables where possible. Greenhouse highlights skill matches to recruiters, so pack your skills section.

Lever

Common at Mid-sized tech, SaaS

QuirkGenerally tolerant. Has trouble with PDFs that were scanned or photo-based.
TipAlways export from Word or a builder as native PDF. Never photograph a printed CV.

Taleo

Common at Oracle shops, old-school enterprise

QuirkThe strictest of the big ones. Very literal about section headers. Prefers Word docs over PDFs in many configurations.
TipMatch section headers exactly. If the form accepts .docx, submit that format. Keep layout as plain as possible.

iCIMS

Common at Healthcare, finance, retail

QuirkStrong keyword matching. Weak on creative formatting.
TipMirror the job description language in your summary and skills. iCIMS weighs literal matches heavily.

SmartRecruiters

Common at Global enterprises, Europe-heavy

QuirkHandles multilingual CVs reasonably. Finicky about embedded hyperlinks.
TipSpell out URLs in plain text (linkedin.com/in/yourname rather than a hyperlinked logo).

The 2 Minute Test You Can Run Right Now

Before you submit anything, run this. It takes two minutes and catches 90% of formatting issues.

  1. Open your CV PDF
  2. Press Ctrl+A (or Cmd+A on Mac) to select all text
  3. Press Ctrl+C to copy
  4. Open Notepad (or any plain text editor)
  5. Paste with Ctrl+V
  6. Read through what you see

If the plain text version:

  • Shows your name at the top → good
  • Keeps job titles near their companies → good
  • Has dates in the right places → good
  • Reads top to bottom in a logical order → good

If it shows missing content, scrambled order, or weird character substitutions (question marks, boxes, fragments) → that is exactly what the ATS parser sees. Fix it before you submit.

Keyword Matching: The Scoring Side

Passing the parser is step one. Scoring well in the match stage is step two.

Once your CV is parsed cleanly, the ATS compares its contents against whatever keyword profile the recruiter set up for this specific job. The keywords come straight from the job posting: required skills, preferred tools, specific methodologies, industry terms. Every match bumps your score. Missing keywords drag it down.

How To Find The Right Keywords

Open the job description. Read it twice. Highlight every specific skill, tool, platform, certification, and industry phrase it mentions. That is your keyword list.

Now compare against your CV. For every keyword on the list that honestly applies to your experience, make sure the exact phrase appears somewhere in your document. Not a synonym. The actual phrase.

If the job says “Google Analytics” and your CV says “web analytics tools,” the parser scores a mismatch. Same skill, wrong words.

Where To Place Keywords

  • Summary section: 3-4 of your highest priority keywords, woven naturally into the first two sentences
  • Skills section: Exact phrase matches for tools, platforms, languages, frameworks
  • Work experience bullets: Keywords in the context of actual achievements, not stuffed in isolation
  • Certifications: Full names with acronyms

The Acronym Trick

One of the easiest wins in keyword optimization. ATS parsers are literal. They do not always know that “Search Engine Optimization” and “SEO” are the same thing. Or that “Project Management Professional” and “PMP” refer to identical credentials.

The fix costs nothing. Write both forms the first time a term appears:

  • “Search Engine Optimization (SEO)”
  • “Project Management Professional (PMP)”
  • “Customer Relationship Management (CRM)”
  • “Key Performance Indicator (KPI)”

Now you match whichever version the job description uses. Costs 5 seconds per term, doubles your keyword hit rate.

File Format: PDF vs Word

The short answer: submit what the job application asks for. If the form has no preference, PDF is safer in 90% of cases.

Why PDF:

  • Locks your formatting so what the recruiter sees matches what you designed
  • Universal compatibility across devices and operating systems
  • Parsers built in the last 5 years handle PDF text well

Why sometimes Word (.docx):

  • Some older Taleo configurations parse Word better than PDF
  • Certain recruiting agencies still prefer editable files
  • The job posting explicitly asks for it

The one format that is always wrong: an image-based PDF (a photo or scan of a printed CV saved as PDF). The parser sees a picture, reads zero text, and you become a blank profile. Test your PDF with the copy-paste trick above before submitting.

The Pre-Submit Checklist

Run through this every single time before hitting submit. It takes under a minute and catches nearly every avoidable rejection.

ATS-Ready in 60 Seconds

  • Single column layout, no tables or text boxes
  • Standard font (Arial/Calibri/Helvetica) at 11pt body, 18-22pt name
  • Section headers use standard labels: Summary, Work Experience, Skills, Education
  • Contact details in the main body, not document header/footer
  • Consistent date format throughout (Month Year)
  • Standard round bullets only
  • Saved as text-based PDF (not an image or scan)
  • Top keywords from the job description appear in your CV
  • Acronyms spelled out with both forms the first time
  • File named FirstName_LastName_CV.pdf
  • Copy-paste test produces clean, readable plain text

What About Creative Roles?

Designers, art directors, creative directors often worry this advice erases their personality. Here is the honest truth.

Your portfolio is where your creativity shines. Not your CV. A senior creative hiring manager will still go look at your Behance, your Dribbble, your portfolio site, your case studies. They do not evaluate your design skills by how beautifully formatted your CV is. They evaluate them by the actual work you link to.

Use a clean ATS-friendly CV with your portfolio URL prominently listed. Let the portfolio carry the visual weight. That way your application actually reaches the human in the first place, and your creativity gets judged on your real work instead of on formatting tricks.

Frequently Asked Questions

Is Word or PDF better for ATS?

PDF is safer in 90% of cases because it locks your formatting. Submit Word only if the job posting specifically asks for it, or if you are submitting through an older Taleo portal. Always test your PDF with the copy-paste-into-Notepad trick to make sure the text is selectable.

Does a one page CV pass ATS better than two pages?

Length is not an ATS scoring factor. Parsers do not care if you are one page or two. What matters is whether the text parses cleanly and whether the keywords match. If you have under 10 years of experience, one page is usually better for the human reader. Anything more senior, two pages is fine.

Can I use color in an ATS-friendly CV?

Yes, as long as the text remains actual text and not an image. A colored section header or a dark blue name at the top is fine. What kills ATS is putting color behind content as a background image, or using color to indicate meaning the parser cannot read (like red for weaknesses).

Should I use a CV template from Canva or Word?

Most Canva and Word templates use tables, text boxes, or two column layouts. They look polished and fail ATS parsing at high rates. If you want a visual template, pick one that is clearly labeled “ATS-friendly” and still test it with the plain text trick before relying on it. A lot of templates claim ATS compatibility and do not actually have it.

Do all companies use ATS?

Almost all medium and large companies do. Very small businesses sometimes still read CVs by hand. But you usually cannot tell in advance, so format for ATS always. A CV that passes ATS is also easy for humans to read, so you lose nothing by being safe.

What is the difference between an ATS and a resume parser?

The parser is one component inside the ATS. The parser extracts text. The ATS handles the whole workflow: receiving applications, parsing them, scoring them against the job, ranking candidates, and passing the top ones to recruiters. People use the terms somewhat interchangeably, but technically the parser is just the reading engine.

Are there free ATS checkers I can use?

Yes. FreeCV has a free ATS simulator that scores your CV against a job description. Jobscan also has a free tier. The paid tools (Jobscan premium, Resume Worded) add features but the free versions catch most of the common problems. For formatting issues specifically, the Notepad copy-paste test is free and reveals issues most online tools miss.

Will my CV get rejected for any ATS error?

Not for every small issue, and the "60% match threshold" you've seen repeated everywhere isn't actually a thing. Modern ATSs don't publish a universal cutoff (and in 2026, many of the AI screening layers sitting on top of them, like GoPerfect or Eightfold, use explainable 1-5 scoring or percentile bands instead of a single keyword-match number). What actually causes automatic rejection is structural: a CV where the parser extracted zero text, no detectable work history section, missing contact details, or significant gaps in required skills. A minor formatting quirk might drop your relative ranking a few notches but rarely flips you from yes to no. Most ATSs rank and sort; the rejection itself usually happens upstream (knockout questions) or downstream (recruiter review).

How many keywords should appear in my CV?

There is no magic number. A practical target is to cover every required skill from the job description and most of the preferred ones. For a well-written job posting with 10 required and 5 preferred skills, you are aiming to hit all 10 required and 3-4 of the preferred. Higher is better as long as it is honest and reads naturally.

Does ChatGPT write ATS-friendly CVs?

It can, if you prompt it right. On its own, it produces generic content that often misses specific keywords. With the right prompts, it can tailor a CV to a job description and flag keyword gaps. We have a full post on ChatGPT resume prompts here with 15 specific prompts you can copy.

Get an ATS-Ready CV in 5 Minutes

Every FreeCV template is built to pass ATS parsing. Single column, clean structure, standard fonts. Just fill in your details and download.

Build My CV Free →

Test Your Existing CV Against ATS

Paste your CV into our free ATS scanner. Get a compatibility score and specific fixes in under 2 minutes.

Check My CV →

About the Author

Abd Shanti is a co-founder of FreeCV, used by job seekers in 180+ countries. He writes practical, data-backed advice on CV writing, job search strategy, and career development.