Two-column résumé templates still show up everywhere — a narrow sidebar for skills and contact info, a wider column for experience, sometimes a subtle table for the education dates. They look sharp in a design tool. They also scramble in the one piece of software almost every applicant meets first: the applicant tracking system's parser.
This isn't a keyword-stuffing problem, and it isn't solved with a "beat the ATS" trick. It's a plain reading-order problem, and the fix is the same for the parser and for the recruiter who opens the file five seconds later: one column, top to bottom, in the order you'd tell your story out loud.
What a parser actually does with a page
An ATS parser doesn't "see" a résumé the way you do. It doesn't understand a sidebar as a sidebar or a table as a skills grid. Most parsers read a PDF or DOCX the same way a screen reader might: left to right, top to bottom, following the underlying text stream — not the visual layout you designed.
That distinction is where columns fall apart:
- Columns get read across, not down. A parser frequently stitches a line from your left sidebar to a line from your right column, because both sit at roughly the same vertical position on the page. "Python, SQL" from your skills column can end up glued to "Senior Engineer, Acme Corp" from your experience column — one garbled line where two clean ones used to be.
- Tables often don't parse as rows at all. Depending on how the table was built, a parser may read every cell in the first column before touching the second — meaning your job titles all come before any of your dates or companies, in whatever order the underlying document stores them.
- Text boxes can vanish entirely. Content dropped into a floating text box sometimes isn't part of the main text stream a parser extracts at all. It renders fine to the human eye and disappears to the software — the opposite of what a keyword-conscious candidate wants.
- Headshots, icons, and graphic skill meters add no signal and real risk. A five-star graphic for "Excel" doesn't parse as a skill level; at best it's ignored, at worst it interrupts the text stream around it.
None of this is a bot trying to reject you. It's software doing a genuinely hard job — turning a laid-out page back into structured text — and columns, tables, and text boxes are exactly where that job gets unreliable.
Why the fix is boring on purpose
The advice that follows from this isn't clever, and that's the point:
- One column, top to bottom — no side rail, no multi-column skills block.
- Standard section headings ("Experience," "Education," "Skills") instead of stylized labels a parser has no reason to recognize.
- Selectable text, not an image of a résumé or a scanned PDF.
- A common, embeddable font, Letter or A4 page size.
- No headshot, no icons, no progress-bar skill meters.
Every one of those choices reads the same way to a recruiter skimming your file at 11pm between fifty others: fast, in order, with nothing to decode. A single-column layout was never a compromise you make for the software — it's the layout that serves both readers at once, which is the only design brief that actually matters here.
The résumé that parses cleanly and the résumé that reads fastest are the same document. Chasing one gets you both.
The "but it looks plain" objection
Plain is the feature, not the cost. A hiring manager scanning forty résumés for one open role isn't rewarding visual flair — they're rewarding the ten seconds it takes to find your last title, your last company, and the one bullet that matches what they need. A two-column layout asks them to hunt for that. A single column hands it to them in the order they expect.
Where you actually earn attention is in the writing — bullets that use the posting's language because the accomplishment is real, a summary that states your fit in one line, gaps you've decided to address honestly instead of hiding behind a sidebar. Layout should be invisible. Content is where the differentiation lives.
What Tailr exports, and why
This is the layout Tailr renders by default, with no toggle to turn it off, because there's no version of "fancier columns" that beats it for either reader. Every tailored résumé comes out as a single page, single column, with standard headings and fully selectable text — available as both PDF and DOCX, at Letter or A4, so you can hand a recruiter whichever format their system prefers without reformatting anything yourself.
The auto-fit logic that keeps it to one page tightens spacing and scales the page as a whole, down to a legible floor — no silent shrink to unreadable type, and no quiet overflow onto a second sheet. Nothing about the layout — no tables, no text boxes, no skill meters — gives a parser a reason to misread your history, and nothing about it makes a person work harder than they have to.
The bottom line
Two-column templates are a design decision made for a screen, not for the two very different readers who'll actually open your file. A parser reads top to bottom through a text stream; a recruiter reads the same way, just faster. Single column, standard headings, selectable text — it's the plainest possible choice, and it's plain because it's correct for both audiences at once.