JSON Resume: How to Convert Your Resume to JSON Format

What is JSON Resume?

JSON Resume is an open-source initiative that defines a standardised JSON schema for resumes. Instead of keeping your career history locked inside a Word document or PDF, you store it as structured, machine-readable JSON. The schema covers everything recruiters and ATS (Applicant Tracking Systems) look for — contact info, work experience, education, skills, projects, and more.

Because the data is just JSON, you get all the advantages that developers already love: version control with Git, easy diffing between versions, programmatic rendering into multiple formats, and seamless integration with APIs and automation pipelines.

Why Convert Your Resume to JSON?

1. Single Source of Truth

Maintaining multiple resume versions — one for design roles, another for engineering, a third for freelance platforms — quickly gets out of hand. With a JSON resume, you keep one canonical data file and generate tailored outputs from it. Change your job title once and every rendered version updates automatically.

2. ATS-Friendly Structure

Most Applicant Tracking Systems parse resumes into structured fields. When your resume is already structured as JSON, the mapping is near-perfect. Fields like work[].position, education[].institution, and skills[].name align directly with what ATS software expects.

3. Portability and Automation

A JSON resume can be consumed by static-site generators, portfolio builders, LinkedIn import tools, and CI/CD pipelines. Some developers even build their personal site by fetching a resume.json hosted as a GitHub Gist and rendering it with a theme engine at build time.

4. Version Control and Diffing

Because JSON is plain text, you can track every edit in Git. Need to see what you changed before your last interview? Run git diff or use a JSON diff tool to compare versions side by side.

The JSON Resume Schema

The official schema (currently at v1.0.0) defines a top-level object with these sections:

{
  "basics": { ... },
  "work": [ ... ],
  "volunteer": [ ... ],
  "education": [ ... ],
  "awards": [ ... ],
  "certificates": [ ... ],
  "publications": [ ... ],
  "skills": [ ... ],
  "languages": [ ... ],
  "interests": [ ... ],
  "references": [ ... ],
  "projects": [ ... ]
}

Every section is optional, so you only include what applies to you. Let’s walk through the most important parts.

The Basics Object

{
  "basics": {
    "name": "Jane Doe",
    "label": "Full-Stack Developer",
    "image": "https://example.com/photo.jpg",
    "email": "jane@example.com",
    "phone": "+1-555-123-4567",
    "url": "https://janedoe.dev",
    "summary": "Full-stack developer with 6 years of experience building scalable web applications with React, Node.js, and PostgreSQL.",
    "location": {
      "city": "San Francisco",
      "countryCode": "US",
      "region": "California"
    },
    "profiles": [
      {
        "network": "GitHub",
        "username": "janedoe",
        "url": "https://github.com/janedoe"
      },
      {
        "network": "LinkedIn",
        "username": "janedoe",
        "url": "https://linkedin.com/in/janedoe"
      }
    ]
  }
}

The basics object holds your identity and contact details. The label field acts as your professional headline, and profiles lets you link to any social or professional platform.

Work Experience

{
  "work": [
    {
      "name": "Acme Corp",
      "position": "Senior Frontend Engineer",
      "url": "https://acme.com",
      "startDate": "2021-03-01",
      "endDate": "",
      "summary": "Leading the design-system team responsible for the component library used by 12 product teams.",
      "highlights": [
        "Reduced bundle size by 35% through tree-shaking and code-splitting",
        "Introduced Storybook-driven development, cutting UI review time in half",
        "Mentored 4 junior developers through quarterly tech talks"
      ]
    }
  ]
}

Each entry in the work array follows the same shape. Leave endDate empty for your current role. The highlights array is perfect for bullet points that demonstrate impact.

Skills and Education

{
  "skills": [
    {
      "name": "Frontend",
      "level": "Senior",
      "keywords": ["React", "TypeScript", "Next.js", "CSS-in-JS"]
    },
    {
      "name": "Backend",
      "level": "Mid",
      "keywords": ["Node.js", "PostgreSQL", "Redis", "GraphQL"]
    }
  ],
  "education": [
    {
      "institution": "University of California, Berkeley",
      "area": "Computer Science",
      "studyType": "Bachelor",
      "startDate": "2013-08-01",
      "endDate": "2017-05-15",
      "score": "3.8"
    }
  ]
}

The keywords array inside each skill group maps directly to the technology tags ATS systems search for. List the specific tools and frameworks rather than broad categories.

Complete Example

Here’s a trimmed but realistic JSON resume you can use as a starting template. Paste it into our JSON Formatter to pretty-print it, or validate it against the schema with the JSON Schema Validator.

