8 ms·

JSON Resume – 5th Birthday and New Features

yingw787 7y ago
Very cool to see this progressing! I remember reading about this site in college. One tip, I think the HTTPS site is requesting HTTP resources for CSS/Google Fonts, which Chrome blocks, so I can't see the themes in their full glory :-)
oweiler 7y ago
The post is from 2018.
- thomasfromcdnjs 7y ago
  That is my bad, static site generator where you input the date manually. Fixing now.
krossitalk 7y ago
One of the examples has a number of missing values (,,) and the literal 'undefined', starting around the Education section https://registry.jsonresume.org/beeman https://registry.jsonresume.org/beeman
- thomasfromcdnjs 7y ago
  Thanks! I will let the user know.
toyg 7y ago
Uh, there was already an XML format for this, I remember doing my CV with it. Nobody ever asked to see it or use it, so I stopped updating it. I learnt a few years later that some HR/recruiter systems do use it, behind the scenes, to talk to each other, they just never surface it. Why would this surface more often...? The HR industry is not made by coders, they live in MSWord and GDocs.
- ben509 7y ago
  I'm thinking of using it (or a slightly hacked modification) because I keep a "master" resume in a messy LaTeX doc with lots of crap I usually filter out, and with variable accuracy in things like dates. But if I change careers, it will be useful because I'll have all that material ready to put back in. Even while you're searching, having your different versions based on a single source of truth helps you keep everything consistent. And you can then convert your source data to MSWord or other formats. It outputs HTML, so it's already a click away. (Careful sending any easily editable format to some recruiters, they're liable to "enhance" it for you.)
  - toyg 7y ago
    > (Careful sending any easily editable format Of course, I only send PDFs (closest you can get to non-editable without going exotic). Personally, these days I just export my LinkedIn bio and then tailor to the particular application. Unless LI starts exposing this, I have no real use for it.
- deleted 7y ago
  [deleted]
goblin89 7y ago
Instead of going with an ad-hoc schema, I wish JSON Resume built on top of data structures standardized by Schema.org. They cover most of the concepts required—https://schema.org/Person https://schema.org/Person, https://schema.org/skills https://schema.org/skills, https://pending.schema.org/knowsAbout https://pending.schema.org/knowsAbout, the list goes on. For concepts not covered by Schema.org (I spotted only one, “interests”) the project could implement custom extensions until they are adopted by the shared vocabulary.
- thomasfromcdnjs 7y ago
  I personally don't disagree, we've always thought it best to leverage other peoples work first. Though one of the largest discussions we had on the specification was the definition of what a name was -> https://github.com/jsonresume/resume-schema/issues/4 https://github.com/jsonresume/resume-schema/issues/4 After everyone's input, we decided to just opt for one field `name` because simply first/last/family name does not work across cultures. When we looked at schema.orgs definition of Person, they went down the avenue of trying to split the name up which still wouldn't fit all use cases. https://schema.org/Person https://schema.org/Person
  - Jean-Philipe 7y ago
    > After everyone's input, we decided to just opt for one field `name` because simply first/last/family name does not work across cultures. Thank you so much for this! Me and family members struggle filling forms because of this on a regular basis. Another pet peeve of mine are address fields. Why not just one field? People are smart enough to write down their address. Not everyone has a zip code or a street number, or streets for that matter.
    - stronglikedan 7y ago
      > Why not just one field? Sales tax calculations by region.
    - nulbyte 7y ago
      > People are smart enough to write down their address. Not usually. In this scenario, given its use for display on a user page, it may make sense. For most other cases, this doesn't pan out. Here in the US, for example, the general public has little sense of how to properly write addresses with floor, apartment, unit, or suite numbers. Folks routinely put things in the wrong order or use the wrong symbol or abbreviation. Others make up nonsense and genuinely think what they have is correct. Developers and geeks aren't immune; I've seen forms that reflect an inadequate understanding of addresses.
sam_lowry_ 7y ago
By the 10th birthday, you should have implemented the LinkedIn export as well ;-)
- thomasfromcdnjs 7y ago
  baha I linked in another comment -> https://joshuatz.com/projects/web-stuff/linkedin-profile-to-json-resume-exporter-bookmarklet/ https://joshuatz.com/projects/web-stuff/linkedin-profile-to-... Slowly getting there
ddebernardy 7y ago
How much traction is this getting in job-tech startups? For instance, LinkedIn, Indeed, etc., as well as applicant tracking systems, and so forth.
- hrktb 7y ago
  > LinkedIn, Indeed, etc., At this level, they won't care for an open format as they can just ask you to reenter all the info in their own form. They assume if you are effectively looking for a job a 10~30 min data entry for each of these sites won't deter you. Or worse, you'll get tired of entering your data again and again, and won't go to their smaller competitors even if they make more efforts to accommodate you. I did the whole dance a year ago, and a candidate's time seems to be the least valuable resource in the system (or it's used as a currency to price how much you are dedicated to getting that job)
  - thomasfromcdnjs 7y ago
    This is true in our experience. We had visions of exporting Linked in profiles to the schema but about a year after launch LinkedIn completely disable API access to user profiles making it virtually impossibly. A developer built a bookmarklet that does it thought -> https://joshuatz.com/projects/web-stuff/linkedin-profile-to-json-resume-exporter-bookmarklet/ https://joshuatz.com/projects/web-stuff/linkedin-profile-to-... Works surprisingly well.
