hacksalot

You're right, thanks. Will update.

Just wanted to second this. It really depends on your velocity -- 6 month consulting gigs or 5+ year stints with a single company. After five or so years of short-term consulting for example you're looking at 20+ entries for work history alone, not counting mentionable side projects, service, other items. And you're a tech candidate so it's got to be keyword-optimized. Recruiter X wants it in MS Word, employer Y wants it in their proprietary ATS, employer Z you have direct access to the devs and can use the LaTeX "secret handshake". Then the anonymized HTML version for your blog, etc. So you get this explosion of formats and, if you edit each format manually, a quick resume update can take all day. Let alone a redesign.

Hi! HMR author here. This is the exact use case for HackMyResume (and FluentCV Desktop), you hit the nail on the head. But we're just in v1.x and before doing stuff like keyword density analysis, StackOverflow tag awareness, GitHub integrations, other fun stuff, the basic generative workflow needed to be solid and we're also trying to stay compatible with JSON Resume (http://jsonresume.org/) 0.0.0 ahead of the 1.0.0 drop -- the current schema doesn't support (formally) the level of detail you'd want for that kind of analysis, which is one of the reasons why FRESH/FRESCA exists (https://github.com/fluentdesk/FRESCA). Stay tuned though, there's a lot of tooling around this already esp. in FluentCV Desktop (= charts and graphs).

Hi, HMR author here -- HackMyResume treats LaTeX as a destination format, not a source format! So you would generate LaTeX through Handlebars/Underscore or whatever other template engine, then use your normal LaTeX workflow. Currently for example, the "awesome" theme generates a LaTeX CV based on Awesome-CV (https://github.com/posquit0/Awesome-CV). You have to run `xelatex` or similar to finish the build, which should probably be documented better.