惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
W
WeLiveSecurity
Recorded Future
Recorded Future
P
Privacy & Cybersecurity Law Blog
V
Vulnerabilities – Threatpost
C
Cybersecurity and Infrastructure Security Agency CISA
G
GRAHAM CLULEY
S
Securelist
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
小众软件
小众软件
The Hacker News
The Hacker News
The Cloudflare Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
V
V2EX
C
Cisco Blogs
Cisco Talos Blog
Cisco Talos Blog
腾讯CDC
Recent Announcements
Recent Announcements
Jina AI
Jina AI
K
Kaspersky official blog
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
酷 壳 – CoolShell
酷 壳 – CoolShell
GbyAI
GbyAI
F
Fortinet All Blogs
T
ThreatConnect
S
Schneier on Security
罗磊的独立博客
Y
Y Combinator Blog
C
Check Point Blog
T
The Exploit Database - CXSecurity.com
宝玉的分享
宝玉的分享
aimingoo的专栏
aimingoo的专栏
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
I
Intezer
F
Full Disclosure
T
Troy Hunt's Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
WordPress大学
WordPress大学
Application and Cybersecurity Blog
Application and Cybersecurity Blog
V
V2EX - 技术
C
Comments on: Blog
T
Tenable Blog
Project Zero
Project Zero
H
Help Net Security
A
Arctic Wolf
Google DeepMind News
Google DeepMind News
NISL@THU
NISL@THU
博客园 - 【当耐特】
F
Fox-IT International blog

DEV Community

