Programming

22950 readers

145 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

CV/Resume generation? (lemmy.world)

submitted 1 day ago by _hovi_@lemmy.world to c/programming@programming.dev

45 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] _hovi_@lemmy.world 2 points 1 day ago (1 children)

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 a yaml file, and can comment/uncomment relevant parts where needed, etc., and I can have it re-rendered to PDF on each change.

that one’s resume should fit on a single sheet of US Letter or A4 paper

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.

[–] litchralee@sh.itjust.works 2 points 1 day ago (1 children)

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.

[–] _hovi_@lemmy.world 2 points 1 day ago

Thanks yeah. I do make sure to have links to the code and demo/distribution (if the project has one)