Earlier quoted context omitted.
Fixing that would require not only a universal data format but also a universal taxonomy of terms A regular HR can only do CTRL-F CTRL-V efficiently in their PDF viewer, when automated system would likely test for /\bnode(?:\.?js)?\b/i, because it's a result of a development cycle, which usually includes some field analysis. HRs would LOVE to select something like "where has($node) and years($redux) >= 2 order by yea…
> They are not idiots, they just have piles of data and nonsensical tools. Disagree.
Why isn't there a universal data format for résumés?
401–410 of 472 posts
Re: Why isn't there a universal data format for résumés?
#402Earlier quoted context omitted.
Amazing - I have recently created a CV at the EU's job advert aggregation website, EURES, and that appears to be a separate thing? Great to have a standard when the own organization doesn't appear to follow it? wonder
I haven’t tried it, but you should find you can export to and from your EURES profile to Europass (and vice versa)- they are distinct, but connected.
Re: Why isn't there a universal data format for résumés?
#403There 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.)
That's not really a "universal format", though. That's an "English language format". Actually, it's an "American format" since I see it specifies "organization" instead of "organisation". Why should resumes in Vietnam or China be using English, after all.
Re: Why isn't there a universal data format for résumés?
#404Earlier quoted context omitted.
>"crazy outside-the-box madman" I like that so much that I dare not copycat it.
I think I actually scored some jobs and interviews while I still kept "wizard" at the top of my CV...
Re: Why isn't there a universal data format for résumés?
#405I 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…
that 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.
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.
Re: Why isn't there a universal data format for résumés?
#406Earlier quoted context omitted.
> They are not idiots, they just have piles of data and nonsensical tools. Disagree.
I can see why. Of course a role that requires CTRL-F level of skills attracts low-skill-required resources to a "helper" subrole. But if you replace it with automation, true skills will remain and thrive. Not that I like them on emotional level, their job is to hire you as cheap as possible and demand as much as they can. But hey it's a market. Learn to negotiate and to plan ahead financially for search periods to av…
Re: Why isn't there a universal data format for résumés?
#407There is one, it is just proprietary https://linkedin.com
Re: Why isn't there a universal data format for résumés?
#408In 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…
My basic rule of thumb is that the more structured and formal the CV submission process is, the worse the applicant to hire ratio will be, and so the more people you are up against.
For those of us in the tech industry, especially later in our careers, that probably isn't an issue, but in many other jobs, and earlier in your carreer, then it's going to be an issue. I remember having to re-enter my CV into ATSs back in 2001 for the big companies hiring graduates because they had so many to get throught, smaller companies just wanted your CVs.
Re: Why isn't there a universal data format for résumés?
#409In 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…
This is not true for the largest corporations of course. But that is a solvable problem, just provide a standardized form. You can even adapt it to the needs of the industry in question. This is actually a great boon because you can specifically ask for qualifications. There should be enough budget for that at least.
If you company easily discards applications your HR is either incompetent or it just isn't looking for candidates. But even then you try to build a connection to people applying to you. You may meet them later because they tend to work in your industry.
Again, there are special rules for the largest of corporations although I think HR should be manned enough to have a sensible recruitment process.
Re: Why isn't there a universal data format for résumés?
#410Earlier quoted context omitted.
Exactly. It would seem most of the over-confident “it’s a myth” comments in this thread are from folks not familiar with typical processes for hiring in the 100s to 1000s.
You shouldn't be hiring that many. The company might, but the managers and people doing the interviews should be looking at maybe 20 positions per year. They can read résumés themselves and give it some thought.