Building an MCP server so Claude can query my SaaS analytics directly Google I/O 2026 and the Rise of the AI Ecosystem How do you verify GitHub contributions without trusting self-reported skills? student Devs: Build AI Agents & Compete for $55K in Prizes 🚀 How to Write a Cover Letter That Actually Gets You Interviews Battle-Tested: What Getting Hacked Taught Me About Web & Cyber Security Unda folders za kuandika code >> mkdir src >> cd src >> mkdir controllers database routes services utils >> cd .. Directory: C:\Users\mwaki\microfinance-system Mode LastWriteTime Length Name Code Coverage .NET AI slop debt" is technical debt on fast forward. Nobody's ready. Multi-Head Latent Attention (MLA) Memoria - A Local AI Reading Companion Powered by Gemma 4 Stop Trusting Your Accuracy Score: A Practical Guide to Evaluating Logistic Regression Models Serious Question: Is the Developer Job Actually in Risk Due to AI? published: true tags: #discuss #career #ai #help rav2d: We ported an AV2 video decoder from C to Rust — here's why Your New Domain's First Week of GA4 Is a Lie: 4 Days of Raw Data from a Launch Gemma Guide - Real-Time Spatial Awareness for Blind Users From YAML to AI Agents: Building Smarter DevOps Pipelines with MCP A Field Guide to Human–AI Relations (For the Newly Bewildered Mortal) The AI Agent That Learns While It Works — A Complete Guide to Hermes Agent Inviting collaborators to work on ArchScope ArchScope is an interactive web-based tool that lets you design, visualize, and test system architectures with real-time performance simulations. Github - ArchScope is an interactive web-based tool that lets you Gemma 4: Google's Open-Weight AI Is a Game Changer for Developers Confessions of a Git Beginner: Why the Terminal Stopped Scaring Me Docker 容器化实战:从零到生产部署 🚀 I Built a Full Stack Miro Clone with Real-Time Collaboration using Next.js Building an African Economic Data Pipeline with Python, DuckDB & World Bank API llms.txt vs robots.txt vs ai.txt: The Developer's Cheat Sheet Intigriti Challenge 0526 Writeup Business Logic Flaws: How Attackers Skip Steps in Your App to Get What They Should Never Have Why Vibe Coders Need Boilerplates to Save Time, Tokens, and Build More Secure SaaS Projects Idle Cloud Cost Is the New Egress Cost Quark's Outlines: Python Traceback Objects Ghost in the Stack (Part 1): Why uninitialized variables remember old data Building a High-Performance Local Chess Assistant Extension with WebAssembly Stockfish and Manifest V3 Breaking the Trade-off Between Self-Custody and Intelligent Automation on the Stellar Network I Open-Sourced a Practical Fullstack Interview Preparation Repository (React + Node + System Design) 🚀 How I Started Coding as a Student (Beginner-Friendly Guide) WordPress vs. Ghost: Why Automated Bot Attacks Are Making us think much I tested 4 AI agent-governance tools against an open spec - here's the matrix zkML Inference Proof: What the Receipt Proves, and What the Model Still Does Not I Scored 1000/1000 on AWS Certified AI Practitioner (AIF-C01) Here's Every Resource I Used Go - Struct and Interface Handling JSON Requests in Go Storing Kamal secrets in AWS Secrets Manager and deploying to a cheap Hetzner VPS How I Caught and Fixed an N+1 Query in My Django REST API I got tired of paying $10/month to remove image backgrounds – so I built it for free How to Start Coding as a Student: A Complete Beginner’s Guide 🚀 Storing Kamal secrets in AWS Secrets Manager and deploying to a cheap Hetzner VPS What Are Buffers? Build AI Agents with Hot Dev The Client Onboarding Checklist That Prevents 90% of Project Problems Scalable Treasure Hunts Are a Myth, But We Almost Made One Gemini 3.5 Flash Has a 1M Token Context Window. Here's What You Can Actually Build With It. I built a ultra-polished developer portfolio template using React & Tailwind v4 (with zero-JSX configuration) Gemini CLI Is Dead. Here's the Better Thing That Replaced It Post-quantum cryptography for embedded and IoT: secure boot, TLS and OTA Understanding Optimistic Preloading in Modern Applications Nobody Wants to Read Your Code (And You Don't Want to Read Theirs) A clothing pairing app E2B vs E4B vs 31B Dense: The Practical Guide to Choosing the Right Gemma 4 Model I built an AI app store screenshot generator because Figma made me cry — looking for brutal feedback Hello DEV Community — My Developer Journey Begins Adaptable apps on ChromeOS: a post-mortem The WordPress Paradox: Why It’s Here to Stay (and How to Stop Ruining It) I built a local voice AI that can change to 9 different personalities! UXRay: I Built an AI That Roasts Your UI Like a Senior Designer Would Wyrly DI: Type-safe Dependency Injection for Modern TypeScript The contract is the interface: agent-driven Steampipe Stave in one command Gemma 4's Hidden Superpower: Why Built-in Thinking Tokens Change Everything for Evaluation Tasks ⚡ WordPress Performance: The Real Truth They Don't Tell You A Mobile App Usually Needs an Admin System First Customer Portals Should Remove Repeated Admin Work Episode 4: The Time Loop (Layers & Caching) I Built ContextForge with Gemma 4: A Project Memory Generator for Developers and AI Coding Agents Why shadow DOM beat iframe for inline tooltips HOW TO CREATE USER AND ASSIGN ROLES IN AZURE WITH ENTRA ID When AI Blackmail Goes Viral Episode 3: The Secret Scroll (The Dockerfile) Monte Carlo Simulation for Engineers: Turning Uncertainty Into Numbers The tokens-per-byte trap: character-level 'compression' adds tokens Nobody Reads Your Code Anymore Why I built a collection of 5 free, zero-signup career finance tools for solo builders 🚀 New React Challenge: Instant UI with useOptimistic Resolvendo a Alucinação da IA na Arquitetura de Software com Code Property Graphs e .NET 9 S1 — Clean Backtrace Crashes: How to Diagnose and Fix Them Cómo solucionar el bucle infinito en useEffect con objetos y arrays The Brutal Reality of Running Gemma 4 Locally I made Claude Code refuse to write code unless the ticket scores 80/100 I Fed React's Entire Hooks Transition History to Gemma 4. Here's What It Found That We Missed. Building a Private RAG System: Lessons from a Local-First AI Journal CodePulse AI — Reviving an AI-Powered Repository Intelligence Platform How to Split Video into Segments with FFmpeg (CLI + API) I've audited dozens of estate agency websites. The same 5 problems show up every single time. Part 1: Taming Asynchronous JavaScript: How to Build a "Mailbox" Queue Building My AI-Powered VS Code Extension 🚀 Google Login in Express with PassportJS & JWT Great example of Gemma 4 moving beyond chatbots into real-world decision support. Using AI to guide everyday actions like recycling shows how impactful applied LLMs can be when designed for usability, not just capability. #Gemma4 #AI #Sustainability Building a Production AI Chatbot for an Educational Institute: Architecture, Lessons & Full Stack Deep-Dive Google Login in Express with PassportJS & JWT How I reclaimed 47GB on my MacBook by cleaning developer project junk Operators Are Not Oracles: How We Learned to Stop Worrying and Love the Configuration
CV vs Resume: What's the Difference and Which Do You Need?
John · 2026-05-23 · via DEV Community

