Live data from Hacker News

Why isn't there a universal data format for résumés?

toot.cat

361–370 of 472 posts

Re: Why isn't there a universal data format for résumés?

#361
post #174

Earlier quoted context omitted.

>Documents like these shouldn't be automatically processed, they should be reviewed by humans. That's very nice to think about but in the real world if people don't match some exact keywords they get thrown away. HR is looking for "node.js" but you wrote it like "nodejs"? Though luck pal, bye. HR wants a "computer scientist" but you have a degree in "computer science"? Same, automatically discarded. If anything, a st…

That's very nice to think about but in the real world if people don't match some exact keywords they get thrown away. This isn't the "real world" you're referring to here -- it's the fin-de-big-tech bubble world where everyone and their dog is not only sold, smack-down drunk on the idea that Algorithms and Data are the Solution to Your Problems. They aren't of course -- it's just a giant hornswoggle. This "world" nee…

I kinda agree with you -- half the job as a programmer is being really tedious and paying attention to written text on a screen. If you can't reasonably review your resume and use spell check, it is not a great look.

Re: Why isn't there a universal data format for résumés?

#362

> Why isn't there a universal data format for résumés? There can be. You can create a universal data format for résumés. You can make the universal data format a world standard in 7 steps: 1. Create a committee comprised of stakeholders. 2. Agree on a protocol for establishing consensus on requirements. 3. Consult all stakeholders about their requirements, and process these requirements through the committee in the f…

This is great! I would add one more important item to that list:

- Find a common problem of these different stakeholders that will actually get solved by your new standard.

Often, the standards talk is just a solution in search of a problem. It is easy to build a standard. It is not so easy to build a standard which really solves some stakeholder pain and gets adopted by multiple organizations.

Re: Why isn't there a universal data format for résumés?

#363

Earlier quoted context omitted.

Absolutely. We typically receive hundreds of resumes for every position. The easiest way to winnow them down is to throw out any with spelling or grammar errors. It is astonishing how high a percentage include these errors. There is absolutely no excuse to have spelling and grammar errors in your resume if you are serious about trying to find work.

Some people aren't native speakers. Do they really need to know how to spell perfectly to work for you?

Native speakers are the worst at pointing typos in my experience because they are so sure of themselves.

Literally every time I have submitted an (academic) paper at least one US reviewer had to point out I made several spelling mistakes when I actually used the British spelling (consistently) instead of the US spelling.

Sorry my man but it is called "English", I think I am allowed to spell things like they do in England.

Re: Why isn't there a universal data format for résumés?

#364

Earlier quoted context omitted.

I'm pretty sure my Resume says "crazy outside-the-box madman" on it somewhere near the top. It pretty much guarantees that I work somewhere with a sense of humor while rejected from places that take themselves too seriously. 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 again…

>"crazy outside-the-box madman" I like that so much that I dare not copycat it.

see also "never fully domesticated", to quote one HN profile description.

in the house == domesticated

house approxEqual box

Re: Why isn't there a universal data format for résumés?

#366
post #174

Earlier quoted context omitted.

>Documents like these shouldn't be automatically processed, they should be reviewed by humans. That's very nice to think about but in the real world if people don't match some exact keywords they get thrown away. HR is looking for "node.js" but you wrote it like "nodejs"? Though luck pal, bye. HR wants a "computer scientist" but you have a degree in "computer science"? Same, automatically discarded. If anything, a st…

That's very nice to think about but in the real world if people don't match some exact keywords they get thrown away. This isn't the "real world" you're referring to here -- it's the fin-de-big-tech bubble world where everyone and their dog is not only sold, smack-down drunk on the idea that Algorithms and Data are the Solution to Your Problems. They aren't of course -- it's just a giant hornswoggle. This "world" nee…

It is Node.js®

Here is your pink slip. Don't call us

Re: Why isn't there a universal data format for résumés?

#367
Slightly off topic, but I have seen a number of comments mentioning "CV parsing". I implement HR technology for a living, which obviously includes recruitment solutions. I have never seen a company implement automated CV parsing, as in rejecting CVs which don't contain certain keywords.

Does anyone have first hand experience of working for a company which does implement automated CV parsing?

Re: Why isn't there a universal data format for résumés?

#368

The EU has tried to put one in place, and it is used for all EU funding programmes and by a number of national and local administrations in Europe, so probably tens of millions used per year. Not sure I like the format but its good it stresses experience and narrative over just 'formal' data. And they have done it quite nicely that you can either download a template and work offline, or you can work in the browser an…

Yes - this is Europass CV. The XML schema is described at https://europa.eu/europass/en/eportfolio-interoperability (the web builder and I'm sure other tools attach the XML to the PDF you download so HR apps can easily make sense of it). It's a specialisation of HR-XML which was one of the first standards groups in this area (now part of https://www.hropenstandards.org).

Re: Why isn't there a universal data format for résumés?

#370
post #63

I used to work in ontologies, and what I learned is that people would rather get an 80% heuristic solution for dirty data rather than a 100% correct solution for data they have to clean. The big job sites have resume parsers that work well enough from a PDF or Word doc, and then they don't have to worry about you forgetting a close tag or a mandatory field. Sure, stuff gets lost, but they get 80% of a billion resumes…

that still doesn't really explain why big companies have not initiated a RFC for resume format. they only have to come up with an RFC and just ask everyone to follow. The cost of producing such an RFC is so small. guaranteed reduction in inefficiencies including operational costs. my gut feeling is that 20% improvement could have big butterfly effects.

They have - it's called HR-XML. It's mostly B2B but if you use EuroPass CV it's using this under the covers
Post reply on HN