pknopf 7y ago
Pro tip, just creating your own schema. Tailor it to your theme. Here is my resume (as YAML): https://github.com/pauldotknopf/resume/blob/staging/resume.yml https://github.com/pauldotknopf/resume/blob/staging/resume.y... This file is consumed and used in a very small ad-hoc project, specifically for my format: https://github.com/pauldotknopf/resume/blob/staging/statik-resume-generator/src/Resume/Program.cs https://github.com/pauldotknopf/resume/blob/staging/statik-r... Here is the final result: https://resume.pknopf.com/ https://resume.pknopf.com/ Easy maintenance. Maximum flexibility. Low tooling.
- MikeKusold 7y ago
  I use JSON to store my resume, and Latex to format it. Here is a snippet: ``` \begin{luacode} require("lualibs.lua") local file = io.open('data.json') local jsonstring = file:read('*a') file.close() local jsonData = utilities.json.tolua(jsonstring) -- Header -- local personal = jsonData["personal"] -- Education -- local education = jsonData["education"] tex.print('\\section{Education}') for key, value in pairs (education) do tex.print('\\cventry{' .. value["year"] .. '}{' .. value["degree"] .. '}{' .. value["school"] .. '}{' .. value["location"] .. '}{}{' .. value["specialty"] .. '}') end ```
- matthewbauer 7y ago
  LaTeX + ORG mode is an easy way to get some literate programming features while also still using a real typesetting engine. You can reuse my setup here: https://github.com/matthewbauer/resume https://github.com/matthewbauer/resume
  - michael-ax 7y ago
    Thank you! and thanks for not forcing bibtex into it.
- paultopia 7y ago
  Yeah, I've done the same, though I kind of went egregiously over the top (academic website with vue.js + tex resume with all kinds of machinery generated from a bunch of yaml files): https://github.com/paultopia/websiterevision2017 https://github.com/paultopia/websiterevision2017
crabasa 7y ago
So, I am working on a "better resume" product for developers: https://fizbuz.com https://fizbuz.com We plan on shipping API support so that developers can build better experiences on top of the data (alternate rendering engines, import/export, etc). I'd love to see about supporting export to JSON Resume. Is there a list of ecosystem tools that speak this format?
- thomasfromcdnjs 7y ago
  We haven't done a good job of showing casing community tooling. It is on our high priority list. That being said, you can scroll through https://github.com/search?o=desc&q=jsonresume&s=updated&type=Repositories https://github.com/search?o=desc&q=jsonresume&s=updated&type... to get an idea of what is out there.
- nv-vn 7y ago
  As someone who doesn't do any kind of web dev it seems like this isn't designed for my use case. E.g. things like Android or iOS development didn't seem to be present, let alone more niche things like embedded, graphics, etc.
