Live data from Hacker News

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

toot.cat

411–420 of 472 posts

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

#411
UK here. Recruited lots of people for my company.

The technical details are irrelevant.

Recruitment agency sends you CV. That CV has all names, address, phone numbers and email addresses removed. This is to stop the recruiter from bypassing the expensive agency and contacting the applicant directly to save agency fees

Next, no age or DOB is displayed. That's against the equality act here.

Next, the recruitment agency pastes their logos at the top of your CV for advertising purposes

End result is that your CV looks nothing like it did when you sent it. The formatting is broken, it prints over 6+ pages. That's why they don't take PDFs, as they can't edit it.

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

#412
Everything cab be standardized so resumes can be as well. LinkedIn serves as a central hub for resumes in the "West" but how long and hard you can push it? In EU there is something like Europass which serves like a central hub for EU citizens' resumes and that can be seen as standardization format for resumes at least in the EU.

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

#413

Earlier quoted context omitted.

You're right, but I wonder how many resumes a job seeker submitted 30 years ago compared with today.

Probably 8 to 15, versus 80 to 100 now.

I'm not sure that's true at all. Coming out of school pre-Web when real information was much harder to come by (even job postings), I sprayed and prayed a lot of resumes to HR departments. (And my first engineering job came through one of those.)

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

#414
post #377

Earlier quoted context omitted.

I think I actually scored some jobs and interviews while I still kept "wizard" at the top of my CV...

My LinkedIn recruiter spam dropped substantially when I added "literally a wizard" to the skills section (and removed everything remotely tech-telated). https://www.linkedin.com/mwlite/in/mikkelpaulson

win / win :D

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

#415
post #328

Earlier quoted context omitted.

I came across this before. wish it's an accepted format on job portals. A challenge I see is -- resumes change wildly by industry. a tech resume is totallly different from an actor's resume.

Do you think this is so different that no formal spec can ever carry the common denominator?

https://www.cityheadshots.com/blog/acting-resume check this out

but I think this complexity can be handled.

I totally support json resumes.

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

#416

Earlier quoted context omitted.

Most humans who deal with technical hiring think that "javascript" and "java" are probably the same thing

Can confirm - I spent a year doing C++ because the recruiter thought it was the same thing as C#.

Java ?? Java-Script ??? Which is which?

http://web.archive.org/web/20171002221201/http://www.jerkcit...

Originally published in October 2002 (almost 20 years ago from when this comment was made, for you future readers and time travellers).

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

#417

Why should there be? Resumes have to be read by humans to judge if they match what is needed. Checking boxes and matching buzzwords only gets you so far.

Makes it easier to spam them out when it's job-hunting time. On the HR side, they already filter on asinine keywords in the ATS. Why not join their game?

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

#418

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 current job, and, although we've had to extend the schema, it's a great base to start with. It's got all the structured fields one would need to build a resume. It would be trivial for a company to start accepting it, at least as a way to pre-fill all the "education and history" fields that we have to fill out anyway.

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

#419
post #377

Earlier quoted context omitted.

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

I think I actually scored some jobs and interviews while I still kept "wizard" at the top of my CV...

"Wizard at getting resume's to pass automatic resume scanners"

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

#420

Everything cab be standardized so resumes can be as well. LinkedIn serves as a central hub for resumes in the "West" but how long and hard you can push it? In EU there is something like Europass which serves like a central hub for EU citizens' resumes and that can be seen as standardization format for resumes at least in the EU.

can*
Post reply on HN