Two-column resumes and the ATS: what actually breaks

The short answer: risky, and rarely worth it

Modern parsers handle many two-column layouts — but not all, and you can’t see which ATS a company runs. A single column parses everywhere, reads faster for humans, and costs you nothing. The two-column upside is aesthetic; the downside is your skills section landing in the wrong job’s field.

How parsers actually read a page

Parsers extract text in reading order — usually left-to-right, top-to-bottom across the whole page width. A well-built two-column PDF stores text in logical order and parses fine; a layout built from floating text boxes stores it in creation order, and the parser interleaves your sidebar with your work history.

What actually breaks: text boxes, tables, headers

The real offenders are the mechanisms design tools use to make columns: text boxes (extracted out of order or skipped), layout tables (cells read across rows, scrambling sections), and content placed in the document header/footer region (many parsers ignore it entirely — a classic spot to lose your phone number).

The reading-order test you can run yourself

Open your exported PDF, select all, copy, and paste into a plain-text editor. If sections appear complete and in a sensible order, a parser will see the same. If your skills interleave with job bullets or the sidebar lands mid-employment-history, the ATS sees that too.

Dates and titles in the wrong column

ATS parsers map text to fields: employer, title, start/end dates. Two-column layouts that put dates in a left rail separated from the role text break that pairing — the parser can’t tell which date belongs to which job, and your experience timeline arrives scrambled or empty.

Skills sidebars: the most common casualty

The typical two-column pattern — skills, education and contact in a narrow sidebar — puts your keyword-densest content in the least reliably parsed region. If the sidebar is a text box, your keyword match score at real employers silently drops to near zero.

"But I applied with one and got the job"

Survivorship isn’t evidence: many applications are read by humans first, some ATSs parse columns fine, and referrals bypass parsing entirely. The question isn’t whether two-column ever works — it’s whether the layout is worth a silent failure rate you can’t measure.

When two columns are fine

Roles where the resume is reviewed by humans only (small companies, direct-email applications, design portfolios attached as PDF) and print contexts. If you know a human reads first, a clean two-column resume is a taste choice, not a risk.

The hybrid that keeps the look without the risk

Want visual structure without parser risk? Use full-width sections with a strong heading hierarchy, a horizontal skills line under the summary, and generous white space. Banded headings give the "designed" feel while keeping one text flow.

What recruiters think of two-column resumes

Mixed — some find them scannable, many find sidebars cramped at 9pt. What they agree on: they read top-to-bottom-left-to-right, so anything in a sidebar gets skimmed last or not at all. Your best evidence belongs in the main flow either way.

If you keep two columns, build them right

Use real column objects (not text boxes), keep all experience — titles, employers, dates, bullets — in one column, keep contact info out of the header/footer region, export to PDF, and run the copy-paste test before every send.

The single-column rule we build on

All 25 RezUp templates are single-column real text by design — the one layout rule that removes ATS parsing risk entirely. The visual variety comes from typography, accent color and banded headings, not from layout mechanics that parsers trip on.