8 min read
Your PDF can look sharp while the importer builds a profile that reads like a ransom note. That's not drama. It's what happens when a two-column template meets a parser that only knows how to walk one line at a time.
Check your resume for free on the same file you'll upload tonight. You're confirming Experience rows and dates survived, not whether the margin looks modern.
How ATS handles columns and tables isn't a design debate. It's read order. Once you see the plain-text stream, you'll know whether to flatten layout or stop tweaking bullet verbs.
Job searching is already draining. You don't need a mystery where Greenhouse shows skills but no employers. We'll match symptoms to layout causes, then rebuild the file recruiters can actually search.
Quick wins
- Export single column before any Workday or Greenhouse upload.
- Paste the whole file into a plain-text editor and read employers aloud.
- Replace skill grids and contact tables with typed lines and bullets.
What parsers do when they hit columns
Think of the ATS as a tape reader, not a designer. It strips characters into one sequence. Multi-column Word sections, Canva sidebars, and table cells are still just boxes of text. The importer picks an order, often left column first or top row left to right, then moves on.
That order rarely matches how you'd tell your story out loud. Your latest job might sit visually on the right while the parser dumps Certifications and Tools from the left rail above every employer name. Recruiters who search on imported title or years of experience then see a thin profile even though your PDF looks full.
Tables add cell boundaries. A simple two-column contact row can split name from phone. Experience tables with title in column one and dates in column two sometimes merge into one mashed line or drop the date column entirely in Lever or Taleo uploads.
Before: Sidebar lists Python, SQL, and Tableau above a right-column job at Acme Corp.
After: Skills section sits under Experience with bullets that repeat those tools beside Acme outcomes.
Before: Month Year dates live in the right cell of a table row under each title.
After: One line per role: Senior Analyst, Acme Corp, March 2021 to Present, then bullets underneath.
This won't fix applying to roles where you're missing licensed credentials or required years. It stops a qualified file from looking empty because the machine read the sidebar first.
Symptoms that point to layout, not fit
Match what you see in the portal or paste preview to a cause before you rewrite summary keywords.
| What you see | Likely layout cause |
|---|---|
| Skills filled, Experience empty | Sidebar or left column read first; body rows never mapped |
| Title and dates on one garbled line | Table cells merged in extraction order |
| Jobs out of chronological order | Multi-column section breaks between employers |
| Contact info missing in search | Header/footer table skipped by parser |
I've screened stacks of these in Workday and Greenhouse, and the file that survives is almost always a single-column DOCX where paste-test reads like a phone screen story, not a design portfolio.
When titles and dates glue together, read why ATS merges job titles and dates for the table-and-tab patterns that trigger it.
Diagnose how ATS handles columns and tables on your file
Run these checks on the exact export you'll attach. If any step fails, stop tailoring content until layout passes.
Step 1: Full-document paste test
Open the PDF or DOCX, select all, paste into Notepad or TextEdit. Read from the top. Your name and contact should appear before section headers. Your most recent employer should appear before older roles without a skill list in between.
Step 2: Compare to portal preview
Upload to a sandbox application or reuse a recent submission preview. If Skills populates while Experience stays blank, you have a column-order problem, not a keyword problem.
Step 3: Flatten and retest
Copy-paste skeleton for a single role line after you remove tables:
Senior Data Analyst | Northwind Health | Minneapolis, MN
March 2021 to Present
• Built weekly patient access dashboards in Tableau; cut report turnaround from 3 days to same-day for clinic ops.
• Partnered with Epic analysts on SQL extracts for no-show risk lists used in daily huddles.
Before: Two-column Canva PDF with tools on the left and jobs on the right; paste shows Tableau lines before Northwind.
After: Single-column Word file; paste shows Northwind title, dates, then bullets that name Tableau and SQL in context.
Before: Experience stored in a three-column table (company, title, dates).
After: Vertical stack with employer line, date line, and bullets only.
Re-run paste-test after each flatten. You're done when read order matches how you'd walk a recruiter through your last three years in thirty seconds.
Column and table traps that still look professional
Nested tables inside section headers are common on downloaded templates. They survive visually but break when Greenhouse walks cells row by row.
Skill proficiency grids (tool name in one cell, bars or dots in another) often import as orphan tool names with no job attachment. Type the tools inside bullets instead.
Invisible column breaks in Google Docs still create two streams on export. Turn on show formatting marks and remove column sections entirely.
Text boxes for summaries float outside body flow. Parsers skip them or drop them at the end after Skills. Keep the summary as normal body text under your name.
And don't trust a template because the job posting showed a table sample. Posting PDFs are marketing. Your upload still has to survive iCIMS or Workday extraction.
DOCX, PDF, and when file type cannot save a grid
Switching from PDF to DOCX does not fix two columns. It only changes the wrapper around the same read order problem. DOCX is often easier to rebuild when you're deleting column sections and tables in Word or Google Docs.
Use text-based PDF exported from Word after layout is flat when the posting requires PDF. Avoid design-tool PDFs where type is outlined or embedded as shapes. Those fail even in one column.
For upload hygiene on enterprise stacks, skim Workday resume format after your paste-test passes. Format rules only help once the text stream is honest.
Tools after layout passes paste-test
Run the checker on the flattened file first. Empty Experience in the scan means go back to columns, not forward to keyword stuffing.
Run a free ATS scan on the DOCX or PDF you plan to submit. You're looking for section mapping, not a vanity score.
When employers and dates look right, Score your job match against the posting and tune bullet one. Layout work and content work stay in that order.
Flatten first, tailor second
How ATS handles columns and tables comes down to extraction order. Sidebars and grids look tidy on screen and chaotic in plain text. Single-column body flow is boring on purpose so Workday and Greenhouse can attach dates to the jobs you actually held.
Tonight, paste-test before you rewrite summary lines. If employers survive in order, you've earned the right to tune bullets. If they don't, no amount of keyword paste will fix an empty Experience row.
Keep a designed PDF for humans if you want one. Ship the flat file to portals. That's the split that stops silent import failures.
After layout is stable, you can generate a cover letter that points at bullet one instead of repeating a broken import preview.
Read more
Frequently asked questions
Most importers flatten the file into one stream and often grab the left column or sidebar first. That is why skills and contact blocks can appear above your latest employer in plain text even when the PDF looks balanced. There is no universal rule across Workday, Greenhouse, Lever, and iCIMS, which is why a paste test beats guessing.
Contact tables in headers are a common failure point. Parsers sometimes skip header rows entirely or read phone and email without your name. Move contact lines into the body on the first three rows. If paste-test shows your name after your skills list, the table placement is already hurting you.
Yes, but upload a single-column export for portals. Keep the pretty PDF for email intros if you want. The application file should be the boring one where employers stay in reverse chronological order in plain text. Two files, two jobs.
Full Skills or Certifications in the portal preview with blank or partial Experience is the classic pattern. Merged job titles and dates on one line is another. If keywords show up but dates and employers do not, you are usually looking at layout read order, not keyword density.