TL;DR
LaTeX resumes look great and usually parse fine when they are single-column text PDFs. Problems appear with tables, multi-column tabular layouts and custom fonts. Word (.docx) is the safest choice for Workday and Taleo employers; LaTeX is fine for most Greenhouse and Lever start-ups.
Side-by-side comparison
| Factor | LaTeX / Overleaf | Word (.docx) | |---|---|---| | Look and typography | Excellent | Good | | Editing speed | Slow for non-coders | Fast | | ATS parsing (single column) | Usually good | Very good | | ATS parsing (tables/columns) | Often scrambled | Often scrambled | | Recruiter edits | Hard — they can't edit a PDF | Easy | | Agencies that request Word | Not supported | Supported |
Why tables break in LaTeX resumes
Popular LaTeX templates use \tabular to align dates on the right. When exported to PDF, some parsers read those cells as separate blocks, splitting job titles from dates or companies.
How to test your resume
Copy all text from your PDF and paste it into a plain text editor. If the order is wrong, an ATS will likely read it wrong too. You can also run it through our free ATS scanner.
What we recommend for tech roles
Use a single-column layout either way. If you want the clean engineering look in an editable Word file, try the Tech Resume Template ($15) — built for software, data and IT roles.