https://jsonresume.org/ because it's fun, and I change my LinkedIn profile at the same time.

Literally just finished mine today using vanilla HTML / CSS.

It’s already designed as a document format and gives me full control, exports seemlessly to PDF when needed, lets me do nice little progressive enhancements moving from paper to the screen.

Overall, I’m really happy with the process. Would recommend if that’s in your skillset.

If there's one thing LinkedIn is good for, it's this (and this might be the only thing LinkedIn is good for). Hiring tools also integrate with LinkedIn so having a presence there is a good idea.

I've always used LaTeX in a Git repository. That's not uncommon in research or academia.

HTML + CSS + Github. Save the webpage as PDF in repo after any changes

I use kickresume.com and pay for it during active job hunts, canceling it once I find a job. I've done that every few years and it's worked well enough. Way less hassle than rolling my own system.

Google Drive and iCloud Drive. I had all of my job search communications in Yahoo Mail folders based on the year I was looking since 2008 (2008,2012,2014,2016,2018,2020,2023,2024). I have been working a lot longer but I stayed at my second job for 9 years.

I also have a “current” resume that gets reviewed every quarter and a folder with the descriptions of major projects in STAR format.

https://resumake.io/ and keeping the JSON in a Git repo for me. Other than that, just LinkedIn.

Markdown file checked into git: https://raw.githubusercontent.com/Leftium/leftium.com/refs/h...

- Cleverly styled to render like this: https://leftium.com/resume

- The git repo will eventually also host a portfolio of my work.

---

Before, I just kept my resume in a MS Word document.

Just a Word document. Word is pretty good at opening old documents, and I expect that to be true in the future too.

Rewrote mine a couple of years back to be a Web page that's machine-readable using the Microformats2 standard (https://microformats.io)

It's available at https://hire.jvt.me

Like many things with me (https://www.jvt.me/salary/) I wanted my CV to be public, and something I could keep continually updated (like my blog https://www.jvt.me/posts/)

It's been a hugely positive thing for me personally, as I can regularly go in and add new things I've shipped or am proud of

When you go to print it, there's a reduced view (using media queries for print stylesheets) so I can be verbose for humans reading on the Web, but provide a limited version for submissions

Implementation wise, it's plain HTML + CSS, no templating or processing, just hand written HTML

Word. I save every update with a date and a 'domain' (in case I customize it). E.g. "2025-06-06 Name Surname CV (PM).docx", "2025-06-06 Name Surname CV (ITSec).docx". When it is time to send it out, I "Save As PDF" with name "Name Surname CV.pdf" and send it out.

This way I have all past iterations (I try to keep it at 2 pages, so every now and then I need to cut out stuff, but I want to keep those old bullet-points in case I need to bring them up to match some job reqs)