Resume Tables and ATS: What Breaks and What to Use Instead | Resume Wiz

Resume Tables and ATS: What Breaks and What to Use Instead

November 02, 2026

An applicant tracking system can often pull the words out of a resume table, but it frequently loses the structure around them. Skills, dates and job titles can end up in the wrong order or in the wrong profile fields. The safest approach is a single-column resume with no tables, and the rest of this guide shows you how to build one and check it.

Resumewiz
Make Your Resume ATS-Ready
Resume Wiz develops tailored resumes with ATS-compliant formatting to help professionals present their experience clearly to employers.

Key Takeaways:

  • Tables, columns, text boxes, headers and footers are the layout elements most likely to cause a partial or failed parse. Greenhouse’s support documentation lists them by name.
  • The words in a table usually survive. The reading order and the link between a label and its value often do not.
  • Replace tables with plain headings, bullets and right-aligned dates or simple separators, and keep contact details in the body of the page.
  • Export a real DOCX or PDF from your word processor, never an image, then run the plain-text test before you apply.
  • If your resume feels too plain, strengthen the content, not the layout. Recruiters still read it after the software does.

Table of Contents

What an ATS does with a table

Most large employers run your resume through a parser before a person sees it. The parser scans the uploaded file and fills in candidate-profile fields such as name, employer, title, dates and skills. Greenhouse says that when this fails, the resume stays attached to the profile, but someone has to enter the details by hand. In practice, a recruiter looking at a busy requisition may not do that work, and your profile can look thinner than your resume actually is.

A table makes that job harder because a parser reads text as a stream. It does not see a grid the way you do. Workable explains that tables and columns can put words, and sometimes individual letters, on different lines, so sentences may come out in an order you did not intend.

So the honest answer to “can an ATS read tables?” is: often partly. It can usually extract the text. What it cannot reliably keep is the meaning that the layout carried, such as which date belongs to which job.

What the employers and universities say

The guidance from people who actually run these systems is consistent.

  • Greenhouse says complex resumes with tables, headers, footers, columned layouts, and contact information in headers, footers or text boxes may be partially or unsuccessfully parsed.
  • MIT Career Advising and Professional Development recommends avoiding tables and text boxes because an ATS may distort, ignore or erase them, and because extraction can recombine information inaccurately.
  • Roche, in its own candidate FAQ, tells applicants to avoid tables, columns, headers and footers, noting that some systems read columns straight across and may drop header or footer information.

Three different kinds of source, one message. If an employer publishes instructions for applicants, follow them first. Where it says nothing, a table-free resume is the low-risk default.

Why tables break parsing

It helps to know what is happening underneath, because it explains why a table that looks perfect on screen can fail.

Adobe explains that in a PDF, a table is stored as line segments and separately positioned pieces of text. No rows or columns exist behind the picture. A parser has to guess the structure from coordinates, and a guess can go wrong.

Consider a common layout: a two-column table with “Skills” on the left and a list on the right, or a job-history table with dates in a narrow left column. A parser that reads left to right across each line might produce something like this:

2019 to 2023 Director of Operations Python, SQL Led a team of 40 Northwind Logistics Tableau

The dates, title, skills and employer are all present. They are also mixed together, and a field-extraction step now has to decide which is which. Some systems do this well. Some do not. You cannot see which kind the employer uses, so you remove the variable.

Columns, text boxes and the other layout traps

Tables are one member of a family. The same logic applies to anything that places text by position rather than in sequence.

Two-column layouts. Adobe notes that some vendors have improved how they handle columns, yet roughly 1 in 10 resumes in its evaluations still rendered poorly. That is the reason it recommends avoiding two-column designs. One in ten is a bad rate when the downside is a scrambled profile. If you currently use columns, our walkthrough on fixing two-column resumes for ATS shows the conversion step by step.

Text boxes. They sit outside the main flow of the document, so a parser may skip them or read them out of order. MIT lists them alongside tables as elements an ATS may ignore or erase.

Headers and footers. Workable points out that headers and footers can be improperly interspersed with the main body text. Greenhouse specifically flags contact information placed there. Put your name, phone, email and city in the first lines of the page body.

Graphics and skill bars. A five-dot rating or a progress bar carries no text. The parser sees nothing, and a recruiter learns nothing precise from it either. Write the skill as a word.

When is a table reasonable?

This is the question people search for after they have read the warnings, and it deserves a straight answer.

No source we reviewed identifies a situation where a table is the better choice for an ATS submission. So the practical rule is: if the resume will be uploaded to an employer’s application system, do not use a table.

Here is how we think about the edge cases.

  • A resume that will be emailed to a person, not uploaded. A human reader is not affected by parsing, but you often cannot know whether the recipient will forward it into a system. A table-free version costs you nothing, so we still send that one.
  • A portfolio or a leave-behind for an interview. A designed document can make sense when someone has already chosen to meet you. Keep it separate from the version you upload, and keep the same facts in both.
  • A table that only looks like a table. Some resumes use a table purely for alignment, with invisible borders. The borders disappear, but the table structure remains in the file, so it carries the same parsing risk.

If you are unsure which situation you are in, use the plain version. The cost of a plain resume is a slightly less decorative page. The cost of a failed parse is a profile a recruiter has to retype.

What to use instead of a table

Most tables on resumes do one of four jobs. Each has a plain replacement that parses cleanly and reads well to a person.

What the table was doing Table-free replacement
Putting dates in a left column next to jobs Put the title and employer on one line, then the dates on the next line or at the right margin using a right-aligned tab stop
Showing skills in a grid A single “Skills” heading followed by a short comma-separated line or grouped bullets, such as “Platforms: Salesforce, SAP”
Placing contact details in a top banner Plain lines at the top of the body: name, city and state, phone, email, LinkedIn URL
Splitting the page into sidebar and main column One column, with education, certifications and skills as sections below experience