CV or resume? It seems like it should be a simple question. It's not — at least not without knowing where you're applying, what industry you're in, and what the person reading your document is expecting.

The confusion is compounded by the fact that the terms are used interchangeably in everyday conversation, even by hiring managers who should know better. Send the wrong document and you'll either hand a recruiter forty pages they never asked for, or walk into an academic job search with a one-page summary that tells the hiring committee almost nothing.

This guide cuts through the terminology and tells you exactly what each document is, when to use each one, and how the geography of job searching changes the calculus entirely.


The Core Difference: Purpose and Length

Let's start with definitions that actually hold up.

A resume is a brief, targeted document — typically one to two pages — summarizing your most relevant professional experience, skills, and achievements for a specific role. It's selective by design. You don't include everything; you include the most relevant things. The goal is to make an immediate impression on a recruiter who's spending seconds on an initial scan.

A CV (curriculum vitae, Latin for "course of life") is a comprehensive document that records your complete professional, academic, and intellectual history. It grows as you accumulate experience, publications, presentations, grants, certifications, affiliations, and accomplishments. There is no length limit — a senior academic's CV might run fifteen to thirty pages, and that length is appropriate and expected.

The fundamental difference is not just length. It's philosophy. A resume is a curated marketing document. A CV is a comprehensive record. Both have legitimate uses; they just serve different purposes for different audiences.


CV vs Resume: Side-by-Side Comparison

CV Resume
Length No limit — grows over career (2 to 30+ pages) 1–2 pages, hard cap
Purpose Complete professional and academic record Targeted pitch for a specific role
When to update Every time you add a credential, publication, or role Each time you apply — tailored per job
Customization Minimal — it's a record, not a pitch High — must be tailored to the job description
Common in Academia, research, medicine; UK/Australia/NZ for commercial roles US, Canada commercial roles; increasingly global
Key sections Education, publications, grants, teaching, conferences, affiliations Work experience, skills, achievements, summary
Typical audience Hiring committees, grant reviewers, academic institutions Recruiters, HR, hiring managers in commercial orgs

The table above reflects the strict definitions. In practice, as the geography section below covers, the term "CV" gets used for what is functionally a resume in many English-speaking markets.


When to Use a Resume

In most commercial job markets — corporate roles, startups, tech companies, marketing agencies, sales organizations, financial services firms, consulting practices — a resume is what's expected. The recruiter has 200 applications in a queue, a six-second initial screen, and no interest in reading your complete educational history.

A resume should be:

  • One to two pages. One page is often sufficient for early-career professionals (under five years of experience). Two pages is appropriate for mid-career professionals. More than two pages for a commercial role is almost always a problem, not a demonstration of experience.

  • Targeted to the role. This is the defining feature of a strong resume. You're not listing everything you've done — you're listing what's most relevant to this specific job posting.

  • Achievement-oriented. Bullets in a resume should describe outcomes and impact, not just responsibilities. "Managed a team" is a responsibility. "Led a team of 7 engineers to deliver a platform migration 3 weeks ahead of schedule, reducing hosting costs by $40K annually" is an achievement.

  • ATS-compatible. If you're applying through an online portal, your resume will likely be parsed by an Applicant Tracking System before a human sees it. This means clean formatting, standard section headers, and language that mirrors the job description.

