Why isn't there a universal data format for résumés?
441–450 of 472 posts
Re: Why isn't there a universal data format for résumés?
#442Earlier quoted context omitted.
That's why gawd invented spell checkers. Besides, I've noticed that ESL speakers make different kinds of mistakes than sloppy native speakers do.
> That's why gawd invented spell checkers. All of the lines below have red squiggly lines under them in my browser's text area: - Qt Quick - Datalog - Datomic - TensorFlow > I've noticed that ESL speakers make different kinds of mistakes than sloppy native speakers do. I've never seen a non-native speaker writing "would of" or using "they're" instead of "their". On the other hand I can't count how many times I've ski…
Yup. My wife learned her first word of English at 43, I've had plenty of time to see how one's mother tongue has a permanent effect on language. My interpretation of what I see:
She has internal word concepts. When the English words fit cleanly into her existing concepts it's easy. When two English words map into one word concept it's considerably harder, it took her a long time to correctly separate turn on from open (and turn off from close), but at least any given thing always goes the same way. In situations where that doesn't even work she will make frequent errors even to this day--do not trust her use of gender words.
Re: Why isn't there a universal data format for résumés?
#443Earlier quoted context omitted.
Some people aren't native speakers. Do they really need to know how to spell perfectly to work for you?
Knowing what the red wriggly lines mean is a start. From my experience, however, it's the native English speakers who spel the worse.
You'll get plenty of words flagged in a tech resume. Besides, spel chequers werk grate.
Re: Why isn't there a universal data format for résumés?
#444Earlier 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…
> 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. Wouldn't those issues be more likely to occur as a result of automated processing? I imagine that most humans who deal with technical hiring would guess that "node.js" and "nodejs" are probably the same thing.
A standard would include standard forms of expressing things--there shouldn't be anything (other than names) that doesn't appear in their dictionary.
Re: Why isn't there a universal data format for résumés?
#445Earlier quoted context omitted.
> The problem we have currently is that some CVs fail that review because they’re in a format that the tools cannot parse. My company (we have software for responding to applicants in real time... think apply... instant conversation with a human recruiter) did a study of about 1,200 resumes and found that 14% of resumes had inaccuracies that would cause them to be screened out... and about 9% of resumes were in a unp…
10 - 15% are typically unparsable, typically PDFs encoded as graphics, and to a lesser extent, Linkedin exports. 14% with incomplete information also sounds right. And I also concur with you on the screening being pretty basic, not ES level of sophistication at all.
The unparsable numbers are really close to what we see. Lots of work to be done to make hiring better.
Re: Why isn't there a universal data format for résumés?
#446Earlier quoted context omitted.
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. Fixing that would require not only a universal data format but also a universal taxonomy of terms to describe skills. That would need everyone to agree on how to describe what they do. Easy enough when you're describing programmin…
I'm pretty sure my Resume says "crazy outside-the-box madman" on it somewhere near the top. It pretty much guarantees that I work somewhere with a sense of humor while rejected from places that take themselves too seriously. Resumes aren't just a list of skills and work history (education isn't even on my resume anymore), it's also a chance to let a small amount of your personality show through so you stand out again…
In a previous life, I was an SRE. Volunteered as a firefighter.
"Keeps things running. Puts out fires."
Served me well on the resume, probably for quite similar reasons.
Re: Why isn't there a universal data format for résumés?
#447Looks like there's an hresume microformat but https://schema.org/Person and https://schema.org/Occupation are probably the way to mark up resumes as JSONLD.
From https://stackoverflow.com/questions/51315725/resume-work-his... :
> Schema.org's Occupation example 4, illustrates how to use Role and hasOccupation to associate an array of work history, like so:
There's already a https://schema.org/JobPosting .
Re: Why isn't there a universal data format for résumés?
#448Earlier quoted context omitted.
Then you being outside the community, have done nothing but filter out the best candidates by focusing on the wrong details under the banner of “attention to detail” It’s ego. What is the résumé’s job? To convey experience and work in a positive light. A small typo that may incidentally be the correct spelling shouldn’t derail that if the goal is to hire the most talented people.
Again, I do stand corrected. To my defense, I was going by my Bayesian prior for certain language names for which one could be 100 percent sure there was no alternate accepted spelling or capitalization. So if one put JAVA or PERL on their resume, that would generate a definite "pass" signal.
Agree or disagree, this is great feedback for job seekers. Spelling is often used as a filter.
What are some other signals that act as red flags for a potential applicant in your hiring flow?
Re: Why isn't there a universal data format for résumés?
#449I had a similar thought, actually started an open source project by myself at https://github.com/alpaylan/cvdl
My view is to have it similar to html/css paradigm of web. I started working with TOML based schemas for defining CV's, actually wrote my CV in the schema.
If you wanna go forward, I would love to be a contributor, also I would love to get your opinions.
Re: Why isn't there a universal data format for résumés?
#450Earlier quoted context omitted.
Again, I do stand corrected. To my defense, I was going by my Bayesian prior for certain language names for which one could be 100 percent sure there was no alternate accepted spelling or capitalization. So if one put JAVA or PERL on their resume, that would generate a definite "pass" signal.
Agree or disagree, this is great feedback for job seekers. Spelling is often used as a filter. What are some other signals that act as red flags for a potential applicant in your hiring flow?
Well another major turn-off would be: a "primary skills" section that mentions 30 different random applications / protocols that one might have been incidentally exposed to for a week or 2 at some job ... 15 years ago. No one can be expert-level in all of these things. Just tell us the top 3-6 that really matter and which define you.
Or even if it's just 1 or 2. It's infinitely better to hire someone who is in fact really solid at what they say they know, than someone who tries to spam you with every random keyword they've been exposed to in the hope that you won't drill down and ask them any hard questions about most of them.
That, and skill listings that don't pass the "apples and orange" test. For example:
Programming languages: Java, Perl, PHP, XML, HTML, CSS, Bootstrap