A few practical notes on this.

Use a tab stop, not spaces or a table, to align dates. A right-aligned tab keeps the date on the same line as the title, and the text stays in sequence for a parser.

Group skills with a label. “Finance: budgeting, forecasting, variance analysis” reads quickly to a person and gives a parser a clean line. Our guide to the skills section covers how to choose what goes in it.

Keep bullets simple. Standard round bullets are fine. Avoid decorative symbols that may turn into odd characters in the extracted text.

Use one standard font. Workable lists standardizing font usage among its core recommendations for correct text extraction.

Headings the parser expects

Layout is half the problem. The other half is labeling. Roche recommends conventional headings such as Education, Work Experience and Technical Skills. Creative headings like “My Journey” or “Where I’ve Made an Impact” give the software nothing to anchor on.

For most senior professionals, a safe structure looks like this:

  1. Name and contact details
  2. Professional Summary
  3. Work Experience (or Professional Experience)
  4. Education
  5. Certifications
  6. Skills

Keywords matter too, but they work only if the parser can place them. For the content side, see our explanation of what really happens with resume keywords and ATS rejection.

Choosing DOCX or PDF

The file type matters as much as the layout. Greenhouse says an uploaded resume should be a document such as DOCX or PDF, not an image, and that image uploads may not parse. It also states that it cannot parse resumes larger than 2.5 MB, which is rarely a problem for a text resume, but can be if you embed pictures.

If you choose PDF, export it from your word processor rather than scanning a printout. A scan is an image, even if it has a .pdf extension.

When the job posting names a format, use that format. When it does not, our breakdown of how recruiters choose between PDF and Word walks through the checks.

The plain-text test: check your resume in two minutes

You do not need to buy a scanner score to find out whether your layout is safe. MIT suggests saving or exporting your resume as plain text and reading the result. Missing text points to a conversion or formatting problem, and text in the wrong order points to structural issues such as tables, text boxes or columns.

Here is how to run it.

  1. Save a copy of your final resume as a plain text (.txt) file from your word processor.
  2. Open the .txt file in a basic text editor.
  3. Read from the top. Is your name first, followed by your contact details?
  4. Check that each job’s title, employer and dates sit together, in that job’s section.
  5. Look for anything missing: a phone number, a certification, a skills line.
  6. Look for anything scrambled: two jobs interleaved, or a date floating at the end of the document.
  7. If something is wrong, find the table, column, text box or header that caused it, rebuild that part as plain text, and test again.

A resume that reads cleanly in plain text is in good shape for a parser. It is not a guarantee, because each employer’s system differs, but it removes the most common causes of failure. For a deeper checklist, see our ATS-compliant resume formatting guide.

Our perspective

We read resumes as recruiters before we write them as career strategists, and the pattern we see most often with senior candidates is this: the content is strong and the container is the problem. An executive with a decade of measurable results sends a designed, two-panel document, and the first system to touch it reorders the story.

Our view is that a resume has two readers, a parser and a person, and it has to satisfy them in that order. A clean single-column structure does that without limiting you. Where design belongs is in clear hierarchy, sharp metrics and a summary that tells a hiring manager in five seconds why you fit.

That is why our documents are built to be ATS-compliant from the first draft, then tailored to the role and the decision-makers behind it. A resume that is easy to parse is the starting point. A resume that earns the interview is the goal, and the two are not in conflict.

Kim

Get a resume that parses and persuades

If you would rather not rebuild it alone, our Evolution package ($699) gives you a recruiter-written executive resume, LinkedIn profile and cover letter built to read cleanly for both people and parsers.

Common formatting mistakes that sit next to tables

People who remove a table often keep other habits that cause the same trouble. Run through this list before you submit.

  • Contact details in the header. Move them into the body.
  • Icons for phone and email. Use the words or just the number and address.
  • Several fonts and sizes. Pick one font and use size and bold sparingly for hierarchy.
  • Unusual section names. Swap them for the conventional ones above.
  • A file name like “final_v7”. Use your name and the word resume, so the recruiter can find it later.

For a wider list, see our guide to resume formatting errors to avoid, and for the commercial cost of getting layout wrong, why layout costs you interviews. If you want to understand the screening stage itself, our job seeker’s guide to ATS scanning explains it in plain terms, and why resumes get rejected by ATS covers the other causes.

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

Can an ATS read a table in a resume?

Usually it can extract the words, but it may lose the structure. Greenhouse states that resumes with tables may be only partially parsed or may fail to parse. The result can be details in the wrong fields or in the wrong order, so a table-free layout is safer.

Is a table with invisible borders safe?

Not reliably. Hiding the borders changes how the table looks, not how it is stored in the file. A parser still meets the same cell structure, so the same risks apply. Use a right-aligned tab stop or a simple line instead.

Are two-column resumes also a problem?

They carry similar risk. Adobe reports that some systems have improved, yet about 1 in 10 resumes in its evaluations still rendered poorly. Roche also warns that some systems read columns straight across. A single column avoids the issue.

Should I submit a PDF or a Word file?

Follow the employer’s instructions if they state a format. Otherwise, either a DOCX or a PDF exported from your word processor is a document format that Greenhouse identifies as acceptable. Avoid image files and scanned pages.

How do I know my resume will parse correctly?

Save it as plain text and read it from top to bottom. Everything should be present, and each job’s title, employer and dates should stay together in order. Missing text or jumbled order points to a table, column, text box or header that needs rebuilding.

Sources

resume tables ats
Back to Blog