What to cut from your CV for each role

By The HireReady24 team · Updated 1 September 2026

Almost every CV guide tells you what to add. This one is about what to take away — because tailoring is subtraction as much as addition, and the subtraction is the part people skip. Tailoring a CV to a posting surfaces the evidence that proves you fit; cutting is how you clear everything else out of the way so that evidence lands in the few seconds a recruiter actually gives you.

This guide assumes the mapping is already done: you've read the posting, you know which of its requirements you can evidence, and the matching material is on the page somewhere. That part is the pillar's job. This one is only about what comes out.

A page has a fixed budget of attention. Every line that doesn't earn its place is spending that budget against you. Here's how to decide what goes.

The test: does this line help me win this role?

Run every element of your CV through one question: does this help me win the specific role I'm applying to? Not "is it true," not "am I proud of it" — does it move the reader toward yes for this posting. If the honest answer is no, it's a candidate for the cut. Three outcomes:

Keep — directly answers a requirement in the posting.
Trim — real but marginal; reduce it to a single line.
Cut — no bearing on this role; remove it entirely.

This is judgment, not a formula, and it's meant to be run fresh for each application. What you cut for one job you may keep for the next.

The test, run over one experience block

A three-outcome rule is easy to agree with and hard to apply, so here it is doing real work. The posting is for a customer operations manager; its must-haves are leading a small support team, bringing response times down, owning the helpdesk tooling, and reporting service numbers to leadership. The candidate's most recent role, line by line as it currently stands:

"Managed a support team of six across two time zones." — Keep. The first must-have, answered outright, at a scope someone can check.
"Cut first-response time from two days to four hours by rewriting the triage rules." — Keep. The posting names response times; this line proves them.
"Ran the migration from a shared inbox to a ticketing system, including data import and agent training." — Keep. Stronger evidence of owning the tooling than any list of tool names.
"Presented a monthly service report to the leadership team." — Keep. The fourth must-have, answered in a line. Nothing to add.
"Responsible for day-to-day team operations." — Cut. Names no outcome, and the lines above already prove everything it gestures at.
"Redesigned the onboarding pack for new agents." — Trim. Real, but the posting never raises onboarding; fold it into the training clause above rather than spending a line on it.
"Represented the department at the annual company offsite." — Cut. True, and it moves this reader no closer to yes.

Four kept, one folded in, two gone — and nothing the posting asked for was lost. Neither cut was of weak work: the offsite line went because this posting has no use for it, and against an internal communications role it would be the first line you'd keep.

What almost always earns the cut

Some things dilute nearly every targeted CV:

Ancient, unrelated roles. A ten-year-old job in a different field can shrink to one line — title, employer, dates — or disappear. Recency and relevance both beat completeness.
The everything skills list. Twenty tools listed "for completeness" bury the four that matter. Keep the ones the posting names and that you'd defend; drop the rest.
Generic responsibilities. "Responsible for daily tasks" describes nothing. If a bullet doesn't name an outcome, it's taking space without paying rent.
Obvious or dated fields. "References available on request," a full postal address, a decades-old GPA, "Microsoft Word" as a skill. None of it helps; some of it ages you.
Hobbies with no relevance. Unless an interest genuinely connects to the role or culture, it's filler.

What never gets cut

Subtraction has a floor, and this is the guide that ought to name it. Some things stay on the page even when they prove nothing about this particular role:

The roles themselves. Trim an unrelated position to one line — title, employer, dates — but don't delete it. Removing the entry doesn't remove the time it occupied; it leaves a gap, and a gap asks a louder question than the irrelevant job ever would have.
Dates, at one precision throughout. If the rest of the history carries months, so does the entry you're least keen on. Selective vagueness is the most visible thing on a page.
A qualification the role formally requires — a licence, a registration, a right to work — even when the posting forgot to list it.
Your contact details, and the one link the work actually lives at.

That floor is a convention here and a firm expectation in some other markets, which is worth knowing before you delete an entry — see the note on markets below.

Cut duplicated evidence, keep the strongest instance

If three roles all show "led a team," you don't need the same proof three times. Keep the single strongest, most relevant instance — the one with the best numbers or the closest fit to the posting — and let the others make a different point or shrink. Repetition doesn't reinforce; it just spends your limited space proving the same thing twice.

