Are two column resumes bad for ATS?

What actually goes wrong

A parser reads a page in a single order and tries to sort what it finds into fields: employer, title, dates, skills. A two column layout has two reading orders, and the parser has to guess which one you meant.

When it guesses wrong, the columns interleave. A line from your sidebar lands between two lines of a job description. Your dates bind to the employer above or below the right one. Skills end up inside a role, or a job title ends up filed as a skill.

The result isn’t a rejection notice. It’s a database record about you that reads like nonsense, sitting in a system where a recruiter searches by keyword and simply never finds you.

Why the advice is so contradictory

Because both camps are describing something real. Modern parsers handle simple two column layouts far better than they did ten years ago, so plenty of people use one and get interviews. Meanwhile older systems, and any layout that puts columns inside a table, still fail badly.

So “two column resumes are fine now” and “two column resumes get you rejected” are both true some of the time, and neither tells you what to do. What you actually need to know is which risk you’re taking, and when it’s worth taking.

It’s worth noticing who tells you it’s fine. Most resume builders sell two column designs, because they photograph well and they’re what people pick. That makes the reassuring answer the profitable one.

Test your own file in two minutes

You don’t have to take anyone’s word for it, including ours.

1. Open your resume PDF.
2. Select all, copy.
3. Paste into a plain text editor, one with no formatting at all.
4. Read it top to bottom.

That output is roughly what the parser sees. If it reads in a sensible order, your layout is probably surviving. If your sidebar is spliced through your work history, you have your answer, and no amount of rewriting the words will fix it.

When a sidebar is still the right call

The trade is real in both directions. Two column resumes genuinely do look better to a person, and they let you show more without adding a page. Use one when you know a human sees it first:

• A referral, where your resume arrives by email rather than through a portal
• A recruiter you’ve already spoken to
• A small company with no applicant tracking system at all
• Anywhere you’re handing it over in person

Use a single column when you’re applying cold through a portal, which is most of the time. Keeping two versions of the same resume is entirely reasonable, and it’s what a lot of people who get interviews quietly do.

The things that break parsing worse

Two columns get all the attention, but these are more reliably damaging:

• Contact details in a header or footer. Many parsers ignore that region completely, so your phone number and email vanish.
• Text inside tables, which is often what a two column layout is underneath.
• A resume saved as an image, or a scanned copy. There is no text to read.
• Invented section names. “Where I’ve Been” is charming and unparseable. Use “Experience”.
• Dates in inconsistent formats, which breaks the link between role and time.

What doesn’t matter at all

Colour, typeface, bullet shape, and margins. None of it affects parsing. Those choices are for the person who reads you after the search, so make the document look like something you’d want to receive. Nobody has ever been filtered out for using navy.