Live data from Hacker News

The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

ktema.org

61–70 of 122 posts

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#61

Dropping a link/endorsement for quarto : https://quarto.org/ It's a static site/document generator that supports bibliographies, jupyter notebooks, and good old fashioned markdown. It works well for complex academic resumes and CV's, as well as blogs and library documentation. I use a template for my website : https://jjd.io/ github repo : https://github.com/jdonaldson/jjd.io Also, if anyone has any positive/negative…

[deleted]

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#64

The only thing you should spend time on with your CV is the content. The ROI on tweaking the look and feel is very low. Aesthetics are not what people care about, unless your resume is so hideous that it gets thrown out.

My CV is a LibreOffice Writer document with no styling added. A “boring” short black and white non-interactive document that I export to PDF. It has my name, contact info, a list of recent work history, and mention of some of the technologies that I work with. Last time I was applying for jobs, two years ago, I got an interview and eventually a job offer from the company I most wanted to work for among the ones I’d b…

Same. LibreOffice exported to PDF.

Also I cram everything into one page while keeping things readable. Being concise is an important skill. Personally I find it ridiculous people with a few years of experience and 3+ pages. I have 12 years of industry experience and don't feel the need for that second page yet.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#65
The overengineering here produced a poor result. I have found a lot of success using the pandoc_resume project, which is literally just a content item written in Markdown, formatted into different outputs using a LaTeX template via `pandoc`. With this, I output a PDF that looks great, and output HTML which I put in as a non-touched file in my static site generator, and it works very well.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#66

I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…

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.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#67

Afaik modern resume parsers prefer .docx to .pdf. Some won't even accept a PDF.

Yea, looks like a big miss that he is not producing a docx file

but then, maybe he dont want employers who only accept docx resume files

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#68

I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…

Nix is completely orthogonal to whatever tech you use to build the resume - it's nice as a build tool + to provide dev environments for however you're going to realize your resume.

There is no reason to mention it, though. It's like mentioned Ubuntu as being necessary for having made a resume.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#69
post #50

I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…

I’ve actually made the switch over to Typst[0] for my app [1]. I’ve previously used a quick jinja .tex template that then just pasted things in, but LaTeX can really throw some strange errors and overall handling the files was a hassle. Typst was much easier to setup and the function-based operation meant that sending variables in was a breeze with better error handling there too. Also, I just grok the syntax a lot b…

Typist looks interesting, although I've had no issues with LaTeX so no reason to change to something more niche.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#70
post #66

I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…

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…

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