[webel0]

I would be careful with LaTeX. I use to have a LaTeX resume generated with LuaTeX. At an old company, I saw my LaTeX resume in the ATS long after I was hired. Apparently, something happened and the PDF displayed as blurred-but-not-unreadable in the ATS. Maybe the ATS did some post-processing or used a limited PDF display engine? Lucky for me, the resume for that job was just a formality. These days, I just use Google Docs and export to PDF.

[DEADMINCEDOS]

I've made sure all the most commonly used ATS systems can read the produced PDF without issue.

[webel0]

I wouldn't worry about automated ATS. Their use is way overstated on LinkedIn, by "resume experts," etc.

I'm talking about whether a human can read the document comfortably.

[tarxvf]

Do you have any tips, code, or even just a list of the common ATS systems? I need to do this with my latex cv but I'm not even sure where to start.

[wonger_]

I think this open-source parser details a typical ATS algorithm: https://www.open-resume.com/resume-parser

[ok_computer]

I don’t know of the example systems but I’ve applied to a handful of companies recently, all running the same-ish workday resume ingestion. You can actually tell which are running a more recent version because the parsing is more accurate.

There is also a common no-account single page application software, I checked at a company I’d applied to and it was called Lever(?)

Normally, I thought for ATS parsing if you upload in an application and a few of the prior experience text boxes are accurate, then you’re good. I’ve always had to fix my experiences though, even with using a word doc.