Media
JSON Resume, for the record
Facts, ready-to-use text, a fictional example and original sources for people writing about the project.

Copy
In a sentence or two
Short description
JSON Resume is a community-developed, open-source schema for expressing a résumé as JSON. Started in 2014 by Thomas Davis and Roland Sharp, it separates career information from presentation so compatible tools can use the same data to build documents and portfolio websites.
Founder bio
Thomas Davis co-founded JSON Resume with Roland Sharp in 2014. His contributions include work on the project's schema, command-line tools and hosted registry.
Checked 21 October 2026
Facts, with sources
Counts come from the project’s source. They are not estimates of how many people use JSON Resume.
| Fact | Value | Source |
|---|---|---|
| Started | 2014 | Public discussion, 7 July 2014 |
| Co-founders | Thomas Davis and Roland Sharp | 2014 release announcement |
| Schema version | 1.7.1 | Package source |
| Resume sections | 14 | Schema source |
| Themes in the gallery | 227 | Theme gallery |
| License | MIT | License text |
Worth knowing
Downloads
One example, ready to use
Meet Alex Example, a fictional profile you can show without exposing anyone’s details. The fictional example, screenshots and factsheet may be reproduced with attribution to JSON Resume (jsonresume.org). Please caption the résumé as a fictional example.
PNG · 1200×900Example résumé (screenshot)Alex Example, a fictional profile safe to publish.
PNG · 1200×900Project overview (screenshot)How the schema, tools and themes fit together.- HTMLExample résumé (HTML)The rendered example, ready to open.
- JSONExample résumé (JSON)The data behind it, to try in any tool.
- TXTFactsheetDescription, founder bio and sources as plain text.
Interviews
Talk to us
Thomas Davis
Co-founder, JSON Resume
Available to discuss the project's history, résumé data portability and maintaining open-source tools.
thomasalwyndavis@gmail.com · GitHub · Résumé
Include your publication, topic, deadline and time zone. Questions about a third-party tool are best sent to its maintainers.