Wish I had seen this before making my resume in latex. One question, though to add publications, is it possible to use bibtex, or do you have to manually convert each publication to YAML?
Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
11–20 of 42 posts
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#12Favorited for next time I make a resume - thanks for making this! Hopefully I’ll never have to touch LaTeX ever again.
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#13Wish I had seen this before making my resume in latex. One question, though to add publications, is it possible to use bibtex, or do you have to manually convert each publication to YAML?
Yes, unfortunately, you will need to convert them to YAML. I think an LLM can easily do that for you, though. This has been requested before, but we haven’t implemented it in order to keep our schema robust and simple. Maybe we should add it.
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#14I have been through a huge over supply of AI generated CVs using similar tools this year. I am sure this will help people so not bashing the tool per se, but bare in mind that you will be joining the robots.
I don't know what the solution really is, but as much as I hate it, a verified Linkedin Profile is a huge signal now. Otherwise a real personal site with care and history. I am guilty of being bad with the second so - no easy answers. Maybe even a wacky looking CV would make me notice a candidate more. Powerpoint 90s style.
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#15I get the motivation, but it honestly feels a bit weird to use tens of thousands of lines of python code to do something that you can just directly do in typst.
I mean, a CV is not really rocket science and there are quite a few great typst templates out there.
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#16This is clearly a real project that was built over several years with human effort (not vibe coded). Which makes it all the more depressing that the author decided to take a massive dump over the entire README.md with AI slop.
Sadly, it appears the project was heavily sloppified a mere 2 weeks ago: https://github.com/rendercv/rendercv/commit/5cc5fbdf9ec1a742...
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#17Yaml itself can be a resume.
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#18Looks nice! I do, however, see an issue with such tools, as they require people to maintain their CV. I don't want to hijack the thread so I won't link here unless asked to do so, but I've build something to keep developers' profiles up to date
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#19I have been through a huge over supply of AI generated CVs using similar tools this year. I am sure this will help people so not bashing the tool per se, but bare in mind that you will be joining the robots. I don't know what the solution really is, but as much as I hate it, a verified Linkedin Profile is a huge signal now. Otherwise a real personal site with care and history. I am guilty of being bad with the second…
AI generated (and quite often fake) CVs are a fucking joke.
I've spent many hours over the last 2 years going through the pile of them
Re: Show HN: RenderCV – Open-source CV/resume generator, YAML to PDF
#20A bit of a missed opportunity not to use the JSON Resume schema for this. https://jsonresume.org/schema
We deliberately chose not to use JSON Resume because we wanted greater flexibility. For example, in RenderCV, you can use any section title you want and place any of the 9 available entry types under any section. In contrast, JSON Resume has predefined section titles, and each section is restricted to a predefined entry type. For instance, you must use the experience entry schema under the experience section.
I hear you. This boils town to personal opinion. I would have preferred to use an existing standard than introducing yet another one. The custom sections aren't something I've ever seen or needed anyway.