Resumes aren't just a list of skills and work history (education isn't even on my resume anymore), it's also a chance to let a small amount of your personality show through so you stand out against the pile.
Of course, if you're submitting to a big corp, you'll be fighting against AI reading your resume first, so, write for that if that's how you roll. I usually only apply to smaller companies that apparently end up as bigger companies by the time I move on.
I like that so much that I dare not copycat it.
in the house == domesticated
house approxEqual box
"Keeps things running. Puts out fires."
Served me well on the resume, probably for quite similar reasons.
A regular HR can only do CTRL-F CTRL-V efficiently in their PDF viewer, when automated system would likely test for /\bnode(?:\.?js)?\b/i, because it's a result of a development cycle, which usually includes some field analysis. HRs would LOVE to select something like "where has($node) and years($redux) >= 2 order by years($php) desc". They are not idiots, they just have piles of data and nonsensical tools. Of course they optimize for nonsense.
A human could search for different variations too, but they are average in average and have no the expertise to install a regex-able viewer. It's stupid little things like this that prevent them from doing their job better, not some systemic issue of their own.
Disagree.
I wish it was easier to do. At my first job after university (not my first job altogether) we initially had great rapport between "DCOps" and HR. To be honest, our group was rather... irreverent, which made it even more interesting that we had such great rapport (we had all the stereotypes going for us, including female-only HR team and basement-dwelling male-only sysadmins).
But thanks to great cooperation, HR would do basic filtering on things they actually checked with us about, then forwarded us the CVs unmodified to give our own opinion before deciding whether to go with it or not.
Unfortunately some time later head of HR ended up let go due to some conflict with C-level I believe, and things slowly reverted to the mean :(
Fixing that would require not only a universal data format but also a universal taxonomy of terms to describe skills. That would need everyone to agree on how to describe what they do. Easy enough when you're describing programming languages, but effectively impossible for any softer skills. This is precisely why you need the human aspect.
The way to fix the issue you describe is to educate HR people, not to try to apply technology to a non-tech problem.