Short answer: tables are risky for important resume content. Some applicant tracking systems can read simple tables, but others scramble the order, skip cells, or separate dates from job titles.
Why ATS systems struggle with tables
ATS parsers try to turn your resume into plain structured text. A table creates rows and columns that may not translate in the same order a human sees on the page.
Avoid tables for key sections
- Contact information.
- Skills.
- Work history.
- Dates and job titles.
- Education and certifications.
- Any keyword-heavy section you need the ATS to match.
What to use instead of tables
- One-column layout.
- Standard section headers like Summary, Experience, Skills, Education.
- Plain bullets.
- Dates written on the same line as the role or directly beside it in real text.
- Simple spacing instead of columns.
ATS-friendly layout checklist
- Can you highlight and copy the text from the PDF?
- Does the resume make sense when pasted into a plain text editor?
- Are role titles, companies, dates, and skills readable in order?
- Are there no icons replacing words like phone, email, or location?
How to test your resume before applying
Run the resume through Vertuelo Resume Checker and compare it with the job description. If the parser misses your job title, dates, or skills, fix the layout before applying.
FAQ
Can ATS read tables in Word documents? Some can, some cannot. Avoid tables for important content.
Are two-column resumes ATS friendly? They are riskier than one-column resumes.
Should I use a Canva resume for online applications? Use design-heavy resumes as portfolio visuals, not ATS application files.