brianzelip 7y ago
Congrats. I remember the HN discussion 5 years ago, and appreciated it then too.
frenchman99 7y ago
Gotta love the "undefined" next to "Egghead Instructor" on one of the example resumes, given that Egghead's pitch is "Learn the best JavaScript tools and frameworks from industry pros". https://imgur.com/a/4qVeeca https://imgur.com/a/4qVeeca
irrational 7y ago
It took me way too long to realize resume meant résumé (written summary of my experiences) instead of resume (to continue)! I was thinking JSON Resume was the next version of JSON, maybe adding the ability to have comments in JSON.
- agumonkey 7y ago
  Or lazy loaded json as stream of objects
  - hombre_fatal 7y ago
    Well, you can already parse JSON SAX-style. Or with newline delimiters.
- 0xJRS 7y ago
  Its not super great but i’ve become a fan of doing this: { “name”: “Michael Scott”, “age”: 40, “_comments”: [“”] }
  - toyg 7y ago
    Literally the "hot comments" pattern ;)
heinrichhartman 7y ago
Aside: > resume export resume.pdf (Currently broken, help needed) https://jsonresume.org/getting-started/ https://jsonresume.org/getting-started/ Any news here? Still puzzling to me, how hard it is to generate PDF documents. I assume this is not using Latex, since that would be a gigantic dependency to pull in. What is/was jsonresume using? Why did it break? PS: Also pdf export on wikipedia has been broken for years now. Seems to be a hard problem. Any information about light-weight pdf generators that work and produce decent pdfs documents would be appreciated.
- ilaksh 7y ago
  https://github.com/jsonresume/resume-cli/pull/294 https://github.com/jsonresume/resume-cli/pull/294
- vcavallo 7y ago
  maybe have a good css sheet for print styles and encourage people to print -> save as pdf?
elcomet 7y ago
I wish it was called yamlresume.org instead of jsonresume.org. Json is not designed for humans.
- ilaksh 7y ago
  yamlresume.org is available. There are multiple projects on GitHub that generate resumes from yaml. The new concept is a lambda function that pulls from a gist. It would not be very hard to do something similar with yaml.
rdiddly 7y ago
Tried it out, but got "Error: could not handle the request" Wish I knew more. I don't think it's the HN Hug of Death™ because I was able to get it to complain about my malformed JSON earlier (since fixed).
the_resistence 7y ago
Really great to see some activity. I thought the project was dead, no offense. Are the problems around an excellent MS Word and PDF versions intractable? Just asking since I don't know node.js/json world well.

Very cool to see this progressing! I remember reading about this site in college. One tip, I think the HTTPS site is requesting HTTP resources for CSS/Google Fonts, which Chrome blocks, so I can't see the themes in their full glory :-)

oweiler 7y ago

The post is from 2018.

thomasfromcdnjs 7y ago
That is my bad, static site generator where you input the date manually. Fixing now.

krossitalk 7y ago

One of the examples has a number of missing values (,,) and the literal 'undefined', starting around the Education section https://registry.jsonresume.org/beeman https://registry.jsonresume.org/beeman

thomasfromcdnjs 7y ago
Thanks! I will let the user know.

toyg 7y ago

Uh, there was already an XML format for this, I remember doing my CV with it. Nobody ever asked to see it or use it, so I stopped updating it. I learnt a few years later that some HR/recruiter systems do use it, behind the scenes, to talk to each other, they just never surface it. Why would this surface more often...? The HR industry is not made by coders, they live in MSWord and GDocs.

