Most advice on this subject is guesswork about what parsers do, often written by people who have never seen one fail. The checks below are the ones our own resume scorer runs, rendered directly from its source, along with the weights it actually applies.
The honest headline: formatting matters far less than the advice industry suggests. It is worth 10% in our scoring. It is on this page because when it goes wrong it goes badly wrong, not because it is where most resumes lose.
These are the patterns our checker flags, with the reason each one matters. They are rendered from the same list the product uses, so this page cannot drift from what it does.
Pipes and multi-column layouts scramble in Workday and Taleo — text from two columns interleaves into nonsense. Use a single column.
Use a plain hyphen. Icon glyphs sometimes drop entirely during PDF text extraction, taking the bullet's first word with them.
Multiple tabs usually mean columns. An ATS reads left-to-right and will merge the columns together.
Parsers look for literal headings on their own line. A missing Work Experience heading is the most severe format problem our scorer reports, because without it a system may fail to build your job history at all — dates and titles end up unattached.
Use Work Experience or Professional Experience, and a Skillsline near the top. Clever section names — “Where I’ve Made an Impact” — are the kind of thing that reads well to a human and disappears to a machine.
These are our scorer’s real weights. We publish them because a score you cannot argue with is not worth much, and because the ordering is the most useful thing on this page.
| Component | Weight | What it measures |
|---|---|---|
| Requirement coverage | 40% | Whether the resume evidences what the posting asks for. Must-haves count three times a nice-to-have. |
| Keyword match | 20% | Vocabulary overlap with the posting. Real, but deliberately not dominant. |
| Content quality | 20% | Quantified outcomes and strong verbs rather than duty descriptions. |
| Experience fit | 10% | Seniority and recency against what the role expects. |
| Format | 10% | Parseability. Worth the least — a perfectly formatted resume for the wrong job is still the wrong resume. |
Requirement coverage is worth four times format for a reason. The most common real problem is not a broken layout — it is a resume that never evidences half of what the posting asked for, formatted beautifully.
A single-column layout with plain text, standard section headings, and no tables or graphics. The goal is that a parser reading top to bottom recovers your text in the order you wrote it — that is the whole requirement, and most other advice is downstream of it.
Rarely in the way people imagine. Most systems parse your resume into fields and rank it; a human still filters. The realistic failure is not a rejection email but your experience landing in the wrong field, or a column layout interleaving into nonsense that nobody reads carefully.
Either works in modern systems, provided the PDF contains real text rather than an image. Export from your editor rather than scanning or screenshotting, and if you can select the text in a PDF viewer, a parser can too.
Yes, but less than most advice implies. Our own scorer weights requirement coverage at 40% against 20% for raw keyword matching, because whether you can do the job matters more than whether you echoed its vocabulary. Put keywords in the bullet that proves them.
They are the single most common real failure. Many parsers read left to right across the full width, so a two-column layout interleaves a skills sidebar into the middle of your job history. The design looks better to you and worse to the machine.
Paste your resume and the job description you are applying to. You get requirement-by-requirement coverage, the keywords you are missing, and any of the format problems above — against that posting rather than in the abstract. The first check is free.