It’s 2021, and finding a job is still a royal pain.
What should you put in your résumé? How should you structure it?
And for goodness' sake, WHAT is the point of uploading a résumé when applying for a job, if the applicant tracking system (“ATS”) requires you to enter all the same information over again manually?
Of course we have optical character recognition (“OCR”) systems that try to parse your (usually Word or PDF) résumé and automatically fill out the ATS database, but if you’ve used one of these in the last ever, you know how well they work.
What if a computer could read your résumé correctly, completely, instantly? What if the only thing you had to do to apply for a job, was to simply upload a single file? What if, after you spent an hour typing your professional history into, say, LinkedIn, you could push an export button and retrieve such a computer-readable file? What if you could take that same file and upload it to, say, Indeed, and have your profile corrected/completed instantly, instead of typing it all out again? And what if we - as humanity - could use this form of black magic as a wedge to pry cover letters away from the the cold dead fingers of the industry?
What if, indeed.
Small Ideas, Executed
Today the Career Schema Project humbly, but proudly, presents to the world the initial alpha draft of its flagship schema, bio-v0.1.0.json. CSP will adhere to the JSON Schema specifications and will each individually follow Semantic Versioning.
Yes, “bio” is a terrible name - we’re working on it. But this schema describes a document that at once replaces both résumés and CVs with a single document format that is both machine readable and, if you’ve got the stomach for editing JSON by hand, human editable.
This is still early. We’re talking Iron Man Mark I early. But the Project is moving quickly and we expect a release candidate spec by the end of Q2 2021.
There are still a bevy of attributes to be added to the spec, a lot of bickering over which attributes are required vs optional, and a ton of documentation to be written, not to mention software libraries, test suites, conversion tools, and the list goes on for quite a while. Nevertheless, while Google hoovers up all of your data for advertising, Spotify tries to fight Netflix for your subscription money, and Windows 10 treats your desktop like a billboard, this Project remains committed to using software for Good™.
The first few phases of this Project aren’t difficult tasks, technologically… so why hasn’t anyone else done it yet? It boils down to a basic lack of incentive. Anyone who is looking for work knows it’s a full time job, and when the pain is most acute for the technologists equipped to solve it, they’ve got bigger fish to fry. As for the job sites and ATS vendors, frankly there’s no obvious economic motive to increase portability and interoperabiilty of this data as it only serves to reudce the friction against adoption of their competition.
We don’t think these are major blockers. As for developer time, we’re solving that by simply taking the first step and getting the ball rolling. As for the job boards and ATS vendors (the “demand side” of the talent market) we have some good thoughts on how to update their thinking and get them involved when the time is right.
The short-term roadmap is fairly clear. In some semblance of order:
- A 1.0 schema draft, along with documentation and samples
- A command line interface (“CLI”) tool for simple manipulation of CSP documents
- Software libraries for advanced manipulation of CSP documents
- A freely usable website for non-techies to enter their information in a simple GUI and download an CSP document
- Meaningful outreach to the job listing sites and ATS vendors for integration and adoption discussions
Soon we’ll publish a more detailed version of this roadmap, and another time we’ll post the real long-term vision stuff. But odds are, the above items will keep us busy for a while.