If you're in the United States, Canada, or the UK applying for non-academic, non-medical, non-research roles, use a resume. Full stop.

NextCV — your premium CV, tailored to every job request


When to Use a CV

There are two main contexts where a CV is the correct document.

Academic, research, and scientific roles. If you're applying for a faculty position, a postdoctoral fellowship, a research grant, or any role within a university or research institution, you need a CV. The academic CV is a complete record of your scholarly work: education, dissertation, publications, conference presentations, grants awarded, teaching experience, committee service, professional affiliations, and more. Academic hiring committees want the full picture, and they'll read it. A one-page resume in this context would be taken as a misunderstanding of the role, the field, or both.

Certain medical and clinical roles. In many countries, medical hiring — especially for hospital positions, fellowships, and specialized clinical roles — uses a CV format rather than a resume. This is particularly true in the UK, Ireland, Australia, and New Zealand, where the term "CV" is used more broadly, and in academic medical centers anywhere.

Non-academic CV users also include: scientists applying for industry research positions (especially in pharma and biotech), professionals applying to EU institutions or some government positions that request a Europass CV or a long-form document, and international applicants following the conventions of their home country.

Freelancers and consultants sometimes use an extended CV format for project-based work where a complete record of engagements and outputs demonstrates breadth and depth — though a well-structured resume or portfolio can often serve this purpose better.


What Employers Actually See

The format debate is real, but hiring managers and recruiters are mostly focused on something simpler: does this document tell me quickly whether this person can do this job?

When you send the wrong document type, you create friction before anyone has read a word. An academic hiring committee receiving a one-page resume will either assume you don't understand academic hiring, or assume your record is thin. A commercial recruiter receiving a twelve-page academic CV will either not read it, or mentally flag you as someone who doesn't understand how corporate hiring works. Neither impression recovers easily.

ATS systems don't care what you call it, but they do care about structure. Most ATS platforms parse both CVs and resumes the same way — extracting text, matching keywords, scoring against job requirements. Where problems arise is formatting: tables, graphics, headers embedded in text boxes, and multi-column layouts confuse parsers. Whether you're submitting a CV or a resume, a clean single-column layout with standard section labels (Work Experience, Education, Skills) will outperform a visually complex document every time.

What hiring managers actually prioritize — once a document clears the ATS — is relevance and clarity. Not whether you called it a CV or a resume. Not whether the formatting is clever. Whether the first fifteen seconds of reading give them a clear answer to: "Is this person qualified for this role, and can I see evidence of it?" Structure and specificity answer that question. Generic descriptions and paragraph-length bullet points do not.

The single biggest formatting mistake in this context is treating your document as a job description listing rather than an evidence file. Recruiters are pattern-matching for impact and fit. Give them the pattern they're looking for.


The Geography Problem

Here's where it gets genuinely confusing: in much of the world, "CV" simply means the document you submit when applying for a job — regardless of length or format. And what that document looks like varies dramatically by country.

United States: The distinction is clearest here. "Resume" is the standard commercial job application document (1–2 pages). "CV" refers to the long-form academic or research document. If an American company says "send us your CV," they almost certainly mean your resume.

United Kingdom, Ireland, Australia, New Zealand: "CV" is the standard term for what Americans call a resume. When a British company posts a job and asks for your CV, they want a 1–2 page targeted document, not your complete academic history. "Resume" is rarely used as a term in these markets, though the documents are functionally equivalent.

