4 ms·
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 fo
by jfengel 5y ago
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 rather than 100% of a million of them. They can't exchange data or even trust what they have, but it's good enough for them to make money. Meanwhile, a competitor demanding good data from its clients never gets off the ground.
Anyway, every data format for human information ends up being either vague (to allow in everything) or impossible (see the myths that programmers believe about names, time, addresses, etc.) You end up giving a string for each field... Then give up, just accept any string, and hope for the best.
Everybody wants Google or some machine learning solution because the formats never work for the information people want to convey. Better solutions could exist but the hacky ones are first to market, in a natural monopoly where there really only needs one good enough product.
If you think a lack of a good resume format is bad, look at electronic health records. Those are far more important to be correct and exchangeable, and even there the cleanup effort is always enormous.
- tomcat27 5y agothat still doesn't really explain why big companies have not initiated a RFC for resume format. they only have to come up with an RFC and just ask everyone to follow. The cost of producing such an RFC is so small. guaranteed reduction in inefficiencies including operational costs. my gut feeling is that 20% improvement could have big butterfly effects.
- andylynch 5y agoThey have - it's called HR-XML. It's mostly B2B but if you use EuroPass CV it's using this under the covers
- jfengel 5y agoBecause they don't want to commit to it. It would instantly become legacy and an increasing thorn in their sides. That was what I learned in ontologies: there is nothing so well understood and immutable that the business case won't change. It's so much easier to be vague than to be clear. I too was convinced that people would rather have good clean data that they could trust, and it would save them a ton of money in the long term while costing a little up front. Maybe someone out there can sell that idea, but it wasn't me.
- tomcat27 5y agovery little in resumes format changed in the last 50 years.
- bsder 5y ago> Those are far more important to be correct and exchangeable In the US, those are far more important to be billable. And that's the problem. Encoding the patient's medical state is simply an afterthought.
- rightisleft 5y agoThis is a great comment for most data collection use-cases *****
- a9h74j 5y agoHence RSO: Resume Search Optimization
- finolex1 5y agoIdeally, 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.
- jacob_rezi 5y agoWe've built standardized metadata into all downloaded resumes with our resume software at https://rezi.ai https://rezi.ai
- berkes 5y agoThis hinges on a false dichotomy. You can have the current sloppy parsers AND a jsonresume.org parser besides each other. You can even hide the latter behind a tiny 'other upload formats' link, if you are afraid this option deters uploads of PDFs or docxs.
- woolion 5y agoThis is exactly what is done with invoices. You can get them as pdf that embed its content as xml, and the receiving ERP software that will load it will try to find the xml, or default to OCR.