You've probably heard conflicting advice about tables in resumes. Some say they're fine, others warn they'll get you rejected by an ATS. The truth is more nuanced. This article gives you a direct answer to 'should tables be added in an ATS-friendly resume?' and explains how to structure your resume so it reads well for both software and humans.
What 'should tables be added in an ATS-friendly resume' actually means in practice
When you ask whether to use tables, you're really asking: will an applicant tracking system (ATS) correctly read my resume if I use a table? An ATS is software that parses resumes into a database. It looks for standard sections like Work Experience, Education, and Skills. If your resume uses a table, the ATS might read the text in the wrong order, miss information, or misattribute it. For example, a two-column table with 'Skills' on the left and 'Proficiency' on the right might be read as 'Skills Proficiency Excel Advanced' instead of pairing each skill with its level. That garbled data can hurt your chances. So the practical question is: does the benefit of using a table (visual organization) outweigh the risk of parsing errors? For most job seekers, the answer is no. But there are exceptions, which we'll cover.
Step-by-step guidance for deciding on tables
Follow these steps to make an informed choice for your resume.
- Step 1: Check the job posting. If it says 'submit in Word or PDF' without specific formatting rules, you have some flexibility. If it mentions 'ATS-friendly' or 'plain text', avoid tables.
- Step 2: Research the company's ATS if possible. Large companies often use systems like Workday, Taleo, or Greenhouse. These generally handle simple tables better than older systems, but why risk it?
- Step 3: Test your resume. Upload your resume to a free ATS parser (like Jobscan or Resumeworded) and see if the table content is extracted correctly. If it's scrambled, remove the table.
- Step 4: Consider the content. If you're using a table to list skills with proficiency levels, try a simple comma-separated list instead. If you're using a table to align dates, use right-aligned tabs or a single-column layout with dates on the same line as the job title.
- Step 5: Prioritize clarity. A resume that reads well when copied into a plain text editor is usually ATS-friendly. If your table breaks that, it's not worth it.
Tip: A simple test is to copy your resume text and paste it into Notepad. If the order is jumbled or information is missing, an ATS may struggle too.
Concrete worked example: Table vs. no table
Let's say you're a data analyst and you want to show your skills and proficiency. Here's how a table might look (illustrative example):
Table version (risky): A two-column table with 'Skill' and 'Proficiency'. An ATS might read it as 'Skill Proficiency SQL Advanced Python Intermediate Tableau Advanced' — losing the pairing. A human sees it fine, but the ATS may not.
No-table version (safer): Use a simple list: 'Skills: SQL (Advanced), Python (Intermediate), Tableau (Advanced)'. This is easy for both ATS and humans to read. For work experience, instead of a table aligning dates, write: 'Data Analyst, ABC Corp (Jan 2020 – Present)'. This keeps the reading order logical.
Here's an illustrative professional summary that avoids tables entirely:
"Detail-oriented data analyst with 6 years of experience turning complex datasets into clear business insights. Skilled in SQL, Python, and Tableau. Reduced reporting time by 30% through automated dashboards. Looking to apply analytical rigor to a growing fintech team."
And here are five illustrative bullet points you might use in your experience section:
- Built a sales dashboard in Tableau that cut weekly reporting time from 5 hours to 45 minutes.
- Wrote SQL queries to extract and join data from 4 sources, supporting monthly revenue forecasts.
- Automated a manual data-cleaning script in Python, reducing errors by 25%.
- Presented A/B test results to marketing, leading to a 12% increase in email click-through rate.
- Trained 3 junior analysts on best practices for data validation and documentation.
These bullets are specific and quantifiable, and they don't rely on tables to be understood.
Practical checklist for an ATS-friendly resume
Use this checklist to ensure your resume is parsable and professional. For more on which sections to include, see our guide on essential resume sections.
- Use a single-column layout. Avoid multi-column designs unless you're certain the ATS can handle them.
- Stick to standard section headings: Work Experience, Education, Skills, etc. Creative headings can confuse parsers.
- Avoid tables, text boxes, headers/footers, and images. These often cause parsing issues.
- Use a common font like Arial, Calibri, or Times New Roman, size 10–12 pt.
- Save as .docx or .pdf unless the job posting specifies otherwise. PDFs are generally safe now, but .docx is sometimes safer for older ATS.
- Include keywords from the job description naturally in your bullet points and skills list.
- Proofread for typos and consistent formatting (dates, punctuation).
- Test your resume with an ATS parser tool to catch issues early.
For a deeper dive into structuring your resume sections, check out choosing resume sections and sections you can safely remove.
Frequently asked questions
Can I use tables in my resume if I'm applying to a small company?
Small companies may use simpler applicant tracking systems or even read resumes manually. However, it's safer to avoid tables unless the job posting explicitly asks for a specific format. A clean, single-column layout works everywhere.
What's the best way to include a two-column layout without using a table?
Use tab stops or a simple text-based layout with clear headings. For example, put the section title on its own line, then list items below. This keeps the reading order logical for both humans and software.
Will a table cause my resume to be rejected by an ATS?
Not necessarily rejected, but it may cause parsing errors. Some ATS may read the table column by column, scrambling your text. To avoid risk, use a single-column format with standard headings.
Ready to build a resume that sails through ATS? Try our ATS Resume Builder to create a clean, parsable resume in minutes. Check our pricing for affordable options.
Frequently asked questions
Can I use tables in my resume if I'm applying to a small company?
Small companies may use simpler applicant tracking systems or even read resumes manually. However, it's safer to avoid tables unless the job posting explicitly asks for a specific format. A clean, single-column layout works everywhere.
What's the best way to include a two-column layout without using a table?
Use tab stops or a simple text-based layout with clear headings. For example, put the section title on its own line, then list items below. This keeps the reading order logical for both humans and software.
Will a table cause my resume to be rejected by an ATS?
Not necessarily rejected, but it may cause parsing errors. Some ATS may read the table column by column, scrambling your text. To avoid risk, use a single-column format with standard headings.