Hacker News Reader

Comment by avip | Hacker News Reader

I wrote my last cv in markdown and named it my_name.cv

Disappointedly, lots of "resume uploaders" refused to accept my file, even as .txt.

Had to retreat back to pdf. Hard times we live in.

I do something like that, but use pandoc to get whatever format they ask for. It's not always nice looking, but it's seldom me who is initiating the contact (ie they already have an interest in me, and they need a resume "for the process").

I wrote mine in markdown and convert it to pdf (well, first html then pdf). It's worked well

   markdown resume.md > resume.tmp.html
   cat template/header.html resume.tmp.html template/footer.html > resume.html
   cp resume.html resume.tmp.html
   sed -i -e 's/"normal"/"pdf"/g' resume.tmp.html
   xvfb-run -a -s "-screen 0 640x480x16" wkhtmltopdf resume.tmp.html resume.pdf
   rm resume.tmp.html*

Similar, I wrote mine[0] with Typst (alternative to LaTeX) and YAML. It's source is still plain text but I get a nice PDF with the beautiful typesetting reminiscent of LaTeX and an easier scripting language.

edit: The generated PDF from the template mostly works with OP's resume-parser[1]. There's just fields lacking like Certifications, Awards, and Skills which are parsed under the Projects Category.

[0]: https://github.com/jskherman/cv.typ

[1]: https://www.open-resume.com/resume-parser

Reply on news.ycombinator.com