How Applicant Tracking Systems Actually Read Your Resume
How ATS software parses columns, fonts, and tables, with practical examples of what breaks parsing and how to fix it.
When you apply online, your resume rarely goes straight to a human. It first passes through an Applicant Tracking System, software that scans, parses, filters, and scores your application based on keywords, dates, and formatting. If the ATS cannot read it, the recruiter never sees it, however qualified you are. This is how these systems work and what sends an application into the digital void.
The Parsing Process
An ATS does not “look” at your resume the way a person does. It does not appreciate your color palette or your hours of layout work. It strips the formatting and converts the document to plain text, then categorizes it into fields. Contact, education, work experience, skills.
This is where most candidates fail. Complex formatting confuses the parser, merging graduation dates with job titles, dropping sections, or misreading the phone number. When a recruiter opens a garbled profile instead of a clean history, they move on.
Text Extraction Mechanics
Most modern systems use direct text extraction rather than OCR. They read the text layer, not an image of it. A PDF exported from Canva, Illustrator, or an unconventional word processor may render text as vector shapes or in unpredictable order, so the output comes out scrambled.
Standard .docx files, or PDFs from Word or Google Docs, are safest. They keep a linear, predictable text structure.
What Breaks the ATS
Multi-column layouts. A two-column design reads horizontally, so the left “Skills” column mashes into the right “Experience” column, producing nonsense. A single column reads in the order you intended. Fix: single column.
Tables and text boxes. Many parsers skip text inside tables and floating boxes entirely, which leaves your profile empty of critical keywords. Fix: use commas or pipe characters for lists, never tables.
Headers and footers. Information in the document margins is frequently ignored. Tuck your contact details into the header and the system may miss your phone and email. Fix: put contact info in the body, at the top.
Creative section titles. The parser uses headings to map fields. “My Professional Journey” is not a recognized trigger, so the job history below it gets misclassified or ignored. Fix: use “Work Experience,” “Education,” “Skills,” “Professional Summary.”
Complex fonts and icons. Custom fonts can convert to random symbols, and phone icons next to numbers confuse older systems. Fix: web-safe fonts, no graphics.
Field Mapping
The parser expects a specific hierarchy per job. Company, title, dates, description. Inverting it or misplacing dates mis-files the fields. Date format is strict. “MM/YYYY - MM/YYYY” or “Month Year” parses, while a bare “2020 to 23” may register as no date range, zeroing your years of experience.
Keyword Matching Is Real
After extraction, the system scores you against the job description. Older systems rely on exact matches, so “CRM” will not connect to “Customer Relationship Management.” Use the posting’s exact phrasing, without stuffing. The recruiter will still read it. Context beats frequency. A keyword in an achievement bullet, “managed customer relationship management, lifting retention 15%,” carries more weight than the same word alone in a skills list.
Strategies for Success
Keep the resume linear, top to bottom, no sidebars. Standardize dates with months and years. Use default solid bullet points. Export as a PDF from a word processor, never an image-based PDF. Test the parse. Copy the PDF text into Notepad. If it is scrambled, the ATS sees the same mess.
The Human Element
Why Formatting Mistakes Persist Despite the Rules
If the formatting rules are so well-known, why do qualified candidates keep getting filtered out? Because the guidance runs against what looks good and what is convenient. Templates that look polished use columns and graphics, and pasting contact info into a header is the natural habit most people learned. The visually appealing choice and the parse-safe choice conflict, and aesthetics usually win in the moment, with the rejection discovered far later.
The convenience factor compounds it. Setting up a clean single-column document with body-text contact info takes a deliberate step that most resume templates do not nudge you toward. Nobody starts out wanting two columns. They inherit a template or follow a visual convention. Rewriting the resume to be parse-safe means fighting the pull of the template and the default.
The fix is to make parse-safety the default rather than the exception. Choose a resume builder or template that produces a clean single-column text-based PDF by design. Verify it once with the plain-text test. After that, the format stays correct automatically, and only the content needs attention, which is where the real value of the resume lives anyway.
The Hidden Cost of Complicated Resumes Beyond Rejection
The damage of a broken format extends past the single rejection. If a resume fails to parse at a company, the candidate’s application disappears without explanation, so they never learn the cause. They assume the problem is their qualifications, not their formatting, and they may rework the content, which was never the issue, instead of fixing the layout. The waste is twofold. The lost opportunity and the misdirected effort.
It also compounds across applications. A candidate using the same template at twenty companies runs the same risk twenty times. Because the failure is silent, there is no feedback loop telling them to change anything. The resume keeps failing in the same invisible way, application after application, while the candidate keeps refining bullets that were never the bottleneck.
The plain-text test is worth doing once. It surfaces the silent failures before they cost a single real application, and it reveals the actual causes. Misplaced contact, jumbled columns, missing text. Fixing it once, then reusing the clean format, turns a recurring hidden problem into a one-time solved one, and lets the candidate focus their effort where it can actually work.
When the System Will Refuse You No Matter the Format
An honest limit is worth stating. Some applications are rejected by the ATS for reasons no formatting fix addresses. The system may be ranking on years of experience, specific certifications, geographic preferences, or a required credential the resume simply lacks. No amount of tagline optimization makes a hardware spec requirement disappear or substitutes for a license that is not held.
This is not a reason to give up on formatting. It is a reason to understand what formatting can and cannot do. Formatting guarantees your information is readable and rankable. It cannot change the underlying fit. A candidate missing a hard requirement was never going to pass, and a clean format at least ensures the rejections that do happen are for actual reasons rather than parsing errors.
The constructive takeaway is to use the honest limit as a filter. If you are being repeatedly filtered for a requirement you lack, the answer is either to gain the credential, target roles where it is not required, or find ways past the system. A direct approach, a referral, that do not depend on the gate. Formatting gets you through when you qualify. The rest is strategy, not formatting.
Beating the ATS is the first step, not the goal. If you strip formatting and keyword-stuff until it reads like a robot wrote it, the recruiter rejects you on sight. Aim for the balance. Structurally simple enough to parse flawlessly, compelling enough to convince a human. Clear achievements, quantified results, straightforward formatting remove the technical barriers and let your qualifications take center stage.