Is Your Two-Column CV Invisible to the ATS?
Two-column CVs look fantastic. A clean sidebar with your skills and contact details, a wide main column for experience — there's a reason they dominate tem...
atscv formatjob search
Is Your Two-Column CV Invisible to the ATS?
Two-column CVs look fantastic. A clean sidebar with your skills and contact details, a wide main column for experience — there's a reason they dominate template galleries. There's also a reason career forums are full of people who applied to a hundred jobs with a beautiful two-column CV and heard nothing back.
The layout isn't the problem. The parsing is.
Why columns confuse parsers
An ATS parser reads your document as a stream of text and guesses its structure. With a single column, the guess is easy: top to bottom. With two columns, the parser must decide: read down the left column, then the right? Or read straight across each row?
Many parsers choose wrong. The result is interleaved gibberish — "Senior Marketing Manager Photoshop 2019–2023 HubSpot" — where your job titles and skills are chopped into each other. Your CV arrives in the database scrambled, your keywords don't match anything, and no recruiter ever finds you.
The rule that actually decides it: reading order
Here's the nuance most advice misses. Columns are a visual property; parsing is a text property. What matters is the order of text in the file's text layer, not where the text sits on the page.
A two-column CV whose underlying text reads in a clean linear order — header, then main column, then sidebar, each section intact — parses perfectly well. A one-column CV built from text boxes can parse terribly. Design and parseability are separate questions, and you can win at both.
You can check your own CV in thirty seconds: open the PDF, select all, copy, paste into a plain text editor. Read what comes out. If it flows in a sensible order — your jobs aren't interleaved with your skills list — you're fine. If it's scrambled, so is your ATS record.
The sidebar elements that always cause trouble
Even with good reading order, some popular sidebar ingredients are parser-proof in the worst way:
- Skill bars and dot ratings. A parser extracts nothing from a bar that's 80% full. Write levels as words: "Excel — advanced".
- Icons instead of labels. A phone icon next to a number may parse as nothing. Add the word, or keep contact details in the main header line.
- Contact info in a graphical header block. Some parsers skip it. Your application lands with no email attached.
When to choose which
Applying online to mid-size or large companies (Workday, Greenhouse, Lever portals): single-column or a verified-safe two-column. This is most applications.
Networking, referrals, emailing a person directly, creative industries with portfolio culture: design freedom matters more — a human opens the file first.
Unsure? The safe default wins. A clean single-column layout loses you nothing with humans — recruiters consistently rate them as easy to scan — and protects you with machines.
You don't have to choose blind
This is exactly the trade-off we built into CVMate's template library: every template carries an honest ATS-fitness rating, the two-column designs keep strict linear text order under the hood, and the ATS checker shows you what a parser extracts from your specific document before you send it anywhere.
Love the two-column look? Keep it — verified. Prefer classic single-column? You're in the majority and the safest hands. What you should never do is guess. Thirty seconds with the copy-paste test tells you more than a hundred rejected applications would.