Can you name one universal data format that is so in practice?
Why isn't there a universal data format for résumés?
191–200 of 472 posts
Re: Why isn't there a universal data format for résumés?
#192In my opinion, there shouldn't be. Documents like these shouldn't be automatically processed, they should be reviewed by humans. Reducing someone's life history to a list of educational institutions and employers feels robotic even for a software developer's mindset. I understand that there are real life problems because companies do use automated processing on applications, but that kind of behaviour shouldn't be en…
As a hiring manager you’d be inclined to disagree. If resumes could be standardized and easily searchable for information it would help find candidates much more accurately and quickly without having to read. Even better would be if there was a verification standard where you could get a blue checkmark on your resume meaning all the information is accurate and not made up bullshit, then you could limit searches only…
I see what you're driving at -- but that implementing that "verification standard" (i.e. standardized, continually updating 3rd-party background checks) would be a huge undertaking, and a larger than cottage-sized industry in itself.
Way, way more than a matter of parsing a bunch of standardized resume documents.
Re: Why isn't there a universal data format for résumés?
#193In my opinion, there shouldn't be. Documents like these shouldn't be automatically processed, they should be reviewed by humans. Reducing someone's life history to a list of educational institutions and employers feels robotic even for a software developer's mindset. I understand that there are real life problems because companies do use automated processing on applications, but that kind of behaviour shouldn't be en…
>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…
If HR is reviewing my CV then it’s prob not somewhere I want to work. :D
Re: Why isn't there a universal data format for résumés?
#194In my opinion, there shouldn't be. Documents like these shouldn't be automatically processed, they should be reviewed by humans. Reducing someone's life history to a list of educational institutions and employers feels robotic even for a software developer's mindset. I understand that there are real life problems because companies do use automated processing on applications, but that kind of behaviour shouldn't be en…
>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…
I review every single resume and applicant I hire. My experience tells me talent acquisition professionals don’t really know how to match and will often suggest poor matches and not bring forward odd fits with interesting backgrounds.
I get hundreds posting into some of the roles I’ve hired for and I’ve got to look at every single one in order to find a possible match. It generally takes me about 30 seconds to a minute to assess a resume. A kernel of interest stands out quickly or a smoke screen of buzz words tells me it’s the wrong candidate.
Algorithms aren’t a substitute for an active hiring manager being really interested in finding the right candidate to join their team.
Re: Why isn't there a universal data format for résumés?
#195Earlier 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'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.
Re: Why isn't there a universal data format for résumés?
#196Earlier 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…
If HR is reviewing my CV then it’s prob not somewhere I want to work. :D
That's a great point, though.
Re: Why isn't there a universal data format for résumés?
#197Another 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 drones in HR.
Re: Why isn't there a universal data format for résumés?
#198Because in certain fields, the design of the resume is just as important as the content of the resume.
Re: Why isn't there a universal data format for résumés?
#199Earlier 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'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.”
Re: Why isn't there a universal data format for résumés?
#200The question is based on a proufound misunderstanding. It's like a goalie saying people should standardize where they aim their penalty kicks.