Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

toot.cat

Post reply on HN
Print view View original

31–40 of 472 posts

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

#31

Post by spondyl »

CalRobert wrote: post #22

There is! https://jsonresume.org/ But nobody really uses it for data interchange. I use it to render my resume in new layouts now and then. Although, it does let style dictate content sometimes (some templates force you to have dates down to the day for job start and end dates, etc.)

I used a JSON resume once and I like the idea. It didn't help when I had to apply for an unemployment benefit (while still trying to enter the industry) and they asked for my resume as a word document.

As you can imagine, I felt like a clown trying to explain that I didn't have a word document because my resume was generated from a JSON file.

I did, however, have a PDF on a USB drive I always kept on me but they refused to accept USBs out of fear that I was trying to give them a virus. Eventually the lady processing my application gave up and printed the PDF off that was hosted on my website but also scolded me for not having a word doc.

The whole ordeal was pointless anyway since they said they can give me 70% of my rent.

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

#32

Post by quickthrower2 »

bee_rider wrote: post #18
travisjungroth wrote: post #14

I would have found it much more interesting and useful if the author had tried to sincerely answer or even ask the question of the title. Instead it’s just a complaint.

I guess the answer must be: Companies have no incentive to make it easy to apply to their job without manual intervention. Which makes sense -- if it were easy enough to apply to companies automatically, I guess some people would just write a script to apply to every company in their field, right?

The underlying problem is you need a JSON format about the company. But the things candidates care for generally are easy to lie about (good culture, career progression, even remote working options), so scatter guns are required. As they say recruitment is broken - but its not easily fixable because it’s broken because of game theory and human behaviour.

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

#33

Post by netcan »

Hiring companies might prefer to just have this as a "hoop."

There are, inevitably, some people who apply to a lot of jobs. Jobs they aren't qualified for. Low intent applications, where the applicant isn't really that interested. Etc.

Even if these are a minority, they apply to a lot of jobs. In any case, standardizing job applications (OP seems to be talking about application forms that are mostly resume-ish fields) just means more of these. More volume, more noise, probably not many more successful hires.

There's kind of the same dynamic on the other side. Most workers don't love the idea of submitting an indexable resume for employers to leaf through.

Sometimes a modicum of friction is helpful.

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

#34

Post by codingdave »

Waterluvian wrote: post #19
dClauzel wrote: post #3

There is, thanks to the semantic web (the real web 3 :) ). See for example the FoaF ontology https://en.wikipedia.org/wiki/FOAF_(ontology)

Is the “semantic web” used in sensible, productive ways these days or does it remain an academic daydream? I’m highly skeptical of the whole concept and feel like I should have organically come across it by now.

Yeah, it is - not to the level people envisioned years ago where people made up their own tags and found a blend of XML and HTML, but it absolutely is in place for more meaningful HTML. We have tags that tell you the purpose of content - header, nav, section, article, footer, etc. Those tags are read by screen readers and other accessibility tools, and do bring semantic value to those readers.

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

#35

Post by ghaff »

bee_rider wrote: post #18
travisjungroth wrote: post #14

I would have found it much more interesting and useful if the author had tried to sincerely answer or even ask the question of the title. Instead it’s just a complaint.

I guess the answer must be: Companies have no incentive to make it easy to apply to their job without manual intervention. Which makes sense -- if it were easy enough to apply to companies automatically, I guess some people would just write a script to apply to every company in their field, right?

This is something of an issue with conference proposals as well. In fact, I've seen some conferences recently that put a strict limit on number of submittals. As a sometimes conference reviewer, I hate people throwing a bunch of overlapping and often generic stuff at the wall.

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

#37

Post by ghaff »

MattGaiser wrote: post #12

I have had a lot of success with "September 2019 - September 2020." Seems to work fine in nearly every case.

Note that there is some number of people who feel pretty strongly about obfuscating their age. I'm not sure what to feel about it personally but it's understandable.

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

#38

Post by yjftsjthsd-h »

heikkilevanto wrote: post #9

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.

Because many job applications make me check boxes already; I'd rather automate filling the same details into forms over and over again.

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

#40

Post by FpUser »

I very much like to write my resume the way I think represents me the best. The last think I need is to tailor it so some programmer who struggles with parsing.

When hire I also like to receive custom resume that helps me to understand better why hire. Again I am totally uninterested tailoring my offering to formalized set of checkboxes concocted by some "industry expert".

Post reply on HN