Skip to content

Media

JSON Resume, for the record

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

Alex Example's fictional résumé, rendered from the example JSON

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.

Facts about JSON Resume
FactValueSource
Started2014Public discussion, 7 July 2014
Co-foundersThomas Davis and Roland Sharp2014 release announcement
Schema version1.7.1Package source
Resume sections14Schema source
Themes in the gallery227Theme gallery
LicenseMITLicense text

Worth knowing

The schema, tools and hosted registry are distinct parts of the project; you can use the format without publishing anything to the registry. A common file format does not guarantee acceptance by an employer or applicant tracking system: supported fields and output depend on the tool and theme.

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.

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.