Nobody? https://xkcd.com/927/
CTRL+F
Why isn't there a universal data format for résumés?
41–50 of 472 posts
Re: Why isn't there a universal data format for résumés?
#42In 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 encouraged.
Re: Why isn't there a universal data format for résumés?
#43Well... Would you rather apply to a job by sending a pdf that you carefully crafted, or by sending your linkedin profile?
Re: Why isn't there a universal data format for résumés?
#44Clearly written by an applicant rather than employer. Your resume is your chance to shine, use the opportunity or pay a service to do it for you. The reason the author is trapped long enough in meat grinder hiring to notice this "problem" is likely precisely because of some indistinguishable cookie cutter bullet point soup getting them nowhere. If you can capture it in a data structure, it's not a resume! See also: w…
> If you can capture it in a data structure, it's not a resume!
Pretty sure a Word file is a data structure.
Re: Why isn't there a universal data format for résumés?
#45Could one use schema.org/Person to mark up HTML5 with appropriate microdata?
schema.org/Person is a terribly designed format, that I would not bring into new projects. Here are some of the reasons:
1. It lacks diversity (e.g. GenderType is incompatible with German laws, requiring "diverse" gender in official forms, which is definitely not "unisex" defined in the format).
2. It looks very much like a US-centric God Object. It is not clear why DUNS, ISICv4 or NAICS are there, but other identifiers like national ID or SSN are not. It would be better to have a single "identifiers" key-value map instead of them, that would be extensible.
3. Contacts would deserve a dedicated structure and key-value map (why single telephone field? why messenger IDs not there?).
Re: Why isn't there a universal data format for résumés?
#46There is! https://jsonresume.org/ But nobody really uses it for data interchange. I use it to render my resume in new layouts now and then. Although, it does let style dictate content sometimes (some templates force you to have dates down to the day for job start and end dates, etc.)
I used a JSON resume once and I like the idea. It didn't help when I had to apply for an unemployment benefit (while still trying to enter the industry) and they asked for my resume as a word document. As you can imagine, I felt like a clown trying to explain that I didn't have a word document because my resume was generated from a JSON file. I did, however, have a PDF on a USB drive I always kept on me but they refu…
tl;dr - HR is underfunded / under-resourced / un-aspirational.
Even if there were a turn-key software platform they all used, which natively supported a standard data format, they'd still find a way to screw it up.
Re: Why isn't there a universal data format for résumés?
#47There is! https://jsonresume.org/ But nobody really uses it for data interchange. I use it to render my resume in new layouts now and then. Although, it does let style dictate content sometimes (some templates force you to have dates down to the day for job start and end dates, etc.)
I used a JSON resume once and I like the idea. It didn't help when I had to apply for an unemployment benefit (while still trying to enter the industry) and they asked for my resume as a word document. As you can imagine, I felt like a clown trying to explain that I didn't have a word document because my resume was generated from a JSON file. I did, however, have a PDF on a USB drive I always kept on me but they refu…
I have my resume in markdown so I can create a word/pdf/html etc. with pandoc. It would be possible to write something that parses a json resume into markdown so it could be trivially format shifted
Re: Why isn't there a universal data format for résumés?
#48In 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…
Also having this it will give you the User to make 1 resume and apply to millions of jobs. It’s a win / win situation
Re: Why isn't there a universal data format for résumés?
#49HR 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 Manhattan it was very obvious that their onboarding process is designed for large groups - many dozens of people at a time - but the day I joined I was the only one being hired. I spent a couple hours with just myself and a single HR rep going through a half dozen rooms, in each room I had to sit as far back and to the left as possible whereas she sat at the front right of the room. She could not pass out forms until I was seated, at which point I would have to come get the form from her and return to the far side of the room to fill it out, then bring it back to her, return to my seat, then she would announce we were moving to the next room, and it would begin again. When I tried to sit at the front of the room she became extremely agitated and refused to continue until I returned to the back of the room, when I tried to get a form from her without first sitting in the back of the room same result. The rest of the company is pretty much the same, it never got better.
Re: Why isn't there a universal data format for résumés?
#50Because individuality is as valuable a commodity in the workplace as elsewhere.