ben509 7y ago
I'm thinking of using it (or a slightly hacked modification) because I keep a "master" resume in a messy LaTeX doc with lots of crap I usually filter out, and with variable accuracy in things like dates. But if I change careers, it will be useful because I'll have all that material ready to put back in. Even while you're searching, having your different versions based on a single source of truth helps you keep everything consistent. And you can then convert your source data to MSWord or other formats. It outputs HTML, so it's already a click away. (Careful sending any easily editable format to some recruiters, they're liable to "enhance" it for you.)
- toyg 7y ago
  > (Careful sending any easily editable format Of course, I only send PDFs (closest you can get to non-editable without going exotic). Personally, these days I just export my LinkedIn bio and then tailor to the particular application. Unless LI starts exposing this, I have no real use for it.
deleted 7y ago
[deleted]

goblin89 7y ago

Instead of going with an ad-hoc schema, I wish JSON Resume built on top of data structures standardized by Schema.org. They cover most of the concepts required—https://schema.org/Person https://schema.org/Person, https://schema.org/skills https://schema.org/skills, https://pending.schema.org/knowsAbout https://pending.schema.org/knowsAbout, the list goes on. For concepts not covered by Schema.org (I spotted only one, “interests”) the project could implement custom extensions until they are adopted by the shared vocabulary.

thomasfromcdnjs 7y ago
I personally don't disagree, we've always thought it best to leverage other peoples work first. Though one of the largest discussions we had on the specification was the definition of what a name was -> https://github.com/jsonresume/resume-schema/issues/4 https://github.com/jsonresume/resume-schema/issues/4 After everyone's input, we decided to just opt for one field `name` because simply first/last/family name does not work across cultures. When we looked at schema.orgs definition of Person, they went down the avenue of trying to split the name up which still wouldn't fit all use cases. https://schema.org/Person https://schema.org/Person
- Jean-Philipe 7y ago
  > After everyone's input, we decided to just opt for one field `name` because simply first/last/family name does not work across cultures. Thank you so much for this! Me and family members struggle filling forms because of this on a regular basis. Another pet peeve of mine are address fields. Why not just one field? People are smart enough to write down their address. Not everyone has a zip code or a street number, or streets for that matter.
  - stronglikedan 7y ago
    > Why not just one field? Sales tax calculations by region.
  - nulbyte 7y ago
    > People are smart enough to write down their address. Not usually. In this scenario, given its use for display on a user page, it may make sense. For most other cases, this doesn't pan out. Here in the US, for example, the general public has little sense of how to properly write addresses with floor, apartment, unit, or suite numbers. Folks routinely put things in the wrong order or use the wrong symbol or abbreviation. Others make up nonsense and genuinely think what they have is correct. Developers and geeks aren't immune; I've seen forms that reflect an inadequate understanding of addresses.

sam_lowry_ 7y ago

By the 10th birthday, you should have implemented the LinkedIn export as well ;-)

thomasfromcdnjs 7y ago
baha I linked in another comment -> https://joshuatz.com/projects/web-stuff/linkedin-profile-to-json-resume-exporter-bookmarklet/ https://joshuatz.com/projects/web-stuff/linkedin-profile-to-... Slowly getting there

ddebernardy 7y ago

How much traction is this getting in job-tech startups? For instance, LinkedIn, Indeed, etc., as well as applicant tracking systems, and so forth.

hrktb 7y ago
> LinkedIn, Indeed, etc., At this level, they won't care for an open format as they can just ask you to reenter all the info in their own form. They assume if you are effectively looking for a job a 10~30 min data entry for each of these sites won't deter you. Or worse, you'll get tired of entering your data again and again, and won't go to their smaller competitors even if they make more efforts to accommodate you. I did the whole dance a year ago, and a candidate's time seems to be the least valuable resource in the system (or it's used as a currency to price how much you are dedicated to getting that job)
- thomasfromcdnjs 7y ago
  This is true in our experience. We had visions of exporting Linked in profiles to the schema but about a year after launch LinkedIn completely disable API access to user profiles making it virtually impossibly. A developer built a bookmarklet that does it thought -> https://joshuatz.com/projects/web-stuff/linkedin-profile-to-json-resume-exporter-bookmarklet/ https://joshuatz.com/projects/web-stuff/linkedin-profile-to-... Works surprisingly well.

pknopf 7y ago

Pro tip, just creating your own schema. Tailor it to your theme. Here is my resume (as YAML): https://github.com/pauldotknopf/resume/blob/staging/resume.yml https://github.com/pauldotknopf/resume/blob/staging/resume.y... This file is consumed and used in a very small ad-hoc project, specifically for my format: https://github.com/pauldotknopf/resume/blob/staging/statik-resume-generator/src/Resume/Program.cs https://github.com/pauldotknopf/resume/blob/staging/statik-r... Here is the final result: https://resume.pknopf.com/ https://resume.pknopf.com/ Easy maintenance. Maximum flexibility. Low tooling.

