Re:The Overengineered Resume with Zola, JSON Resume, Weasypr...
by DEADMINCEDOS on Thursday July 11, 2024 @11:56AM
(#40938015)
I've made sure all the most commonly used ATS systems can read the produced PDF without issue.
[ Parent
| on HN ]
Re:The Overengineered Resume with Zola, JSON Resume, Weasypr...
by webel0 on Thursday July 11, 2024 @02:37PM
(#40939363)
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.
Re:The Overengineered Resume with Zola, JSON Resume, Weasypr...
by tarxvf on Thursday July 11, 2024 @06:40PM
(#40941253)
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.
Re:The Overengineered Resume with Zola, JSON Resume, Weasypr...
by ok_computer on Thursday July 11, 2024 @09:42PM
(#40942120)
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.
Re:The Overengineered Resume with Zola, JSON Resume, Weasypr...
by wonger_ on Thursday July 11, 2024 @10:42PM
(#40942373)
I think this open-source parser details a typical ATS algorithm: https://www.open-resume.com/resume-parser