CVEmber
Create my resume
← Blog

How an ATS actually reads your resume, and what breaks it

Applicant tracking systems don't look at your resume. They parse it. Here is what that means for columns, tables, headers, fonts and file names, and a checklist you can apply in ten minutes.

ATS · 15 September 2026 · 6 min read

By Rajesh Kumar · How these pages are made

An applicant tracking system is a database with a form on the front. When you apply, your resume is run through a parser that tries to fill that form: name, email, phone, each job with its title, employer and dates, each degree, a list of skills. A recruiter searching the database sees what landed in those fields, not your PDF. If the parser guessed wrong, the recruiter never learns that the resume was good.

What parsers do well

They read left to right, top to bottom, in one column. They recognise section headings that use ordinary words: Experience, Education, Skills, Summary, Projects, Certifications. They pull dates in common formats and pair them with the nearest job title. They match skills by looking for the words the job post used.

What breaks them

  • Tables and multi-column layouts. Text in a two-column table is often read across the row, so a job title on the left gets glued to a skill on the right. Real two-column designs are fine if the underlying text order is still one column per block, which is how CVEmber's sidebar templates export. A table copied out of Word is not.
  • Headers and footers. Many parsers skip them entirely. If your name and email live in the page header, they may not exist.
  • Graphics as text. Skill bars, icons for phone and email, a name set as an image: none of it is text. The parser sees nothing.
  • Creative section names. "My journey" is not "Experience". "Toolbox" is not "Skills". Rename sections for a human only when a standard word would not fit.
  • Dates without months. "2022 – 2024" is read as anywhere from one to three years. "Jun 2022 – Mar 2024" is exact.
  • Scanned PDFs. A photo of a resume has no text layer. Export from your editor, never from a scanner.

Keywords, without stuffing

A recruiter searching for "PostgreSQL" will not find "Postgres" or "SQL databases". Use the exact words the job post uses, in your skills list and at least once in a bullet where it actually happened. Do not paste the job description in white text; parsers index it, recruiters see it, and it reads as what it is.

A ten-minute checklist

  1. Contact details in the body of the page, not a header.
  2. Standard section names.
  3. Months on every date, and "Present" on the current role.
  4. Skills as short phrases, one to four words each.
  5. Bullets that start with a verb and contain a number where one exists.
  6. File name: your name and the role, for example Priya-Sharma-Product-Manager.pdf.
  7. A text PDF. Select some text in the viewer; if you cannot, it is an image.

Check it in thirty seconds

The free Resume Checker runs these checks on any resume, with a named fix for each point lost. No account needed.

We test our own templates the same way a parser reads them, field by field. What we tested, what counts as a pass and what we haven't tested are on our ATS testing methodology page. If you are choosing a tool, our comparisons set the facts side by side, with sources.