MikeKusold 7y ago
I use JSON to store my resume, and Latex to format it. Here is a snippet: ``` \begin{luacode} require("lualibs.lua") local file = io.open('data.json') local jsonstring = file:read('*a') file.close() local jsonData = utilities.json.tolua(jsonstring) -- Header -- local personal = jsonData["personal"] -- Education -- local education = jsonData["education"] tex.print('\\section{Education}') for key, value in pairs (education) do tex.print('\\cventry{' .. value["year"] .. '}{' .. value["degree"] .. '}{' .. value["school"] .. '}{' .. value["location"] .. '}{}{' .. value["specialty"] .. '}') end ```
matthewbauer 7y ago
LaTeX + ORG mode is an easy way to get some literate programming features while also still using a real typesetting engine. You can reuse my setup here: https://github.com/matthewbauer/resume https://github.com/matthewbauer/resume
- michael-ax 7y ago
  Thank you! and thanks for not forcing bibtex into it.
paultopia 7y ago
Yeah, I've done the same, though I kind of went egregiously over the top (academic website with vue.js + tex resume with all kinds of machinery generated from a bunch of yaml files): https://github.com/paultopia/websiterevision2017 https://github.com/paultopia/websiterevision2017

crabasa 7y ago

So, I am working on a "better resume" product for developers: https://fizbuz.com https://fizbuz.com We plan on shipping API support so that developers can build better experiences on top of the data (alternate rendering engines, import/export, etc). I'd love to see about supporting export to JSON Resume. Is there a list of ecosystem tools that speak this format?

thomasfromcdnjs 7y ago
We haven't done a good job of showing casing community tooling. It is on our high priority list. That being said, you can scroll through https://github.com/search?o=desc&q=jsonresume&s=updated&type=Repositories https://github.com/search?o=desc&q=jsonresume&s=updated&type... to get an idea of what is out there.
nv-vn 7y ago
As someone who doesn't do any kind of web dev it seems like this isn't designed for my use case. E.g. things like Android or iOS development didn't seem to be present, let alone more niche things like embedded, graphics, etc.

brianzelip 7y ago

Congrats. I remember the HN discussion 5 years ago, and appreciated it then too.

frenchman99 7y ago

Gotta love the "undefined" next to "Egghead Instructor" on one of the example resumes, given that Egghead's pitch is "Learn the best JavaScript tools and frameworks from industry pros". https://imgur.com/a/4qVeeca https://imgur.com/a/4qVeeca

irrational 7y ago

It took me way too long to realize resume meant résumé (written summary of my experiences) instead of resume (to continue)! I was thinking JSON Resume was the next version of JSON, maybe adding the ability to have comments in JSON.

agumonkey 7y ago
Or lazy loaded json as stream of objects
- hombre_fatal 7y ago
  Well, you can already parse JSON SAX-style. Or with newline delimiters.
0xJRS 7y ago
Its not super great but i’ve become a fan of doing this: { “name”: “Michael Scott”, “age”: 40, “_comments”: [“”] }
- toyg 7y ago
  Literally the "hot comments" pattern ;)

heinrichhartman 7y ago

Aside: > resume export resume.pdf (Currently broken, help needed) https://jsonresume.org/getting-started/ https://jsonresume.org/getting-started/ Any news here? Still puzzling to me, how hard it is to generate PDF documents. I assume this is not using Latex, since that would be a gigantic dependency to pull in. What is/was jsonresume using? Why did it break? PS: Also pdf export on wikipedia has been broken for years now. Seems to be a hard problem. Any information about light-weight pdf generators that work and produce decent pdfs documents would be appreciated.

ilaksh 7y ago
https://github.com/jsonresume/resume-cli/pull/294 https://github.com/jsonresume/resume-cli/pull/294
vcavallo 7y ago
maybe have a good css sheet for print styles and encourage people to print -> save as pdf?

elcomet 7y ago

I wish it was called yamlresume.org instead of jsonresume.org. Json is not designed for humans.

ilaksh 7y ago
yamlresume.org is available. There are multiple projects on GitHub that generate resumes from yaml. The new concept is a lambda function that pulls from a gist. It would not be very hard to do something similar with yaml.

rdiddly 7y ago

Tried it out, but got "Error: could not handle the request" Wish I knew more. I don't think it's the HN Hug of Death™ because I was able to get it to complain about my malformed JSON earlier (since fixed).

the_resistence 7y ago

Really great to see some activity. I thought the project was dead, no offense. Are the problems around an excellent MS Word and PDF versions intractable? Just asking since I don't know node.js/json world well.