GuidesYour resume
How an ATS parses your resume, and how to make it readable
An applicant tracking system pulls the text out of your file, splits it into sections by their headings, and picks out your contact details, employers, titles, dates, schools and skills into fields a recruiter can search and an application form can prefill. It reads a one-column PDF or Word file with standard headings and plain text best. Columns, tables, text boxes, images and contact details in the page header are the usual reasons a parse goes wrong.
By The Jobapplier team ·
What an applicant tracking system is
An applicant tracking system, or ATS, is the software an employer uses to publish its jobs, take applications and move candidates through its hiring steps. Workday, Greenhouse, Lever, iCIMS, Ashby and SmartRecruiters are some of the common ones. When you press Apply on a company's careers page, the form you fill in usually belongs to one of them.
Your resume does two things inside it. The file itself is kept and shown to whoever reviews your application. And the text in it is read by a parser, which turns it into structured fields: your name, email and phone, each job with its employer, title and dates, each school and degree, a list of skills. Those fields are what the recruiter searches and filters on, and what some application forms fill in for you.
What happens to your file, step by step
- Text extraction. The parser takes the text out of the file. A PDF made from a word processor has a text layer it can read. A scanned page or a PDF exported as an image has none, and the parser gets nothing or a poor guess from character recognition.
- Reading order. The text comes out in the order the file stores it, which is not always the order you see. In a two-column layout the left and right columns can be read line by line across, mixing a job title from one column with a skill from the other.
- Sections. The parser looks for headings it knows (Experience, Work Experience, Education, Skills, Summary, Projects) and files what follows under each. A heading it does not know, such as “Where I've made an impact”, leaves the lines under it without a home.
- Entries. Inside Experience it looks for the pattern of a job: an employer, a title, a date range, then lines of work. Inside Education, a school, a degree and dates.
- Fields. The result is stored as the candidate's profile in the ATS, beside the original file.
What breaks a parse
Most parsing problems come from a handful of layout choices.
| Layout choice | What can go wrong |
|---|---|
| Two or three columns | Lines from the columns are read across and interleaved. |
| Tables and text boxes | Cells come out in an odd order, or a box is skipped entirely. |
| Contact details in the page header or footer | Some parsers skip headers and footers, so your email and phone go missing. |
| Icons for phone, email and location | The icon carries the meaning; the parser sees a stray symbol or nothing. |
| Skill bars and charts | An image of a level is no text at all. |
| Creative section names | Lines land in no section, or the wrong one. |
| Years without months, or mixed date formats | Durations come out wrong; overlaps and gaps look odd. |
| A scanned or image-only PDF | No text layer to read. |
None of this means a designed resume is always rejected. It means the structured profile built from it may be wrong or empty, and a recruiter searching that profile for a skill will not find you.
The layout that parses cleanly
- One column, read top to bottom.
- Your name and contact details in the body of the page, at the top, as plain text: email, phone, city, and a LinkedIn or portfolio link.
- Standard headings: Summary, Experience, Education, Skills, and Projects or Certifications if you have them.
- Each job in the same order: title, employer, place, dates, then its lines.
- Dates with months, in one format throughout: “Mar 2021 – Jun 2024”.
- Plain bullets, and no tables, text boxes, icons, images or charts.
- A common font at a readable size, and a PDF with a real text layer, or a Word file if the posting asks for one.
- The right paper size: US Letter for jobs in the US and Canada, A4 elsewhere, so the file prints as the reader expects.
A quick check: open your PDF, select all the text and paste it into a plain text editor. If what you see is in the right order, with your contact details at the top and each job's dates beside it, a parser will most likely read it the same way.
When the form fills itself from your resume
Many application forms offer to read your resume and fill in the fields for you. SmartRecruiters builds your experience and education entries from the file you upload. Workday offers to autofill its form from a resume, or to apply manually. Some other systems tick a “fill out the application with my resume” box by default.
This is where a parse problem becomes your problem. A misread resume can put a job title in the employer field, merge two jobs into one, or drop a degree, and it can write over fields you had already filled in. Before you go on to the next page, read every entry the form made from your file. Our guides to applying on Workday and SmartRecruiters walk through those forms page by page.
What a parser does not do
A common claim is that most resumes are thrown out by an ATS before a person sees them. We have not seen evidence that supports a figure like that, and the systems named above are built for people to review applicants. What can happen is quieter: a recruiter searches the candidate pool for a skill or title, and a resume whose text did not parse, or does not name that skill, does not come up. Some employers also add their own knockout questions, such as the right to work in a country, and an answer there can end an application whatever the resume says.
So the goal is plain: a file whose text comes out whole and in order, under headings a machine recognises, naming the skills the posting asks for in the posting's words. The guide to resume keywords covers that last part.
How Jobapplier builds and sends the file
Every resume Jobapplier makes follows the layout above: one column, standard headings, dates with months, and no tables or icons, as a PDF with a text layer. It is printed on US Letter for a posting in the US or Canada and A4 everywhere else, and every file is named Resume.pdf, so its name tells the employer nothing about which version it is. Technologies are bold inside the lines that used them and listed once under Skills, which keeps a separate “Tech stack” line out of each role.
Your master resume also gets a health score, out of 100 with a grade from A to F, from checks a parser cares about: whether an uploaded file has a readable text layer, your contact details, standard headings, dates with months, length and the shape of your bullets. Each failed check says what cost points.
When you apply with the browser extension, “Apply with tailored resume” attaches that posting's own resume on every page of the form, in place of a file the form already holds. On forms that read a resume and fill fields from it, the extension fills the fields from your profile, and you check them, as with any field, before you press Submit yourself. See the browser extension and resume tailoring for more.
Questions
Is PDF or Word better for an ATS?
Both are read well when the PDF has a real text layer and the layout is a single column. Send a PDF unless the posting asks for a Word file. A scanned or image-only PDF has no text to read.
Can an ATS read a two-column resume?
Some can, but many read the text across both columns line by line, mixing them. One column is the safe choice.
Should my contact details go in the header?
Put them at the top of the page body instead. Some parsers skip headers and footers, so an email or phone number placed there can go missing.
How can I see what a parser reads from my resume?
Open the PDF, select all the text and paste it into a plain text editor. If the order is right and your contact details, employers and dates come out whole, a parser will most likely read it the same way.