I used to work in ontologies, and what I learned is that people would rather get an 80% heuristic solution for dirty data rather than a 100% correct solution for data they have to clean. The big job sites have resume parsers that work well enough from a PDF or Word doc, and then they don't have to worry about you forgetting a close tag or a mandatory field. Sure, stuff gets lost, but they get 80% of a billion resumes…
Why isn't there a universal data format for résumés?
281–290 of 472 posts
Re: Why isn't there a universal data format for résumés?
#282Re: Why isn't there a universal data format for résumés?
#283I used to work in ontologies, and what I learned is that people would rather get an 80% heuristic solution for dirty data rather than a 100% correct solution for data they have to clean. The big job sites have resume parsers that work well enough from a PDF or Word doc, and then they don't have to worry about you forgetting a close tag or a mandatory field. Sure, stuff gets lost, but they get 80% of a billion resumes…
Ideally, there would be software to save your resume in this standardized format (perhaps a word extension), which would mean there would be no cases like missing close-tags.
Re: Why isn't there a universal data format for résumés?
#284Re: Why isn't there a universal data format for résumés?
#285It’s PDF, ideally with LaTeX.
Re: Why isn't there a universal data format for résumés?
#286Earlier 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.
Re: Why isn't there a universal data format for résumés?
#287In 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…
Except it doesn't, because a lot of things in life doesn't fit in that boxes that well.
You might not have experience in node.js, but in JS and some of the node.js-alike server side VMs.
Even just a "degree in computer science" can mean many things. Furthermore you might have something which for the position is "equivalent", like a "master of science in cognitive systems with a specialization on AI" which contained a lot of CS courses, and maybe also some pr-axis experience. Or you just started working as a programming free lancer with 16. Or ...
Furthermore a resume is quite individualistic, beyond just the raw content it contains. How that content is represented can sometimes give you hints, about what kind of questions you want to ask during an interview.
I have seen a bunch of standardized forms for resumes some companies opted into, they _always_ caused endless problems.
Re: Why isn't there a universal data format for résumés?
#288Re: Why isn't there a universal data format for résumés?
#289Earlier 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.
Making such „mistakes“ actually shows quite a bit about the counterpart starting with correctness and precise communication.
Back then it drove me nuts when someone wrote „advanced in AngularJS 2“ - and it kept coming!