211–220 of 472 posts
On the employer front: I always hated looking at 1000x pieces of white paper that all look the same. It was mind numbing.
On the employee front: I always ensured I used very graphical resumes that stood out. They always got the attention of the hiring managers, and it was a great filter of either "You're boring so you threw my resume away" or "You're awesome and the kind of company I want to work for by having some fun with it".
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.)
Json Resume is still going strong. I am one of the founders, I try to do a couple major maintenance periods per year. Currently I am working on updating all the community projects built, still got quite a few to add but currently there is -> https://jsonresume.org/projects/ I think over 3k+ people use the new Gist hosting. (In our old hosting we had around 10k resumes. Not including those who by pass the free communi…
In 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…
There can be. You can create a universal data format for résumés.
You can make the universal data format a world standard in 7 steps:
1. Create a committee comprised of stakeholders.
2. Agree on a protocol for establishing consensus on requirements.
3. Consult all stakeholders about their requirements, and process these requirements through the committee in the form of a requirements document.
4. Develop a résumé format that meets the requirements through the committee.
5. Ratify and publish the résumé format standard through the committee.
6. Publicise the résumé standard.
7. Evangelise the résumé standard until it achieves widespread adoption.
That's almost all there is to it. You just need money, time, expertise, charisma, luck, and for the stakeholders to want you to succeed.
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…
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.
In 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…
In 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…
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…
Specifically?
Yes there are obviously companies that strip mine every nugget of "data" they can possibly find about an individual, and then pass this along to whoever may be willing to buy, garbage-in, garbage-out style.
But actually verifying that this information has anything to do with the real world (the way background check companies do) is a completely different, and very expensive endeavour.
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. Yikes. “It’s not JavaScript it’s Ecmascript! What a RED FLAG.”
Not comparable.