Why all the criticism this is a great tool, it might not fit your needs, but it is a great tool none the less. He did a great job building it and its useful to some, and its open source and people can tweak it for there own use cases.
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).
Even back then there were plenty of Resume generators. What still haunts these tools is a too complex environment setup and unappealing template designs.
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 sound a bit like overkill, but I don't think that is a reason that the OP would want to ignore or exclude any that users would find useful. Personally, I keep about 3-4 (linkedin, .doc, .pdf, .htm).
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.
Ten might be overkill, but I really want to have an html version hosted online as well as a PDF version with the same content and LaTeX-quality typesetting (my current resume is written in LaTeX). There's some hacky tools out there for taking a resume in markdown and making html + pdf, but nothing really satisfactory, so I'm thinking this might be exactly what I've been looking for.
Problem is, your CV should be optimised for the format in which you are looking at it. A Word and PDF version should be no more than 2 sides of A4, with the page break at a logical place. HTML should be interactive, with widgets that show relevant content.
Web design is fundamentally different to print design, and your CV should show that you understand that. So you should be able to make a Word version save that to PDF, then re-write and redesign the content for the web page.
In an optimal sense, I agree with you, but I don't have the skill/time/desire to make a really awesome web version as you describe, and would be quite happy with one that roughly mirrors the printable version. There's always LinkedIn too, which gives some of that interactivity.
Further, this (really the underlying JSON resume schema) could be a great starting point for a fancier web-resume generator working from the same content.
That's an opinion that not everyone holds, and doesn't necessarily hold for all sorts of people/positions. If you do design-heavy types of work, then it makes a lot of sense to heavily optimize for the format. If not, then that's just window dressing on a format that is used to convey information.
I highly interactive web-based resume for a lawyer or accountant might seem silly in that community (and some of my lawyer/account friends agree).
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.
Awesome, thanks for linking to this! I copied this format from a friend 10+ years ago and have yet to find a better/cleaner replacement. Never knew that it is based on a well-known template.
That's nice. I've been using LaTeX's moderncv template for years and I was looking for a change, specially because in moderncv, the dates are on the left side and when you input a range (say, september 2010 - january 2011) it ends up all cramped.
BTW, do you have the base style for that uploaded somewhere?
One thing that I really wanted to do for hiring is to be able to put resumes on top of each other in a tool and slice and dice over time periods to see how a person's career has evolved be it in terms of companies they worked for, skills they picked up etc. Does anyone else feel the same need? Storing the resumes in a queryable format is a good first step towards my dream :)
It would really save me time in understanding who to talk to first. Would it impact the final decision? No. But it would certainly help me prioritize candidates. It is really time consuming to go through 120 resumes to see who you want to talk to first (especially when you also have a day job of delivering software).
Really cool! Folks interested in this might also be interested in a new project I just launched--a free minimalist résumé builder focused on developers and designers: https://makerslate.io
Exporting to various formats is high on my list of todos. I'll definitely be looking closely at how it's implemented here.
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.
You'd need an interface more robust than the console and json at that point, right? In order to select which aspects of your LI profile are appropriate for which level? But I agree it's probably a good next step.
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.
I'd be tempted to make an image of the PDF and insert it into a Word document so it fills the page, but that would probably have broken their workflow (Word's inline comments, perhaps) and dropped me straight into the reject pile.
From what I can tell, their general "workflow" is to shove the Word document into a parser that grabs your name, address, experience, education, etc. and puts it into a searchable format so that can filter on certain keywords. The reason they need to Word doc is because it's the only format their parser accepts...
I don't think I've seen a job that required Word since about 2009, and back then I wasn't using LaTex so I didn't have the problem but don't any of the LaTex to word tools or services I see around work?
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.
