Under an Hour: Recruiter Steps to Fix Two Column Resumes for ATS
A columned resume is a risky bet for any application that will pass through an applicant tracking system. If you’re submitting online, build a single-column version and save the columned design for people-only handoffs. The reason comes down to how parsers read a page and the reading-order mistakes columns tend to cause, which the workflow below walks you through fixing.
Key Takeaways:
- Two-column resumes risk misreading key details such as dates, job titles, and skills, which can lower ATS rankings despite the content being intact.
- Converting a columned resume into a single-column format typically takes less than an hour and significantly improves parsing accuracy by maintaining a logical top-to-bottom flow.
- File formats matter: use text-based PDFs or Word documents and avoid image scans or flattened exports that parsers cannot read reliably.
- Contact information should be in the main document body, not headers or footers, to prevent loss during parsing.
- Testing your resume with plain-text paste and parse previews helps ensure that information remains correctly mapped, especially before submitting online applications.
Table of Contents
- How ATS software actually reads your resume
- What actually goes wrong when columns get parsed
- When a two-column layout is actually fine
- The workflow to convert a columned resume to single-column
- File types and export settings that keep you parseable
- How to test your resume before you hit submit
- A recruiter’s pre-submit checklist
- Handling complex data that normally lives in columns
- Founder perspective: balancing design and deliverability
- Getting ATS-compliant help when you need it
- FAQ
- Sources
How ATS software actually reads your resume
Parsing engines aren’t reading your resume the way a hiring manager would. They’re hunting for structured fields: your name, contact details, job titles, dates, and skills, then slotting each into a database record. Most parsers reconstruct text in a fixed order, generally top to bottom and left to right, which means anything arranged side by side on the page can get read out of sequence.
That’s the core problem with columns. A sidebar skill list and a main-column job description sit next to each other visually, but a parser reading line by line may stitch them together in a way that scrambles both.
Workday’s own parser guidance warns that parsing results vary with format and word order, and recommends avoiding tabular and column layouts for the cleanest extraction.
- Parsers extract structured fields like contact info, education, experience, and summary text.
- Reading order follows position on the page, not your intended logical flow.
- Format and word order both affect how accurately a parser maps your content.
What actually goes wrong when columns get parsed
The failures are specific and repeatable. A sidebar skills list can get glued mid-sentence into a job bullet from the main column, turning “Managed a team of 12” into something unreadable once Python, Excel, and three other skill words land in the middle of it. Tables cause a different problem. Dates can separate from job titles, or entire cells of content can get trapped and dropped from the extracted text.
- Sidebar content often merges into adjacent job bullets, breaking sentence structure.
- Table cells can separate titles from dates or omit content entirely.
- Text boxes frequently get skipped by parsers altogether.
Parsing-benchmark testing has shown two-column layouts triggering critical flags and measurable score drops, with the issue traced to reading-order scrambling rather than missing words. The content is usually all there; it’s just mapped to the wrong fields or sequence, which can quietly tank your ranking in a recruiter’s search without you ever knowing why.
When a two-column layout is actually fine
Columns aren’t wrong in every context, only in the ones where a machine reads first.
- Use a columned, design-forward layout for portfolio PDFs or printed leave-behinds handed to a person.
- Use the same design for a resume emailed directly to a hiring manager who will open and read it themselves.
- Always keep a single-column source file ready for any online application portal.
If you do send a design-forward resume by email, attach a plain-text copy alongside it or link to a parsed profile as a backup, so nothing gets lost if the recipient’s system scans the attachment anyway.
The workflow to convert a columned resume to single-column
This takes under an hour for most resumes and removes nearly all the parsing risk columns introduce.
- Rebuild the page as one top-to-bottom flow: Summary, then Experience, then Skills, then Education.
- Pull sidebar items (certifications, tools, languages) inline under standard section headings instead of leaving them in a side rail.
- Convert any skills column into a comma-separated line or a simple bulleted list under a “Skills” heading. Indeed’s guidance on two-column resumes notes that one-column layouts tend to be more compatible with employer platforms than the two-column alternative.
- Delete tables, text boxes, and any embedded images.
- Move contact information into the body of the document, never into a header or footer field, since some parsers skip those sections entirely.
- Export as a text-based PDF or .docx, then paste the content into a plain text editor to confirm the order reads correctly from top to bottom.
Pro Tip: After converting, read the plain-text version out loud. If a sentence doesn’t make sense in order, a parser will struggle with it too.
File types and export settings that keep you parseable
The file format matters almost as much as the layout. A clean single-column resume can still fail if it’s exported the wrong way.
- Stick to text-based PDF or .docx; both let a parser extract actual text rather than guessing at an image.
- Avoid image-based PDFs and flattened exports, which some design tools produce by default and which parsers generally can’t read at all.
- Use standard fonts and simple bullet characters, and skip special characters or visual-only section headers that don’t match standard wording like “Experience” or “Education.”
- If a job posting specifically requests .docx, send .docx. If it accepts PDF, make sure it’s text-based, not a scanned or flattened image.
How to test your resume before you hit submit
Testing takes a few minutes and catches most problems before a recruiter ever sees them.
- Copy your resume text and paste it into Notepad or a similar plain editor, then scan whether the reading order still makes sense.
- Run it through a parser preview or a quick parse test to check that your name, email, job titles, dates, and skills all extracted into the right fields.
- Retest after every structural change. You’re aiming for all your primary fields mapped correctly, with nothing merged or missing.
A recruiter’s pre-submit checklist
After years of reviewing resumes from the hiring side, a few checks catch most problems before they cost you an interview.
- Contact information sits in the document body, not in a header or footer.
- Section headings use standard wording: Experience, Education, Skills, Summary.
- Work history reads in a clear chronological order with no gaps that look like formatting artifacts.
- Bullet points sit directly under the job title and dates they describe.
- The file is a text-based PDF or .docx, never an image export.
- A plain-text paste test shows information in the correct, logical order.
Pro Tip: If you’ve rebuilt your resume twice and it still comes out scrambled in plain text, that’s usually a sign the underlying template, not your edits, is the problem.
A full executive-level rewrite, a situation with high conversion risk, or any case where the stakes feel high is often where bringing in a professional pays for itself faster than another round of DIY fixes.
Handling complex data that normally lives in columns
Some content genuinely seems built for columns: certifications next to dates, technical skills grouped by category, or a timeline of roles with locations attached. You can keep that information organized without using an actual column layout.
For skills grouped by category, use a bolded sub-label on its own line followed by a comma-separated list, rather than a side-by-side grid. For certifications or licenses with dates, write them as a short list under an “Education and Certifications” heading rather than a two-column table pairing credential against date.
If you’re tempted to use tabs to line up dates on the right side of the page, resist it. Tabs and tables both risk the same cell-trapping and order problems as true columns, since many parsers read them the same way. A simple format like “Project Manager, Acme Corp, March 2022 to present” keeps every piece of information in one readable line that a parser can extract without guessing which field a tab-separated number belongs to.
The same logic applies to multi-location roles or projects: write the location inline after the company name instead of putting it in a separate column. It looks slightly less polished, but it helps ensure the parser attaches the right date and location to the right job.
Founder perspective: balancing design and deliverability
A resume’s job is to get read, by a machine first and a person second. Design matters, but only after the content survives the first gate. For online applications, single-column wins every time. For executive clients, we typically deliver an ATS-clean source file alongside a design-forward version reserved strictly for people-only handoffs, so neither goal gets sacrificed.
Kim
Getting ATS-compliant help when you need it
Converting a resume by hand works, but executive-level rewrites often involve more than reformatting: rebuilding the narrative, tightening the summary, and making sure every section still reads well once the columns are gone. That’s the work we focus on.
Our Evolution package covers an executive resume, LinkedIn profile and cover letter for $699, one payment. For more hands-on, ongoing support, see the Elevate packages page for details and pricing. Every deliverable comes as a single-column source file plus a text-based PDF, tested before it reaches you. If you want a fully managed job search with tailored applications and outreach, check out Elevate and Land. Start at Resume Wiz to see which package fits your timeline.
Want a recruiter in your corner for your next senior role? Book a free call with Resume Wiz and we will map out your next move together.
FAQ
Does ATS recognize columns?
Some systems can read simple two-column layouts, but results are inconsistent across different ATS platforms, and the risk increases with complexity. Workday’s parser guidance specifically recommends avoiding tabular and column formats for the most reliable parsing.
Is an ATS score around 70% generally good?
Parsing scores vary by tool and testing method, so there’s no single universal benchmark for what counts as good. A safer approach is confirming that every primary field, your name, contact details, job titles, dates, and skills, extracts correctly and in the right order rather than chasing a specific percentage.
Is a two-column resume bad for ATS?
Two-column resumes carry real risk because many parsers read left to right across the full line, which can interleave sidebar content with your main job descriptions. Indeed’s guidance recommends a simple one-column format specifically because it tends to be more compatible with employer platforms.
Is an ATS score around 80% generally good?
As with any parsing score, the number itself matters less than what’s actually missing or scrambled in the extracted text. Focus on verifying reading order and field mapping through a plain-text check rather than treating any single percentage as a pass or fail line.
