ATSFormattingParsing

Two-column resumes and the ATS: exactly what breaks

Why multi-column resume layouts scramble in parsing, what the extracted text actually looks like, and how to keep the design you like without losing a section.

MeritSlate Team4 min read

"Don't use two columns" is the most repeated rule in resume advice and the least explained. Here's the mechanism, what the damage actually looks like, and the cases where a sidebar survives.

What a parser does with a page

A PDF has no concept of a column. It stores glyphs at coordinates, and the extraction step reconstructs reading order from those positions using heuristics. The most common heuristic is the obvious one: group text into lines by vertical position, then read each line left to right.

On a single-column page that produces exactly what you see. On a two-column page it produces a zipper — one line of your sidebar, one line of your job history, alternating all the way down.

What you designed

Columns interleaved

What the parser reads

A two-column layout looks organized to you — the extractor reads across both columns and interleaves them.

What you designed

SKILLS · Python, SQL | EXPERIENCE · Senior Analyst, Acme (2021–2024)

Two visually separate regions a human reads as separate.

What a naive extractor produced

SKILLS Python, SQL EXPERIENCE Senior Analyst, Acme 2021–2024

One line of prose where the skills list has been welded into the job title.

Do that for forty lines and you get text that still contains every keyword you wrote — which is why a naive keyword count says your resume is fine — while the structuring step can no longer tell which company a date belongs to, or where the skills section starts and ends.

The damage is silent and uneven

Two things make this failure worse than it sounds.

You never see it. Your PDF looks perfect in every viewer you own. The scrambling happens inside a system you have no visibility into, and no rejection email has ever said "your columns interleaved".

Parsers disagree. Some handle columns well, some catastrophically. So the same file can sail through the first company's system and lose its entire employment history at the second. "It worked when I applied to X" is not evidence that it works.

What actually gets lost

In rough order of frequency:

CasualtyConsequence
Section boundariesSkills merge into experience; the parser can't segment the document
Date-to-employer associationYears-of-experience filters compute against the wrong role
Contact details in a sidebarPhone and email land mid-sentence and fail extraction patterns
Job titlesTitle fit scores against a mangled string
Reading order for a humanThe recruiter reading the parsed profile sees the same soup

When a sidebar is survivable

Not every multi-column layout is equally dangerous. The risk scales with how much load-bearing content lives in the second column.

Lower risk

  • A narrow right rail holding only decorative elements
  • Two columns used only inside a skills list, after a single-column header
  • A DOCX where the 'columns' are actually a single-column layout with tab stops
  • Any layout you've verified against multiple parsers

High risk

  • Contact details in a left sidebar
  • Skills, certifications or dates in a sidebar beside your experience
  • Full-height columns running the length of the page
  • A column implemented as a text box or floating shape

The safest version of "I want a sidebar" is a single-column resume with a visually distinct skills block that spans the full width. You keep the design contrast; the reading order stays unambiguous.

Check yours in thirty seconds

Select all the text in your PDF, copy it, and paste it into a plain notes app. Read the first fifteen lines. If your skills have merged into your job titles, or your dates have drifted away from their employers, you've found it.

For the full layout rules see the ATS-friendly resume format, and for what happens after extraction, how an ATS actually reads your resume.

Or run the free MeritSlate checker: it simulates nine vendor parsers against your actual file and shows you the text each one recovered, so you can see the zipper instead of guessing at it.

Frequently asked questions

Will a two-column resume definitely be rejected?
Not rejected — scrambled, which is often worse. Extractors reconstruct reading order from coordinates, so a two-column page can be read straight across, welding your sidebar into your job history line by line. All your keywords survive; the field structure recruiters filter on doesn't.
Is any sidebar safe on a resume?
Risk scales with what's in it. A narrow decorative rail is usually harmless; contact details, dates, skills or certifications in a sidebar are the worst case. The safest version of the look is a single-column resume with a full-width skills block.

Written by

MeritSlate Team

The team building MeritSlate's deterministic scoring engine — nine evidence-anchored axes, a nine-vendor ATS parse simulation, and every point backed by receipts.

Keep reading

All articles
ParsingATSFormatting

PDF vs DOCX: which resume file format should you send?

Whether an ATS can read PDFs, how parsers extract text from PDF and Word files, where each format fails silently, and how to export a resume that survives the trip.

Jul 3, 20265 min read
FormattingATSResumes

The best fonts for a resume (and the ones that break parsing)

Which resume fonts survive ATS extraction, what point size and margins to use, and why icon fonts and exotic ligatures turn your resume into unicode garbage.

Aug 9, 20264 min read
FormattingResumesATS

Functional vs chronological resumes: why the functional format fails

The functional (skills-based) resume breaks ATS parsing and reads as concealment to recruiters. What to use instead when your history isn't a straight line.

Aug 9, 20264 min read

Reading about ATS filters is step one. Beating them is step two.

Free account · 2 full scores every day · no credit card.