XYZ Corp is interested in learning more about you, so we are pleased to offer you the opportunity to now submit an XYZ Corp resume: Please follow [this link] for instructions on filling out the XYZ resume format correctly!
Why isn't there a universal data format for résumés?
131–140 of 472 posts
Re: Why isn't there a universal data format for résumés?
#132Earlier 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…
I believe I understand your point – therefore I would like to take this opportunity to channel something that 'patio11 wrote on Twitter many years ago: “Do not send in a job application before you have an actual human being who has expressed enthusiasm for reading or forwarding it.”[0] I believe this is sound advice, and the pitfalls you mentioned was probably the reasons that he gave this advice. [0] https://twitter…
Re: Why isn't there a universal data format for résumés?
#133I 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…
Re: Why isn't there a universal data format for résumés?
#134Earlier 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…
> 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 I'm sure this happened somewhere at some point in time, but IMO it's becoming a myth blown out of proportion. I…
Tech companies doing recruiting of any meaningful volume are indeed generally using searches or matches of some kind at the start of the funnel.
Re: Why isn't there a universal data format for résumés?
#135Earlier quoted context omitted.
Don't they kind of do that at larger organizations with EDI? Or is it still nonstandard between organizations?
EDI is only semi-standardized; in my experience usually each pair of trading partners requires a separate effort (usually the bigger partner imposes the requirement and the smaller one has to make changes). Some difficulties include: * There are multiple protocols for exchanging EDI documents (AS1, SMTP, FTPS, SFTP...) * There are multiple standards for the documents themselves (EDIFACT, X12, GS1 XML...) * There are…
Re: Why isn't there a universal data format for résumés?
#136HR people don’t like changing their procedures. I’ve done numerous interviews large corporations where the first part of the interview process involved copying my printed resume by hand onto sheets of paper so that someone could then type in what I had written into a web browser. Why they couldn’t just copy from my printed resume or accept soft copy in word or ascii I have no answers for. When I joined at Chase Manha…
- worked at a place where they printed A3 excel sheet to write new prices on paper with a pencil
- courthouse procedures are peak redundancy, it's like the opposite of any database normalization 101, the more you copy the same data in various formats the better, and do not question why. It's systemically settled, since everybody expect the data to look like this, any deviation will trigger anxiety, and since they have no information management training they will scream for missing data even though there's still 12 copies of it scattered around the page, just like the emacs keyboard xkcd blended with the old waiting room social mirroring experiment
Re: Why isn't there a universal data format for résumés?
#137Earlier 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…
I’m curious if you have much evidence that this is common? I suspect it’s mostly a myth that is easy to believe (it can feel good to believe it because it means you were removed from the applicant pipeline because of stupid computer reasons rather than because you don’t appear to meet some bar to a human, even if that bar is a stupid thing like prestige) and oft repeated. I definitely think it’s likely that most peop…
I think the fact it’s low cost to avoid and high cost if it occurs keeps most people just doing it regardless of whether it’s true or not
Re: Why isn't there a universal data format for résumés?
#138In 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…
As a hiring manager you’d be inclined to disagree. If resumes could be standardized and easily searchable for information it would help find candidates much more accurately and quickly without having to read. Even better would be if there was a verification standard where you could get a blue checkmark on your resume meaning all the information is accurate and not made up bullshit, then you could limit searches only…
Re: Why isn't there a universal data format for résumés?
#139Earlier 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…
I’m curious if you have much evidence that this is common? I suspect it’s mostly a myth that is easy to believe (it can feel good to believe it because it means you were removed from the applicant pipeline because of stupid computer reasons rather than because you don’t appear to meet some bar to a human, even if that bar is a stupid thing like prestige) and oft repeated. I definitely think it’s likely that most peop…
For external candidates, we see less than 30% of all resumes. As with all things, 80% of the rest are junk and another 20% are potentially viable candidates.
Re: Why isn't there a universal data format for résumés?
#140HR people don’t like changing their procedures. I’ve done numerous interviews large corporations where the first part of the interview process involved copying my printed resume by hand onto sheets of paper so that someone could then type in what I had written into a web browser. Why they couldn’t just copy from my printed resume or accept soft copy in word or ascii I have no answers for. When I joined at Chase Manha…
That sounds like an incredibly unsettling experience.