Live data from Hacker News

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

toot.cat

461–470 of 472 posts

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

#461
I was a contributor to the XML Resumé Project 20(!) years ago (http://xmlresume.sourceforge.net/), which could have been such a universal format. The goal was more about making it easy to render your resume in multiple formats, rather than data interchange, though.

I think that https://jsonresume.org/ is the modern equivalent (with much less XML, thankfully :).

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

#462
post #311

Earlier quoted context omitted.

Why JSON? Why not YAML or something more easily editable by a human?

Could of went either way really, YAML is a superset of JSON, so in theory, you can switch between them at any time. I think we wanted JSON at the time because it just relied on less extra packages when working inside of the JS ecosystem. So yeah, if anyone wants to make a resume.yaml, we only need to add an extra step to convert it to json for them to use any of the tooling.

Fair. I guess the reason I asked is because YAML is a little easier to play with for humans, especially since some sections need things like new lines among other things. Doing a YAML text block is easier to read and write than JSON's quoted string with new lines replaced with `\n`.

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

#463
post #436
post #391

Earlier quoted context omitted.

Shouldn't a universal Resume format also include digitally signed proof of your claims of degrees and certifications?

I guess it would have to. And that's precisely where the true horror lies in such an idea.

That you can't lie to potential employers?

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

#464

Earlier quoted context omitted.

I’d say they are. Who cares if I write “Nodejs” or “Node.js”? The reader knows exactly what I meant, and that’s what matters. Anything else is just needless pedantry.

It's not about communication, here. You want to be absolutely perfect in your CV, to prove that you've spent time and effort making it perfect. It serves no other purpose but to show your determination. If communication was the point, a long rant in which you write "yeah I worked with node.js, it was cool lol" would be OK as well, after all it gets the point across doesn't it?

I'm an OCD-ish perfectionist (especially in writing) if the world has ever seen one, to the point where I didn't stark working on my bachelor's or my master's thesis before I had exactly the markdown + latex setup + custom typography that I wanted. So I would definitely internally cringe if I'd see typos like this.

But to reject a candidate just because they're not the same kind of pedant that I am would be quite unreasonable IMHO. As long as the whole thing isn't littered with typos or formatting issues, that's just something I wouldn't pay too much attention to. Not everyone needs to be the person to dot every i and cross every t.

Also, I really want to see the HR department that can confidently reject or even mark down a candidate when most of the writing I've seen from most people in any company I've ever been (including from HR departments, PMs or executives) has been "meh" at best, and full of errors or at least awkward language more often than not. For better or worse, writing skills are not necessarily something we tend to select for in the industry.

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

#468

There are three different common standards: HR Open Standards Candidate, schema.org and JSON Resume. HROS (which does XML and JSON) is used as a data exchange format between enterprise ATS and HRIS it's very comprehensive and is very detailed (perhaps too detailed). Schema.org seems mostly like Google and friends just making something up (without even trying to work with other existing standards) and trying to get ev…

Schema.org doesn't have anything for the resume side of things. They have a model for a job listing, so job listings can appear in search results with special formatting, but nothing for resumes. HR Open Standards is only available with membership. Doesn't appear very "open", but I'd assume that doesn't matter much to the industry. JSON Resume seems like the best take so far. I've used it for my resume and at my curr…

Schema.org treats resume data as an extension of person. There's hasOccupation and role and alumniOf and organizationRole. It's not a "resume" it's a profile (old joke for job board people).

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

#469

There are three different common standards: HR Open Standards Candidate, schema.org and JSON Resume. HROS (which does XML and JSON) is used as a data exchange format between enterprise ATS and HRIS it's very comprehensive and is very detailed (perhaps too detailed). Schema.org seems mostly like Google and friends just making something up (without even trying to work with other existing standards) and trying to get ev…

Schema.org doesn't have anything for the resume side of things. They have a model for a job listing, so job listings can appear in search results with special formatting, but nothing for resumes. HR Open Standards is only available with membership. Doesn't appear very "open", but I'd assume that doesn't matter much to the industry. JSON Resume seems like the best take so far. I've used it for my resume and at my curr…

>HR Open Standards is only available with membership. Doesn't appear very "open", but I'd assume that doesn't matter much to the industry.

Membership is free and you can access the standards (from their website hropenstandards.org):

"The versions of HR Open Standards linked below are available for free public download. You need to be logged in to download the standards. If you're not already an HR Open Standards member, you can register for a free Community membership account."

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

#470

Earlier quoted context omitted.

> It's "Node.js" with a dot. If you spell it "nodejs", that's a serious red flag and you shouldn't be surprised if it gets you automatically discarded -- even by a human reviewer. Yikes. “It’s not JavaScript it’s Ecmascript! What a RED FLAG.”

The difference is that JavaScript is the name of an actual language. Where nodejs isn't the actual name of the project. The Node.js project advertises itself as a "JavaScript runtime." Both JavaScript and EMCAScript are acceptable.

I would argue that JavaScript is somewhat of an unofficial name since it is an Oracle trademark.

https://www.reddit.com/r/javascript/comments/8d0bg2/oracle_o...

Post reply on HN