{
  "basics": {
    "name": "Jane Doe",
    "label": "Full-Stack Developer",
    "email": "jane@example.com",
    "url": "https://janedoe.dev",
    "summary": "Full-stack developer with 6 years of experience building scalable web apps.",
    "location": { "city": "San Francisco", "countryCode": "US" },
    "profiles": [
      { "network": "GitHub", "username": "janedoe", "url": "https://github.com/janedoe" }
    ]
  },
  "work": [
    {
      "name": "Acme Corp",
      "position": "Senior Frontend Engineer",
      "startDate": "2021-03-01",
      "highlights": [
        "Reduced bundle size by 35%",
        "Led design-system team across 12 product teams"
      ]
    },
    {
      "name": "Widgets Inc",
      "position": "Frontend Developer",
      "startDate": "2018-06-01",
      "endDate": "2021-02-28",
      "highlights": [
        "Built real-time dashboard serving 50k daily users",
        "Migrated legacy jQuery codebase to React"
      ]
    }
  ],
  "education": [
    {
      "institution": "UC Berkeley",
      "area": "Computer Science",
      "studyType": "Bachelor",
      "startDate": "2013-08-01",
      "endDate": "2017-05-15"
    }
  ],
  "skills": [
    { "name": "Frontend", "keywords": ["React", "TypeScript", "Next.js"] },
    { "name": "Backend", "keywords": ["Node.js", "PostgreSQL", "GraphQL"] }
  ],
  "projects": [
    {
      "name": "OpenTracker",
      "description": "Open-source time-tracking CLI built with Rust",
      "url": "https://github.com/janedoe/opentracker",
      "keywords": ["Rust", "CLI", "Open Source"]
    }
  ]
}

How to Create Your JSON Resume

Option 1: Write It by Hand

If you prefer full control, create a resume.json file and fill in the sections that apply to you. Use the JSON Formatter to keep it tidy and catch syntax errors.

Option 2: Start From a Polished Resume

If you don’t have an up-to-date resume yet, start by building one with a free tool like Resumeily. It lets you pick a template, fill in your details, and export a clean PDF. Once you have your content organised, converting it to JSON is straightforward — just map each section to the schema fields shown above.

Option 3: Use the CLI

# Install the CLI globally
npm install -g resume-cli

# Create a new resume.json with interactive prompts
resume init

# Validate your resume against the schema
resume validate resume.json

# Export to HTML using a theme
resume export resume.html --theme elegant

The resume-cli tool scaffolds a valid JSON file and can render it into HTML, PDF, or host it as a web page. There are dozens of community-built themes to choose from.

Validating Your JSON Resume

The JSON Resume project publishes an official JSON Schema that you can validate against. Paste your resume into the AllJSONTools JSON Schema Validator along with the official schema URL to catch missing fields, wrong types, or invalid date formats before you publish.

You can also generate a schema from your own resume using the JSON Schema Generator to understand its structure at a glance.

Rendering With Themes

One of the biggest advantages of JSON Resume is the theme ecosystem. Because the data format is standardised, anyone can build a renderer. Popular themes include:

• jsonresume-theme-elegant — Clean, professional single-page layout

• jsonresume-theme-stackoverflow — Inspired by the Stack Overflow developer story

• jsonresume-theme-kendall — Minimal two-column design

• jsonresume-theme-orbit — Modern sidebar layout with skill bars

Switch themes with a single CLI flag — no need to reformat or restructure anything.

Bonus: JSON-LD for Your Resume

If you host your resume on a personal site, you can embed structured data using JSON-LD (Linked Data). Search engines like Google parse JSON-LD to display rich results. Here’s a snippet using the Schema.org Person type:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Doe",
  "jobTitle": "Full-Stack Developer",
  "url": "https://janedoe.dev",
  "sameAs": [
    "https://github.com/janedoe",
    "https://linkedin.com/in/janedoe"
  ],
  "knowsAbout": ["React", "TypeScript", "Node.js", "PostgreSQL"]
}

Place this inside a <script type="application/ld+json"> tag in your page’s <head> to help search engines understand who you are and what you do.

Tips for a Great JSON Resume

1. Use ISO 8601 dates — Always format dates as YYYY-MM-DD. This avoids locale ambiguity and sorts correctly.

2. Quantify achievements — “Reduced load time by 40%” is far more compelling than “Improved performance”. Put numbers in your highlights.

3. Keep it valid — Run your file through a formatter regularly. A single trailing comma will break parsers.

4. Version control it — Store resume.json in a Git repo. Tag each version you send out so you can always trace back what a specific employer received.

5. Trim what you don’t need — The schema has 12 sections but you only need the ones relevant to you. A shorter, focused resume beats an exhaustive one.

Putting It All Together

Here’s a practical workflow for managing your resume as JSON:

1. Draft your resume content using a visual builder like Resumeily to get the wording, layout, and structure right.

2. Convert the content into resume.json following the JSON Resume schema.

3. Validate with the JSON Schema Validator to catch errors.

4. Format with the JSON Formatter for readability.

5. Render using a JSON Resume theme or your own custom template.

6. Commit to Git and tag each version you send to employers.

By treating your resume as structured data, you gain the same advantages developers already apply to code: reproducibility, traceability, and automation. The JSON Resume format turns a painful document-management chore into a streamlined, developer-friendly workflow.