3 ms·
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
by eternal_july 11y ago
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.
- benmarks 11y agoHeh, well, it is on GitHub, and there is a history of merged PRs: https://github.com/hacksalot/HackMyResume/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged+ https://github.com/hacksalot/HackMyResume/pulls?utf8=%E2%9C%...
- hacksalot 11y agoHi! 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/ 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 https://github.com/fluentdesk/FRESCA). Stay tuned though, there's a lot of tooling around this already esp. in FluentCV Desktop (= charts and graphs).