← Guides

Why there's no universal CV format (and what to do about it anyway)

A reasonable question with a disappointing answer

"Why doesn't a universal, machine-readable CV format just exist already?" is a fair question — plenty of serious, well-funded organizations have tried to build one. The disappointing answer: several real standards exist, each solving a real problem, and none of them are read by the Applicant Tracking Systems actually screening the applications you send today. The gap isn't technical. It's an incentive problem: an ATS vendor's proprietary parser is a competitive moat, and there's no commercial reason for any of them to accept a standard schema over their own.

The five families that don't talk to each other

  • JSON Resume — a simple, open, developer-community JSON format. Great for portfolio sites and open-source tooling. Zero adoption by any ATS vendor or Fortune 500 employer — its actual audience is other developers, not recruiters.
  • Schema.org (Person / JobPosting) — structured markup that helps search engines find job postings and profile pages. This is about discoverability, not about handing a structured CV to a hiring system — a job board using JobPosting markup isn't thereby able to parse your CV any better.
  • HR Open Standards / Trusted Career Profile (TCP) — the longest-running attempt (the lineage traces back to 1999), recently relaunched in January 2026 as the Trusted Career Profile with genuinely serious institutional backing — the Gates Foundation, Walmart, and the U.S. Chamber of Commerce Foundation, among others. Real momentum, but as of today, no major ATS vendor has committed to actually reading it.
  • Europass / EDCI — actively maintained by the European Commission, and genuinely important if you're applying for EU civil-service roles, Erasmus+ programs, or cross-border public-sector jobs via EURES. Outside that specific lane, private-sector employers and commercial ATS platforms essentially don't use it.
  • The verifiable-credentials stack (W3C Verifiable Credentials, Open Badges 3.0, Comprehensive Learner Records) — the most technically interesting development, and arguably where real momentum is heading. Instead of a résumé document, this treats your history as a bundle of cryptographically signed, individually verifiable claims — a diploma or certification that can't be faked, rather than a line of text someone has to trust. Still adjacent to, not integrated with, how hiring actually works today.

Worth saying plainly: there is no ISO standard for CVs, and nothing in progress toward one. Any product or service claiming "ISO-compliant CV formatting" is making a claim that doesn't correspond to anything real.

The practical consequence: no format shortcut exists yet

If you're hoping that submitting your CV in some particular "standard" format will let a system read it more completely or more fairly than a well-formatted PDF, that shortcut doesn't exist today. Every ATS-to-HRIS data exchange that actually happens in production uses each vendor's own proprietary schema — not JSON Resume, not Europass XML, not TCP. A structured, standards-based export is a genuinely useful thing to have (as your own durable record, portable between tools, resistant to any one vendor going away) — it just isn't yet a thing any employer's system will read directly.

What this means for how you should actually maintain your CV

Given that no external standard is being read by the systems that matter, the practically useful move is to separate two different jobs that people often conflate:

  1. Keep one complete, structured source of truth for your entire career story — every role, every technology, every detail, in a format that's genuinely yours and portable, independent of any single job application. This is the same principle JSON Resume gets right for developers, just not (yet) something any ATS consumes directly.
  2. Generate a well-formatted, parser-friendly output from that source — a PDF or DOCX tuned to the actual, documented failure modes of real ATS parsing engines (see our guide on how an ATS actually reads your CV), not a format bet on a standard nobody's reading yet.

Treating your CV as a maintained dataset that generates outputs, rather than a single hand-edited document, is the approach that actually matches where the technology is today — not five years from now, once (if) the standards world and the ATS world start talking to each other.

Related guides