but...if I already have my CV in LaTeX why would I need it in this?
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.
I was semi-hoping, that "résumé validation" would validate it against things like expected buzzword frequency, HR stopwords and so on. The important things, you know.
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).
I would love for there to be a formalized CV standard to avoid having to reenter the info on your resume into a job application.
There's more than one. If you can solve parsing CVs/resumes in to standardised formats reliably, you'll get bought by an ATS for a trazillion dollars.
Even if one is able to build a rock solid format for CVs/resumes that is queryable, including i18n support, there is still the issue of adoption which is the hard part.
You'll need early adoption by large employers such as big tech companies to governments for it to have potential to reach critical mass and make you become an acquisition target by Applicant Tracking System vendors.
It seems to do a great job for what it claims to do, but I don't really understand the need for such a tool. How often do you update your CV that you need an automated tool to do it? And why would you need it in 10 different formats?
If your job is the type where you're on the same team/project for years on end doing basically more of the same thing from month to month, then I can understand why you wouldn't necessarily see the value in this kind of tool. I update mine once every 2-4 months or so, whenever I complete a project, earn a certification, take a course or work (professionally) with a new technology. Having 10 different formats does sou…
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.
This is the OP sample: http://please.hackmyresume.com/jane/resume It's certainly a step up from a docx but just not that great of a template based on the criteria I named. It seems to me the template itself is the most important differentiating characteristic of a product like the OP. I understand it accepts custom templates, but that one above is the only sample I found. Here's my own old-school resume with the DeCo…
If that's your real resume, I'd suggest changing the address before posting it on the Internet, because creeps.
In unrelated uncreepy news, we are practically neighbors! One block over on Steiner.
but...if I already have my CV in LaTeX why would I need it in this?
My resume is in LaTeX and I love it and its easy to edit and it looks beautiful... but some jobs (and I'm not kidding here) will only accept resumes in an MS Word .doc format. I can't tell you how much butchering I had to to do get my resume in Word to look close to how nice it looks as a PDF.
latex2html -> html2rtf
I've used that for years. No problems, though the odd jobsite's commented on formatting, giving me an opportunity to explain the generator ;-)
There's more than one. If you can solve parsing CVs/resumes in to standardised formats reliably, you'll get bought by an ATS for a trazillion dollars.
Even if one is able to build a rock solid format for CVs/resumes that is queryable, including i18n support, there is still the issue of adoption which is the hard part. You'll need early adoption by large employers such as big tech companies to governments for it to have potential to reach critical mass and make you become an acquisition target by Applicant Tracking System vendors.
The formats exist already, and the ATSs use them: cf HRXML.
The problem - poorly solved by Burning Glass, Daxtra, TextKernel, Sovren et al is converting documents applicants pass in to those formats.