← All guides

Career

How to Write a CV That Gets You Interviews

A CV has one job: earn you a conversation. Most fail at it before a human ever opens the file — filtered by software, skimmed in seconds, or lost to a paragraph nobody asked for.

Train for the Job editorial team · 8 min read

Key takeaways

  • A CV is a filter, not a biography — every line should argue that you are worth a conversation.
  • Software reads your CV before a person does. Formatting decisions you never think about can decide whether it is even seen.
  • Achievements outperform duties. "Responsible for X" is a job description; "did X, which produced Y" is evidence.
  • One CV tailored to one job beats one CV sent to fifty jobs.

Advertisement

What a CV is for

A CV is not a record of your career. It is an argument for why the next thirty minutes of a stranger's time should be spent talking to you instead of someone else. Once you read it that way, the whole document changes — every line either builds the case or wastes space that could.

Two readers see it, usually in this order. First, software: an applicant tracking system that parses and often ranks your CV before a person opens it. Second, a hiring manager giving it somewhere between six and thirty seconds on the first pass. Neither is reading for nuance. Both want a fast answer to one question — can this person do the job.

The shift that changes everything else

Write it as evidence, not description. A list of what you did is forgettable. A short case for why you are the right hire is not.

Structure for the software and the human

Parsers are less capable than most candidates assume. Multi-column layouts, tables, icons used as bullets, and creative section headers routinely get mangled or dropped — fields go missing, experience gets misread, and none of it is visible to you in the file you submitted.

  • Single column, always. Two- and three-column CVs look modern and parse badly — readers go line by line and can interleave unrelated sections.
  • Standard headings: Experience, Education, Skills. Anything cleverer gets missed.
  • Reverse-chronological order, most recent first — the default for a reason.
  • PDF unless a Word document is specifically requested. PDFs hold formatting; modern parsers handle them fine.
  • No skill bars, star ratings, or icons standing in for words. None of it is machine-readable, and none of it is convincing.

None of this flattens the design. Clean type, real hierarchy, and generous white space read as more senior than a dense, decorated page — and they parse better. Good CV design and machine-readable design are, almost always, the same thing.

Achievements, not duties

This single shift separates the CVs that get read from the ones that get skimmed past. Weak CVs list what the job involved. Strong CVs list what changed because a specific person held it.

Anyone can describe their job title. A hiring manager wants to know what happened because you were the one in the seat.
  • Weak: "Responsible for managing social media accounts."
  • Strong: "Grew Instagram from 4,000 to 22,000 followers in 8 months by shifting the posting strategy toward short-form video."
  • Weak: "Handled customer complaints."
  • Strong: "Cut average resolution time from 3 days to 6 hours by restructuring the escalation process."

The pattern: verb, action, result. A number sharpens it but is not mandatory — if you do not have one, describe the concrete outcome instead of retreating to a duty statement. What is mandatory: never invent the number. An interviewer's first follow-up question will expose it, and the interview ends there.

Tailor every line to the posting

One CV sent to every job is the most common reason strong candidates get filtered out early. Tailoring does two things at once: it improves your keyword match for the parser, and it shows a human reader a document written for this role, not recycled from the last one.

  • Mirror the posting's language. If they say "stakeholder management," use that phrase, somewhere it is genuinely true.
  • Reorder bullets within each role so the most relevant achievements sit at the top.
  • Cut what has no bearing on this role. Relevance beats completeness.
  • Rewrite the summary line for each application, naming the target role directly.

Fifteen extra minutes per application. Consistently the highest-return fifteen minutes in the entire process.

The summary: three lines, no adjectives

At the top, under your name, write two or three lines: who you are professionally, and the strongest evidence you are good at it. Skip "hardworking" and "team player" — every CV a recruiter reads that day claims the same thing, and a claim without evidence reads as filler.

Two sentences, done well

"Marketing coordinator with 3 years in B2B SaaS, focused on lifecycle email and content. Grew a newsletter from 1,200 to 9,000 subscribers and cut churn 15% through a redesigned onboarding sequence." A claim, backed by evidence, in two sentences.

What quietly kills applications

  • An objective statement instead of a summary. "Seeking a challenging role where I can grow" describes what you want, not what you offer. Flip it.
  • Unexplained gaps. One line — "career break for family relocation," "freelance consulting during this period" — closes the question before it opens.
  • Inconsistent formatting: mixed date styles, shifting fonts, uneven bullets. It reads as carelessness before a single word is read.
  • Length mismatched to experience. Padding an early-career CV to two pages reads as thin content stretched thin — cut instead.
  • A dated, unprofessional email address. Five minutes to fix; it costs interviews when ignored.
  • No proofreading. One typo will not sink a strong application on its own, but it undercuts the "attention to detail" nearly every posting quietly requires.

Before you send it

  1. Every bullet describes an outcome, not a task.
  2. The summary and bullet order are tailored to this specific job.
  3. The language mirrors key phrases from the posting.
  4. Layout is single-column with standard headings.
  5. Read aloud once, slowly — catches what a spellchecker misses.
  6. File named clearly: "FirstName-LastName-CV.pdf," not "Document3-final-v2.pdf."

Advertisement

Frequently asked questions

Should my CV be one page or two?

One page under roughly 5-7 years of experience; two is acceptable, often expected, beyond that. Length matters far less than whether every line earns its place — a tight one-pager beats a padded two-pager at any stage.

Do I need a photo on my CV?

Depends on the market. In the US, UK, Canada, and Ireland, it is uncommon and can work against you under bias-avoidance hiring practices. In parts of continental Europe it is standard. When unsure, check local convention and leave it off — it rarely decides anything either way.

What's the difference between a CV and a resume?

In the US and Canada, "resume" is the standard one-to-two-page application document, while "CV" refers to a longer academic document used for research or teaching roles. In the UK, Ireland, and most of Europe, "CV" is simply the everyday word for what Americans call a resume.

Should I list references on my CV?

"References available on request" is outdated — cut it. Employers assume you can provide references if asked. List actual contacts only if a posting specifically requests them upfront.

A strong CV gets you in the door. Most employers screen what happens next with a cognitive or personality test — practice free before yours.

Practice a free assessment