What do you guys use to build your CVs? Do you automate it in any way or just use something like Google Docs? I’d be interested to know.
Personally I’ve been using rendercv for a while and I can’t imagine going back to doing it manually. However, I think I might need some more flexibility. Been struggling to get any interviews so I’ve been doing what I can to experiment with my CV. If any of you have a good typst
template they’ve actually used to land a role I would love to steal borrow it.
Thanks for the in-depth answer. I could definitely be better about it tbh but I agree highlighting points relevant to each role. Makes a lot of sense.
However, I think automating it actually makes this easier. With
rendercv
, I have everything in ayaml
file, and can comment/uncomment relevant parts where needed, etc., and I can have it re-rendered to PDF on each change.Yeah I might have to go back to this. I recently expanded to 2 pages to be able to show more personal projects / open source work, but it hasn’t seemed to entice any employers much anyway.
Having previously been on the reviewing side of job applications, if you have GitHub/Codeberg repos with your work, please, please, please include those links somewhere on the resume, ideally spelled out and also clickable in the PDF. It’s a neat trick to showcase more work than what fits on a page.
Although the non-technical recruiters might gloss over links, the technical reviewers very much look at your code examples. Why? Because seeing your coding style and hygiene, Git workflow and commit messages, documentation, and overall approach to iterative improvement of a codebase is far more revealing than anything that AI-nonsense coding tests can show.
So while this won’t necessarily get your resume past the first gate, always be thinking about the different audiences whom your resume might be passed around to, within the prospective organization you’re applying to.
Thanks yeah. I do make sure to have links to the code and demo/distribution (if the project has one)