It is best to avoid tables in an ATS resume. Some modern applicant tracking systems read simple tables fine, but many still flatten a table into a single jumbled line or read it column-by-column — scrambling your dates, titles, and bullets in the parsed text a recruiter actually searches. Because you cannot know which ATS a given employer uses, the safe choice is a single-column, table-free layout. You get the clean alignment you wanted from a table by using tabs, columns of text, and white space instead.
Why tables are risky
A table looks tidy to a human because your eyes follow the visual grid. An applicant tracking system does not see the grid — most parsers convert the document into a linear stream of text and try to label each piece (this is a job title, this is a date, this is a bullet). Tables break that step. Depending on the parser, a two-column row can be read straight across (gluing a skill to an unrelated date) or down each column (tearing a title away from the company and dates that belong to it). The resume on your screen still looks perfect; the text the ATS stored and ranks you on is scrambled.
| Layout choice | How an ATS tends to read it | Risk |
|---|---|---|
| Single-column, no tables | Clean top-to-bottom text, correctly labeled | Low |
| Simple 2-column table (skills) | Sometimes fine, sometimes flattened to one line | Medium |
| Table for the whole layout | Often scrambled or read column-by-column | High |
| Text boxes / sidebars | Frequently skipped entirely | High |
What to use instead
You almost certainly reached for a table to line things up — dates flush right, skills in neat columns. You can get the same look without the parsing risk:
- Right-aligned dates: use a tab stop, not a table cell, to push dates to the right margin. It reads as one line of text to the parser.
- Skills lists: a simple comma-separated line or the editor's native multi-column text feature beats a table grid.
- White space and bold: spacing and weight create structure a human reads instantly and a parser ignores harmlessly.
Two-column table — left cell: "Senior Analyst, Acme"; right cell: "2021–2024". Parser reads down each column: "Senior Analyst, Acme | Data Lead, Globex …" then "2021–2024 | 2018–2021 …" — titles and dates fully separated.
Single line of text with a right tab stop: "Senior Analyst, Acme ........ 2021–2024". Parser reads it as one labeled entry, title and dates intact.
Same visual alignment, completely different parsed result.
How to verify before you apply
The fastest check is free: save your resume as plain text, or copy it into a blank document, and read it top to bottom. If anything is out of order or merged, fix the layout. For a closer look at keyword coverage and parsing, Jobscan's ATS guide and a resume scan will flag the same issues an employer's system would. The principle is simple and consistent across sources: if a parser can read it cleanly as one column of text, it is ATS-safe.
The honest summary
Skip tables. A single-column, table-free resume is the only layout that parses reliably across every applicant tracking system, and you lose nothing visually — tab stops and white space recreate the alignment you wanted. When in doubt, read your resume as plain text; if it makes sense to you in that form, it will make sense to the ATS.
Common questions
- Should tables be added to an ATS-friendly resume?
- No, as a default. Tables are the single most common cause of garbled ATS parsing. A few systems handle simple tables, but plenty do not, and you usually cannot tell which one an employer runs. A single-column layout with no tables parses reliably everywhere.
- Why do tables break applicant tracking systems?
- Many parsers read a page by flattening its layout into linear text. A two-column table can be read left-to-right across rows (mixing unrelated cells) or column-by-column (separating a job title from its dates). Either way, the structured text the ATS stores and searches no longer matches what you see on screen.
- How do I get clean alignment without a table?
- Use the document’s built-in tab stops, simple multi-column text, and right-aligned dates rather than table cells. Visually it looks aligned; structurally it is still a single readable stream of text the parser handles correctly.
- How can I tell if my resume’s tables caused a problem?
- Save your resume as plain text (or copy-paste it into a plain editor) and read it top to bottom. If titles, dates, and bullets appear out of order or merged together, an ATS will likely see the same scramble. Running it through an ATS scan surfaces the same parsing issues.
Sources
Keep reading
What does an ATS-friendly resume look like?
An ATS-friendly resume is single-column and plain-text, with standard headings, readable dates, and no tables or graphics. Here is the exact anatomy.
Why is my resume getting rejected by ATS?
ATS rejection has two causes: parse failures from bad formatting and keyword gaps against the job description. Here is how to diagnose and fix yours.
How do I check if my resume is ATS-friendly?
Check two things: that your resume parses (read it as plain text) and that it matches the job (scan it for keywords). Here is the free, step-by-step method.