Why isn't there a universal data format for résumés? • Hacker News Board

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

#201

Post by Diti » Mon, Jan 17, 2022, 1:49 AM UTC

moralestapia wrote: post #195

vanusa wrote: post #174

Earlier quoted context omitted.

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'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. Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.

Perfectionism and pedantism are good qualities some teams are after, it is unsurprising that some people would reject a candidate who did not bother “properly” writing the name of the technology they use.

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

#202

Post by kwertyoowiyop » Mon, Jan 17, 2022, 1:50 AM UTC

Also, why isn’t there a universal format for job postings?

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

#203

Post by monsieurbanana » Mon, Jan 17, 2022, 1:56 AM UTC

Diti wrote: post #201

moralestapia wrote: post #195

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. Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.

Perfectionism and pedantism are good qualities some teams are after, it is unsurprising that some people would reject a candidate who did not bother “properly” writing the name of the technology they use.

He was clearly being pedant, not perfectionist. I've never heard of a team looking for pedant people. I'm curious to hear your definition of the word.

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

#204

Post by irrational » Mon, Jan 17, 2022, 1:57 AM UTC

vanusa wrote: post #174

moralestapia wrote: post #91

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…

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.

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

#205

Post by throwawayboise » Mon, Jan 17, 2022, 1:57 AM UTC

moralestapia wrote: post #195

vanusa wrote: post #174

Earlier quoted context omitted.

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'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. Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.

Even back in the era when reading resumes and hiring was a manual human process, the standard advice was that resumes should be perfect. Nicely formatted, with no spelling or grammatical errors. You have ample time to think about the content, to proofread it yourself, and to have someone else proofread it. It's the first impression the potential employer has of you, no reason to not make an effort.

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

#206

Post by micromacrofoot » Mon, Jan 17, 2022, 1:58 AM UTC

polote wrote: post #77

There is one, it is just proprietary https://linkedin.com

people are coming from the angle of “why do I have to fill out a webform and not just upload a standard file for ingestion” but in terms of how much of computing is experienced today, that’s starting to seem like an antiquated notion… how many people are using phones or tablets to apply for jobs? they’re not doing much file managing directly… linkedin is already supplanting resumes

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

#207

Post by moralestapia » Mon, Jan 17, 2022, 2:02 AM UTC

Diti wrote: post #201

moralestapia wrote: post #195

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. Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.

Perfectionism and pedantism are good qualities some teams are after, it is unsurprising that some people would reject a candidate who did not bother “properly” writing the name of the technology they use.

nodejs came out on 2009, I've used it non-stop since then and probably built close to 100 things with it. I am on the author's list of both node and v8.

I write it as nodejs because that's how I got used to it on the mailing lists and several places that I frequent.

If a "team" decides not to hire me because of the latter, then ... thanks, I guess?

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

#208

Post by b112 » Mon, Jan 17, 2022, 2:05 AM UTC

throwawayboise wrote: post #205

moralestapia wrote: post #195

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. Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.

Even back in the era when reading resumes and hiring was a manual human process, the standard advice was that resumes should be perfect. Nicely formatted, with no spelling or grammatical errors. You have ample time to think about the content, to proofread it yourself, and to have someone else proofread it. It's the first impression the potential employer has of you, no reason to not make an effort.

Considering the node ecosystem, wouldn't those with mistakes on their resume be the perfect fit?

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

#209

Post by b112 » Mon, Jan 17, 2022, 2:14 AM UTC

pyrale wrote: post #107

ravenstine wrote: post #64

Earlier quoted context omitted.

I wonder if there's any advantage in using fonts and layout that are adversarial to automated resume processing, as in if something fails to scan then perhaps a human is more likely to actually look at it. But perhaps HR just throws those out.

Some people do add an emoji in their name on linkedIn to know whether they are being contacted by someone who read the page, or by a bot.

Awesome! I may adopt this. Thanks

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

#210

Post by weare138 » Mon, Jan 17, 2022, 2:16 AM UTC

vanusa wrote: post #197

Another factor people aren't mentioning -- even if such a format were to gain widespread adoption, along with the emergence of a side industry of Equifax-like companies that verify all the bullet points -- it would in effect amount to the backbone of a social credit system: https://en.wikipedia.org/wiki/Social_Credit_System And as such, it should be rigorously boycotted, no matter what benefit it may bring to the dro…

Wat? The article is just talking about automated software parsing different file formats. If you're worried about 'Equifax-like companies that verify all the bullet points' I'm sorry to inform you that's already happening. Not that I agree with this system but that's where we already are. People can't get jobs because the current zeitgeist in the industry is using algorithmic software to select candidates. The entire solution is just bad software built on a crap idea that has real world consequences. If we can't get something better at least having some standard format that we can feed this crap software it can actually parse is slightly less worse.