Continental Europe: Practice varies by country. Germany has traditionally used a fairly structured CV format with a photo and personal details that would be unusual in an Anglo-American application. France has historically included a photo and date of birth. The Europass CV format, promoted by the EU, is a standardized long-form template used for applications across EU institutions and in some member state public sectors. Increasingly, professional CVs in major European markets are converging toward the cleaner, more targeted Anglo-American format for commercial roles.

Canada: Follows American conventions. Resume for commercial roles; CV for academic and research positions.

Scandinavia: CV is the standard term. Commercial CVs are typically concise (1–2 pages), clean in design, and often include a professional photo and brief personal statement — though the photo convention is less universal than it once was.

The practical implication: before you apply, look at the conventions for the country where the company is based. If you're applying to a UK company, send what they call a CV (which is your resume). If you're applying to a US university for a faculty position, send an academic CV. If you're applying to a German company, check whether their hiring norms include a photo and personal details section.


The Photo Question

Including a photo on your CV or resume is one of the most geographically variable norms in job searching.

Never include a photo if you're applying to US, Canadian, or UK companies for commercial roles. In these markets, photos are explicitly discouraged to reduce unconscious bias in screening. Many applicant tracking systems are designed to strip them. Some recruiters will discard applications with photos on the assumption that the applicant doesn't understand local norms.

Commonly expected in Germany, Austria, Switzerland, parts of Scandinavia, and several other European and Asian markets. If local norms include a photo and you omit it, your application may look incomplete or unfamiliar to the recruiter.

Optional or transitional in France, Spain, and many other markets where the convention is shifting.

When in doubt, check the job posting. Companies with international hiring experience often specify their preferences. LinkedIn also publishes country-specific application guides. And if the company has a careers page with example materials, those are worth reviewing.


Content Differences Beyond Length

Beyond length and the photo question, there are content conventions that differ between resume and CV formats.

Personal details. Academic CVs typically include your institutional affiliation and academic email. Commercial CVs in some countries include date of birth, nationality, or marital status — none of which appear in American or British commercial resumes (and which should not appear: this information is legally protected in many jurisdictions, and including it puts the reviewer in an awkward position).

References. Commercial resumes typically note "references available upon request" or omit the topic entirely. Academic CVs often include actual names and contact information for references, since committees may contact them early in the process.

Objective statement vs. professional summary. Old-style commercial resumes used objective statements ("Seeking a challenging role in marketing"). Modern commercial resumes use professional summaries — a 2–4 sentence statement of who you are professionally and what you bring to the role. Academic CVs typically omit both, since your record speaks for itself.

Publications and presentations. On a commercial resume, these appear only if directly relevant (e.g., industry publications for a thought leadership role). On an academic CV, they get their own sections and are listed comprehensively in standard citation format.

Three steps to a tailored CV


Common Mistakes

Most CV and resume errors fall into a small number of recurring patterns. These are the ones that actually cost people interviews.

1. Sending an academic CV for a commercial role. This happens more often than it should, particularly with candidates transitioning from academia to industry. A twelve-page document listing every conference paper and committee role is not what a tech company's HR manager wants to read. Condense it: lead with transferable skills, highlight industry-relevant achievements, and cut everything that doesn't speak to the commercial role.

2. Not tailoring the document to the job description. A generic resume sent to fifty companies is less effective than five tailored resumes sent to five companies. Every job description contains the keywords the ATS is scanning for and the priorities the hiring manager cares about. Mirror that language. Reorder your bullets to lead with the most relevant experience. This isn't gaming the system — it's communicating clearly.

3. Including outdated or irrelevant experience. The job you had in 2003 that isn't related to anything you're applying for now should not appear on your resume. For most professionals, ten to fifteen years of experience is the relevant window. Earlier roles can be listed as a one-line entry (company, title, dates) or omitted entirely. Every line you include is a line the reader has to process — make sure it's earning its place.

4. Ignoring country-specific conventions. Including a photo on an application to a US company, or omitting one on an application to a German company, signals unfamiliarity with local norms. Same with including date of birth or marital status where they're not expected, or using a two-page academic CV format for a commercial role in a market that expects one page.