Trim ruthlessly inside the lines you keep

Cutting isn't only about removing whole sections. Inside the bullets you keep, remove the words that aren't working: throat-clearing openers ("Was tasked with…"), hedges ("helped to assist with"), and adjectives doing a verb's job. "Successfully managed to improve" is three weak words in front of one strong one. Say "improved," attach the number, and stop.

The same move at bullet scale, on a line from the block above:

Before: "Was tasked with successfully managing the improvement of the team's response process, which ultimately resulted in helping to significantly reduce our average first-response time over the course of the year."
After: "Cut first-response time from two days to four hours by rewriting the triage rules."

And at section scale, where most of the space is: three early roles carrying three bullets each become one that keeps its two strongest and two that shrink to a dated line apiece. The history stays intact, but the block that was holding the top of your second page is now four lines, and the role that matters arrives while the reader is still paying attention.

Tight lines read as competence. A reader can feel the difference between someone who edited their CV and someone who emptied their memory onto it.

Cutting for reasons that aren't relevance

Some lines change for reasons that have nothing to do with fit, and guides that only talk about relevance leave you improvising on exactly the cases where improvising is expensive.

A client you can't name. Describe the work and the sector, not the logo — "a listed retail group," "a regional health provider." The outcome is yours to claim; the name was never the evidence.
A project under NDA. Keep the role, the dates and the discipline, and give scale instead of specifics: what kind of system, how large a team, over what period.
An employer you'd rather not be asked about. Keep the entry and the dates; give it one neutral factual line. Deleting it doesn't retire the question — it turns a line the reader would have skimmed into a gap they'll ask about directly.
A role you're deliberately not repeating. Same treatment. Not advertising something is different from pretending it didn't happen, and only one of those survives a reference check.

The rule underneath all four: cut the detail, never the dates.

When you're not sure, ask what its absence costs

The hardest cuts are the borderline ones — a decent achievement that isn't quite on-topic. A useful tie-breaker: imagine the line gone. If the CV is weaker for a requirement the posting actually names, keep it. If the only loss is that you personally liked it, cut it. You are not deleting the accomplishment from your life — only from this application, where it wasn't helping.

This is the same instinct a career-change CV leans on hardest, where whole stretches of true history have to yield space to the parts that transfer.

So how short should it end up?

Length is the question sitting behind "what to cut," and the honest answer is that there's no universal number. You'll see confident ones quoted; most aren't attached to anything you can check, and none of them knows how long you've been working. What the right length depends on is career length, sector, and market.

Markets differ by format, not by taste. A UK or US CV is a persuasive document, and there deleting an unrelated role is at least available to you. A German Lebenslauf is a tabular record with a complete, month-dated history, and a Brazilian currículo expects the chronology intact as well — in both, removing the job isn't one of your options, and shortening means shortening descriptions. If one document has to work across markets, cut to the stricter floor.

And if you've made an honest pass — every remaining line answering something the posting asked for, old roles down to a line each, repeated proof reduced to its strongest instance — and it's still longer than you'd like, then it isn't too long. It's a long career presented honestly, with the strongest material where the reader starts. The failure worth fearing isn't a document that runs over; it's a short one padded back out with everything you just cut.

A subtraction checklist

Every remaining line answers, or supports, a requirement in the posting.
Old and unrelated roles are trimmed to a line or gone.
The skills section lists what's relevant and defensible, not everything you've touched.
No requirement is proven three times where once would do.
Filler fields and empty responsibilities are removed; kept bullets name outcomes.
The chronology is unbroken and dated at one precision — no cut left a gap behind it.
Anything you couldn't name in full is described rather than deleted, with its dates intact.

Subtraction is the harder half of the job. Adding a line only asks you to remember something; cutting one asks you to decide it isn't worth a stranger's attention, and the case for keeping it is always the argument you can hear most clearly. That's why this pass gets skipped, and why it gets skipped hardest on the applications you care about most. HireReady24 reads the posting against your full history and marks which lines earn their place for that role, so what you're reviewing is a proposed cut rather than your own CV and an instruction to be ruthless with it. Nothing leaves your history — a line dropped from one application is still there for the next one.