Are tables always bad on a résumé

They are a risk rather than a certainty. Some extractions flatten a table into the right order and some interleave it, and you cannot see which will happen.

What about invisible tables used for alignment

Same risk. The borders are a visual choice; the grid is what the file contains, and the grid is what has no reading order.

How should I align dates on the right then

With a tab stop or the design's own layout rather than with a table cell. Every design here places dates without a grid.

Do text boxes cause the same trouble

Yes, and often worse. A floating box is its own object and can land anywhere in the extracted stream, including mid-sentence.

Will the checker tell me I used a table

It deducts twenty-two points when it detects a table or multi-column pattern in the extracted text. Where a table has already been flattened, there is nothing left to detect, so read the counts as well as the findings.

Guide · ATS

Tables, text boxes and what they do to a parse

A table gives an extractor a grid and no rule about which way to walk it. Here is what that does, what to build instead, and what a checker can honestly detect.

ConxfolioPublished 2026-09-12

— a grid has no reading order.

A table is a grid of cells. Reading it requires a rule about which way to walk the grid, and the file does not contain one. That is the entire problem, and it explains every symptom people describe.

What goes wrong

An extractor walks the cells in whatever order the file stores them. Sometimes that matches the order you intended. Sometimes it produces the first cell of every row before the second cell of any row, which is how job titles end up separated from their dates and bullet points end up under the wrong employer.

Invisible tables count

Borders are a visual setting. A table with no visible lines, used to align dates on the right or to build a skills grid, is exactly the same object inside the file as one with lines. Removing the borders removes the evidence, not the risk.

Text boxes and sidebars

A floating box is its own small document inside the file, and it can be extracted at any point in the stream. A contact sidebar can arrive in the middle of a bullet point, or at the very end, or not at all. It is the same structural problem as a two-column layout, in a more concentrated form.

What to build instead

Dates on the right. Use a tab stop, or a design that places them. Not a two-cell row.
Skills. A single line of comma-separated entries, or a simple list. The skills guide covers how they are split and counted.
Contact details. One or two plain lines in the body of the page, near the top.
Anything that looks like a grid. Ask whether a list would carry the same information, and it usually will.

What the checker can and cannot detect

The ATS résumé checker deducts twenty-two points of parseability when it detects a table or multi-column pattern in the extracted text, and the finding names the fix. It works on what the extraction gives it, which means one honest limitation: where a table has already been flattened into a clean single stream, there is nothing left to detect, and where it has scrambled the order, the damage shows up as missing sections and low counts rather than as the word "table".

So read both parts of the report. The findings tell you what was recognised; the line reporting words, lines and recognised headings tells you whether your document survived at all. The guide to the checker covers the rest of the report in order.

The designs here do not use them

Every one of the 21 ATS-safe designs in the gallery is a single text flow: the dates, the skills and the header are placed by the layout rather than by a grid, and the mark is verified against the exported PDF. If you are rebuilding a résumé that came from a word processor template, moving it into the builder removes the tables as a side effect, because there is nowhere to put one.

Word processor templates are where most tables come from

Very few people set out to build a résumé from a grid. They start from a template whose columns, headers and alignment are built on one, and the structure is invisible in normal editing. If your document came from a template and you have never looked at its structure, assume a table until you have checked, and check by turning on the option that shows table boundaries.

The same applies to an infographic résumé built in a design tool. The output is often a page of shapes and text frames with no reliable order at all, which is the most complete version of this problem.

What to do with a document you cannot rebuild

Where an existing file is the only copy, import it rather than retyping it. The reading in the résumé builder works on the extracted text, sorts what it can into fields, and shows you what it read before anything is applied, which turns a damaged layout into a starting point in a few minutes. Then export a fresh file whose structure you know, and the problem is gone permanently rather than for one application. The guide to scans covers the harder case, where there is no text layer at all.

See what came out

Run the exported file and compare the words, lines and recognised headings with the page you think you sent.

Open the ATS checker Read the format guide

Questions

Are tables always bad on a résumé: They are a risk rather than a certainty. Some extractions flatten a table into the right order and some interleave it, and you cannot see which will happen.
What about invisible tables used for alignment: Same risk. The borders are a visual choice; the grid is what the file contains, and the grid is what has no reading order.
How should I align dates on the right then: With a tab stop or the design's own layout rather than with a table cell. Every design here places dates without a grid.
Do text boxes cause the same trouble: Yes, and often worse. A floating box is its own object and can land anywhere in the extracted stream, including mid-sentence.
Will the checker tell me I used a table: It deducts twenty-two points when it detects a table or multi-column pattern in the extracted text. Where a table has already been flattened, there is nothing left to detect, so read the counts as well as the findings.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.