4 ms·
Points for originality, but it does seem a little complicated. I did something like this about six months ago, but in HTML, CSS, and zsh. As a next step, try te
by scardipdap 2y ago
Points for originality, but it does seem a little complicated. I did something like this about six months ago, but in HTML, CSS, and zsh. As a next step, try testing your output with a free ATS parser.
- neilv 2y agoSeconded, about trying to make sure it's ingestable by various ATS software. I had a resume in TeX, distributed as PDF, which I verified could be parsed as text by open source PDF readers, but later learned that ATS software had still been silently throwing away my resume. You can also try uploading your to the various job sites (e.g., LinkedIn, Indeed, Wellfound), if you don't already have a profile there, and see what they do with it. You can also test it when applying to employers that use one of the popular SaaSes (the kind that asks you for your LinkedIn, then makes you upload your resume PDF/.doc, then makes you use Web forms to fix what they parsed). (I currently do my resume in LibreOffice, and distribute as PDF, on the assumption that will be closer to the MS Word output that ATS sees the most of.)
- adzm 2y agoDo you have any links to free ATS parsers? This is an interesting angle I hadn't considered.
- andrewflnr 2y agoI have considered it, but didn't find any parsers that didn't creep me out.
- karpatic 2y agoAny clue if Latex or html works better?
- c0wb0yc0d3r 2y agoMy guts say that only pdf and doc formats matter. I would imagine that it’d be more likely a dev is testing outputs from word or printing to pdf from a browser. Of your options my thought is HTML to pdf via the browser is most tested.