There is a difference between a process that looks polished and one that produces better hiring decisions. This guide focuses on the practical choices that hold up when the work is busy, the information is incomplete and somebody has to make a call.
Why the layout is risky
A PDF records where words sit on the page, not the order you intended someone to read them. A parser reconstructs order from positions. If it sees a skills sidebar beside experience, a naive reader alternates lines across the page: “Python Senior Engineer, SQL Acme…” The resulting text may be grammatical enough to avoid an error while losing the actual job record.
When two columns can work
Use a generous, consistent gutter from top to bottom. Keep every element inside one column. Avoid floating badges, text boxes and full-width elements that break the pattern halfway down the page. Keep your name and contact details in normal body text at the top, not in a repeating page header.
What makes them fail
Narrow gaps look like ordinary spacing. A sidebar that changes width destroys the boundary. Tables used as invisible layout grids can flatten row by row. Icons can replace labels a parser needs. Each choice asks the extractor to infer more than the document states.
A practical test
Export the PDF, select and copy all text, then paste it into a plain-text editor. Read it linearly. Are your title, employer and dates still adjacent? Do the sections appear in order? Then upload the actual PDF to a parser and check the structured record, especially blank employer, title, date and contact fields.
The honest recommendation
If applications are a major part of your search, a simple single-column layout is the lowest-risk choice. Keep two columns only if you value the design and can verify its extracted text. There is no universal ATS verdict; there is only the evidence produced by your file.
For the mechanics behind this advice, read what an ATS actually sees.
The short version
- Why the layout is risky. Make the choice explicit, then test it against the work rather than a hunch.
- When two columns can work. Make the choice explicit, then test it against the work rather than a hunch.
- What makes them fail. Make the choice explicit, then test it against the work rather than a hunch.
- A practical test. Make the choice explicit, then test it against the work rather than a hunch.