CV vs Resume: What's the Difference?

People use "CV" and "resume" interchangeably, and most of the time it doesn't matter. But sometimes it does. Apply to a US tech company with a four-page academic CV and you'll get filtered out. Apply to a European employer or a PhD program with a one-page resume and you'll look underqualified.

The short version: a resume is a short, targeted summary tailored to one job. A CV (curriculum vitae) is a comprehensive record of your entire professional and academic history. The longer version depends on where you live and what you're applying for.

Definitions

A resume is a concise document, usually one page, that markets you for a specific role. You include only what's relevant to that job. You rewrite it for each application. The goal is to get an interview, not to document everything you've ever done.

A CV is a complete inventory of your academic and professional life: degrees, publications, grants, talks, teaching, awards, references. It grows over time. You don't trim it for each application; you add to it. In academia and research, this is the standard document.

The confusion comes from geography. In the US and Canada, "resume" and "CV" mean two different documents. In the UK, Ireland, and most of Europe, "CV" is the word people use for what Americans call a resume. So a British "CV" and an American "resume" are often the same one-to-two-page document, while an American "CV" is a different beast entirely.

Side-by-side comparison

	Resume	CV
Length	1 page (2 max for senior roles)	2+ pages, no upper limit
Purpose	Pitch for one specific job	Full record of academic/professional history
Tailoring	Rewritten per application	Static, grows over time
Common regions	US, Canada (for industry jobs)	Academia worldwide; standard format in UK/Europe
Detail level	Highlights only, relevant to the role	Comprehensive, exhaustive
Typical sections	Summary, experience, skills, education	Education, publications, research, teaching, grants, talks, service
Photo/personal data	No (US); avoided for bias reasons	Common in parts of Europe; never in US academia

When to use each

Use a resume when you're applying for industry jobs in the US or Canada. Software engineering, product, finance, marketing, design. The reader is a recruiter or hiring manager who spends seconds on each document and wants to know, fast, whether you fit this role. See our software engineer resume example for what that looks like in practice.

Use a CV when you're applying for anything academic: faculty positions, postdocs, research roles, grants, fellowships, or PhD and master's programs. Here the reader is a committee evaluating the full arc of your scholarship. Length signals productivity, not verbosity. A two-page CV from a tenured professor would look thin. Our academic CV template covers the sections that matter and the order to put them in.

The tricky case is the move between worlds. If you're leaving academia for industry, you can't just hand over your 12-page CV. You have to compress it into a one-page resume that translates research output into business value. That's a real skill, and we wrote a full guide on the PhD to industry resume transition.

Regional differences

This is where most of the confusion lives.

United States and Canada. Resume for industry, CV for academia. Two distinct documents. A resume here is one page, no photo, no date of birth, no marital status. Including personal data invites discrimination concerns and marks you as someone unfamiliar with US norms.

United Kingdom, Ireland, Australia, New Zealand. People say "CV" but mean a short, targeted document, functionally a resume. One to two pages. Photos are uncommon and increasingly discouraged. If a UK job ad asks for your "CV," it wants the equivalent of a US resume, not a 10-page academic dossier.

Continental Europe. "CV" is the universal term, and the format varies by country. In Germany (Lebenslauf), France, Spain, and Italy, it's common to include a photo, date of birth, and nationality, though this is slowly changing as anti-discrimination practices spread. The Europass CV is a standardized EU format some employers expect. Length is typically one to three pages.

Academia, everywhere. A CV is a CV. Long, comprehensive, photo-free, organized around publications and research. A physicist in Tokyo, Berlin, and Boston all submit recognizably similar documents.

The practical rule: read the job posting. If it asks for a "CV" and the role is in industry in the UK or Europe, send a short targeted document. If it asks for a "CV" and the role is academic, send the full record.

What sections actually differ

Both documents share a core: name, contact details, education, and experience. The divergence is in everything else.

A resume prioritizes:

• A short summary or objective (optional, increasingly skipped)
• Work experience with quantified achievements, most recent first
• A skills section, often keyword-heavy for screening software
• Education, condensed to degree, institution, and year

A CV adds, and often leads with:

• Publications (journal articles, conference papers, books)
• Research experience and projects
• Teaching experience and courses taught
• Grants, funding, and fellowships
• Conference talks and presentations
• Professional service (peer review, committees, editorial roles)
• References, listed in full

On a resume, you'd never list every conference talk. On a CV, leaving them off looks like you have none.

A note on screening software

One thing both documents now share: most applications pass through automated parsing before a human reads them. For industry resumes especially, that means clean structure, real text (not text baked into an image), and standard section headings. A beautifully designed two-column PDF that a parser can't read is worse than a plain one it can. We cover the specifics in our guide to writing an ATS-friendly resume.

CVs face less aggressive automated filtering, since academic committees tend to read them directly, but the same principle holds: machine-readable text beats clever layout.

One source of truth for both

Here's the part that trips people up: most professionals need both at some point. You keep a full CV for grants or academic applications, and you cut it down to a resume when a company comes calling. Maintaining two separate documents by hand means they drift out of sync.

RenderCV solves this cleanly. Your career data lives in a single YAML file. To produce a dense academic CV, you keep all your sections and pick a CV-oriented theme. To produce a tight one-page resume, you trim the sections and switch themes. Same source data, two different outputs, no copy-pasting between Word templates.

Because the content is structured and version-controlled, you can branch it. Keep a cv.yaml with everything and a resume.yaml that pulls the relevant subset, both rendered through the same engine to identical typographic quality.

Whether you need the one-page pitch or the complete record, build it at rendercv.com. Write once, render either.