[deleted]
Why isn't there a universal data format for résumés?
421–430 of 472 posts
Re: Why isn't there a universal data format for résumés?
#422[dead]
Re: Why isn't there a universal data format for résumés?
#423I definitely think there should be, and my project (Nectr, https://nectr.network) is an attempt at a standard format. Along with the common things (job history, education, et.al.), we also try to pin your abilities (skills, platforms, etc) to entries in our knowledge graph of IT skills and platforms; and we encode availability in a standard way. IMO, these two aspects are crucial to finding the right talent, when they are available.
Re: Why isn't there a universal data format for résumés?
#424Earlier quoted context omitted.
You shouldn't be hiring that many. The company might, but the managers and people doing the interviews should be looking at maybe 20 positions per year. They can read résumés themselves and give it some thought.
Who sorts which 20 out of 20,000 resumes go to which managers? Not the managers. Who is “the company”? That’s who is keyword searching/matching/filtering.
The hiring manager. We have got tired of hr rejecting great résumés because they don't understand keywords. They have no clue that qt and qt5 are the same thing, and if we put both keywords on they reject someone with only one. Nor do they get that someone great with c++ is almost automatically great at qt. I'd be happy to teach c++ to someone with rust or Haskell experience if they are willing to learn. (And if it is rust we are open to new work in rust, though we have a lot of legacy c++ you will maintain)
We consider ourselves lucky to get 50 résumés, and if even one isn't obviously disqualified that is a miracle
Re: Why isn't there a universal data format for résumés?
#425Earlier quoted context omitted.
Some people aren't native speakers. Do they really need to know how to spell perfectly to work for you?
Native speakers are the worst at pointing typos in my experience because they are so sure of themselves. Literally every time I have submitted an (academic) paper at least one US reviewer had to point out I made several spelling mistakes when I actually used the British spelling (consistently) instead of the US spelling. Sorry my man but it is called "English", I think I am allowed to spell things like they do in Eng…
> Native speakers are the worst at pointing typos in my experience because they are so sure of themselves.
Agree. And yet, they are still the ones that mix up "your" and "you're", "then" and "them" and "than"
Re: Why isn't there a universal data format for résumés?
#426In 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…
Sounds like a job for a buzzword fuzzer
Re: Why isn't there a universal data format for résumés?
#427Earlier 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. Yikes. “It’s not JavaScript it’s Ecmascript! What a RED FLAG.”
The difference is that JavaScript is the name of an actual language. Where nodejs isn't the actual name of the project. The Node.js project advertises itself as a "JavaScript runtime." Both JavaScript and EMCAScript are acceptable.
[deleted]
Re: Why isn't there a universal data format for résumés?
#428Earlier quoted context omitted.
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?
[deleted]
Re: Why isn't there a universal data format for résumés?
#429In 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 recall people copy-pasting the job description and hiding it in their resume by making the text invisible just so that automated software would see a 100% keyword match. Bonus here if you use 2-3 alternate spelling for each buzzword (C++ and c++). Is that no longer done?
Re: Why isn't there a universal data format for résumés?
#430Earlier quoted context omitted.
“It’s not JavaScript it’s Ecmascript! Not comparable.
I’d say they are. Who cares if I write “Nodejs” or “Node.js”? The reader knows exactly what I meant, and that’s what matters. Anything else is just needless pedantry.
Just like if you write "alot" instead of "a lot" the reader knows exactly what you mean, and yet ...
But whatever. It's your life. You do you, and I'll do me.