5. Including a photo where it's inappropriate. This gets its own entry because the consequences are real. In the US, UK, and Canada, an application photo can trigger unconscious bias and is sometimes used as a reason to disqualify an application outright — not by principled decision, but by the recruiter who assumes the applicant doesn't know the rules. When in doubt, leave it out.

6. Listing responsibilities instead of achievements. "Responsible for managing social media accounts" tells a hiring manager almost nothing. "Grew organic Instagram reach by 340% over eight months through a weekly video series" tells them what you actually did and what it produced. The switch from responsibility to outcome is the single highest-leverage edit you can make to any resume or CV.


Making the Decision

The decision tree is actually fairly simple once you have the context:

Are you applying to an academic, research, or medical role? → CV (long-form, comprehensive).

Are you applying to a commercial role in the US or Canada? → Resume (1–2 pages, targeted).

Are you applying to a commercial role in the UK, Ireland, Australia, or New Zealand? → CV (but in practice, this is a resume — 1–2 pages, targeted — just called a CV locally).

Are you applying in continental Europe? → Check country conventions. For most professional commercial roles, a clean 1–2 page document is appropriate; be attentive to local norms around photos and personal details.

Are you unsure? → A clean, well-formatted, targeted 1–2 page document is the safest default for any commercial role in most English-speaking markets.


One Document, Multiple Versions

The practical reality for most active job seekers is that you need the same information formatted for different contexts. The content of what you've done doesn't change — your job is to understand how to present it appropriately for the market you're applying to and the role you're targeting.

Tools like NextCV are useful precisely here: you maintain a complete profile of your experience, and you generate tailored versions for each application. The underlying content is the same; what changes is the emphasis, the language, and the level of detail that's appropriate for each context.

Whether you call it a CV or a resume, the goal is the same: give the person reading it exactly what they need to make a confident decision about inviting you to interview. The format is just the packaging.


Frequently Asked Questions

What is the difference between a CV and a resume?

A CV (curriculum vitae) is a comprehensive, long-form record of your complete professional and academic history — there's no length limit, and it grows throughout your career. A resume is a short, targeted document (typically 1–2 pages) summarizing your most relevant experience for a specific role. The core difference is philosophy: a CV is a complete record; a resume is a curated pitch.

Is a CV the same as a resume?

In strict usage, no — they serve different purposes and have different lengths. In practice, many countries (particularly the UK, Australia, Ireland, and New Zealand) use the term "CV" to refer to what Americans call a resume: a short, targeted job application document. So the same 1–2 page document might be called a CV in London and a resume in New York, even though they're functionally identical.

Should I use a CV or resume for UK jobs?

Use what UK employers call a CV — which is functionally a resume: 1–2 pages, targeted to the role, achievement-oriented. UK employers asking for a "CV" do not want a long-form academic document. The format is the same as an American resume; only the label differs.

Should I use a CV or resume in the USA?

Use a resume for commercial roles in the US: 1–2 pages, tailored to the specific job posting. In the US, "CV" refers specifically to the long-form academic or research document. If you're applying for a faculty position, fellowship, or research grant at a US institution, then a CV is correct. For everything else — corporate, startup, nonprofit, government — use a resume.

How long should a CV be?

It depends on context. An academic or research CV has no length limit and should include everything relevant to your scholarly record — senior academics commonly have 15–30 page CVs. A commercial CV (what the UK and Australia call the document used for job applications) should be 1–2 pages, the same as an American resume. If someone asks "how long should my CV be" for a job in industry, the answer is almost always: two pages maximum.

Can I use a resume instead of a CV?

Yes, in most commercial job markets. If you're applying to corporate, tech, startup, finance, or any non-academic commercial role — in the US, Canada, UK, Australia, or most of Europe — a well-structured 1–2 page document works regardless of what you call it. The only context where substituting a resume for a CV is genuinely problematic is academic and research hiring, where committees expect the full comprehensive record and will notice its absence.


Ready to put this into practice? Build your job application CV with NextCV →

Related Articles