How to tailor your CV to a job description

A tailored CV isn't a different CV. It's the same true history of your work, reordered and reworded so the person reading it can see — at a glance — that you've done the job they're hiring for. This guide walks through how to do that by hand, well enough that you'll never send a generic CV again.

We'll use one principle throughout: evidence before confidence. Every line you add should point at something you actually did. Tailoring is about surfacing the right real evidence, never about inventing a better story.

Start by reading the job description like a checklist

Most people skim a posting for the gist. To tailor well, read it twice with a pen.

On the first pass, mark every requirement — the skills, tools, and outcomes the employer names. On the second pass, separate them into two piles:

• Must-haves — repeated, listed first, or written as "required." These are the bar.
• Nice-to-haves — "bonus," "a plus," "familiarity with." These break ties.

The must-haves decide what belongs at the top of your CV. The nice-to-haves decide what you keep further down and what you can safely cut.

Match your evidence to each requirement

Take each must-have and ask: where in my actual experience did I do this? Write the answer next to it — a specific project, a number, a result. If you can't find real evidence for a hard requirement, that's honest signal about fit, not a gap to paper over. Where the evidence exists but has no line yet — you did the work and never wrote it down — writing a STAR story from it is how you build one.

This mapping is the whole job. A requirement of "owned reporting for a cross-functional team" is answered by "built the weekly revenue dashboard three teams used to plan sprints" — not by adding the word "reporting" to a skills list.

When the evidence exists but sits in a different field entirely — you did the thing, in another industry, under another job title — the mapping still holds, but the translation is harder than anything else on this page. That case has its own guide: tailoring a CV when you're changing careers.

Mirror the posting's language — the exact words

Two things read your CV: a hiring manager in a hurry, and often an applicant-tracking system (ATS) that the recruiter searches by keyword — some systems also sort applications against the requirements the employer set. Both reward using the employer's own terms.

If the posting says "stakeholder management," use "stakeholder management" — not "working with people." If it says "React," don't write "modern JavaScript frameworks." You're not gaming a filter; you're removing the translation step between what they asked for and what you wrote. Only mirror language that's genuinely true of your experience.

Deciding which of the posting's words carry weight — and which are filler you should refuse to carry forward — is a skill of its own, with its own guide: pulling the right keywords from a job posting. Checking whether your finished draft actually mirrors the ones that matter is a separate pass, and it comes near the end of this one.

Lead with what matters for this role

Recruiters spend seconds on the first scan. Put the evidence that answers the top must-haves where it lands first:

1. Reorder your bullet points within each role so the most relevant achievement leads.
2. Rewrite your summary (if you keep one) to name the role and your two strongest, most relevant proof points.
3. Promote the relevant role. If a side project matches better than your day job, give it more space.

Nothing here changes the facts. It changes the order the reader meets them in.

Worked: one posting, carried through to finished bullets

Everything above is a move. Here they are performed once, end to end.

The posting below is a specimen: invented for this guide, assembled from phrasing common to real listings, and belonging to no company. The candidate is invented too, and everything attributed to them is stated here before it is used — nothing in the rewrites appears out of nowhere, because that is the failure mode this whole guide exists to prevent.

Marketing Manager, B2B software. You'll own the content calendar end to end and run our email programme hands-on in HubSpot. Every month you'll report the content channel's pipeline contribution to the leadership team, and you'll hold the agency relationship behind our long-form work. Required: B2B experience and hands-on marketing automation. A plus: event experience, and any exposure to SEO.

The requirement list, in two piles. Must-haves, because they're written as required or sit in the sentences describing the job itself:

• Own the content calendar
• Run the email programme hands-on, in HubSpot — marketing automation
• Report pipeline contribution to leadership, monthly
• Hold the agency relationship
• B2B experience

Nice-to-haves, because they're written as "a plus": events, and SEO.

Notice that automation appears twice — once as a tool ("HubSpot") and once as a way of working ("hands-on"). Repetition is the clearest signal a posting gives you, and here it decides which of the candidate's bullets has to lead.

The specimen candidate. Three years in the marketing team of a B2B analytics company. They planned and published the blog, built and sent the newsletter, sat in the monthly leadership review, were the day-to-day contact for a freelance writer, and helped staff two conference stands. Their CV describes that work the way most CVs describe work — by naming the duty rather than the outcome.

Bullet one — the calendar.

• Before: "Responsible for content across the blog and social channels."
• After: "Owned the content calendar for the blog and newsletter — planning, commissioning and publishing, with everything scheduled a month ahead."

The posting's first must-have is own the content calendar. "Responsible for content" is the same fact in words the employer didn't use, and it never says what owning it involved. Nothing was added here: the planning, the commissioning, the publishing and the schedule are all in the candidate's record above.

Bullet two — the automation.

• Before: "Sent the company newsletter."
• After: "Ran the email programme hands-on in HubSpot — built the segments, wrote the sends, and set up the follow-up sequence that fires after a content download."

This is the bullet that leads, because the posting leaned on automation twice. "Sent the newsletter" is true and answers none of it. The rewrite uses the employer's words — hands-on, HubSpot, email programme — and each one is attached to something the candidate actually did.

Bullet three — the reporting.

• Before: "Attended monthly marketing meetings."
• After: "Reported the content channel's pipeline contribution to the leadership team each month, using the attribution report I set up in HubSpot."

"Attended" is the weakest verb on any CV: it describes a chair, not a contribution. The candidate was in the leadership review and did build the report, so the stronger line is also the more accurate one.

What's left over. The agency requirement is answered by one honest line — "day-to-day contact for our freelance long-form writer" — which is smaller than the posting implies, and is better said plainly than inflated into "managed agency relationships." The events plus earns a trimmed line further down. The SEO plus this candidate simply doesn't have, and the right move is to leave it alone: a nice-to-have you can't evidence costs you a tie-break, while claiming it costs you the interview it wins.

Three rewrites, one plain line, no new facts — and the same history, read in the order this employer reads in.

Quantify wherever you honestly can

"Improved performance" is a claim. "Cut page-load time from 4.2s to 1.1s, lifting signup completion 18%" is evidence. Numbers turn assertions into proof, and proof is what earns the interview.

You don't need perfect analytics. Reasonable, defensible estimates — team size, time saved, volume handled, percentage moved — are far stronger than vague adjectives, and you'll be able to speak to them in the interview because they're real.

Quantifying work that isn't measured in percentages

Both examples above come from work that generates metrics on its own. Most work doesn't. Support, care, operations, administration and teaching produce almost no conversion rates, and readers in those roles are routinely told to "add numbers" by advice that only ever demonstrates itself on a growth team.

The four quantities nearly every job has are volume, frequency, coverage and time. Each of these is an ordinary duty made specific with one of them:

• Before: "Handled customer enquiries." After: "Handled around forty tickets a day across email and live chat, as the only agent covering the early shift." — volume and coverage, neither of which needed an analytics tool to know.
• Before: "Responsible for the staff rota." After: "Built the weekly rota for a team of eighteen across three sites, including holiday and sickness cover." — scope, stated at a size a stranger can picture.
• Before: "Improved the invoicing process." After: "Cut invoice turnaround from ten working days to three by moving approvals out of email." — time saved, which is the strongest number most back-office roles will ever have.
• Before: "Trained new staff." After: "Trained every new starter on the team — nine in my last year — and wrote the induction checklist that replaced shadowing." — people, frequency, and an artefact that outlasted you.

Count once and count conservatively: the figure has to survive being asked about, and an "around forty" you can stand behind is worth more than a precise number reconstructed to look good. And there is no percentage coming at the end of this section — we have no defensible figure for what quantified bullets do to an interview rate, so we aren't going to quote one.

What tailoring never changes

Everything above moves, rewrites, promotes and de-emphasises. Some things do none of those, and they are worth naming before the next section starts talking about cutting:

• Employers and job titles stay as they were. A title that undersells you is still the title; clarify it in the line underneath — "Coordinator — in practice the team's project lead" — rather than replacing it.
• Dates stay, at one precision throughout. If most of your history carries months, the entry you're least keen on carries months too. Selective vagueness is the most visible thing on a page.
• The chronology stays unbroken. Trimming a role to a single line is tailoring; deleting the entry is not. The time it occupied doesn't leave with it, and the gap left behind asks a louder question than the irrelevant job ever would have.
• The scope of what you did stays fixed. Reordering evidence is tailoring; promoting yourself from contributor to owner is a different thing, with a different name.

Tailoring changes emphasis, order and wording. It doesn't change the record.

Cut what doesn't serve this application

This section carries the principle only — that tailoring is subtraction as much as addition. The decision rules, including how to judge a borderline line and how short a CV should end up, live in what to cut from your CV.

Tailoring is as much subtraction as addition. A decade-old role unrelated to the job, a skills section listing every tool you've touched, a paragraph the posting gives no reason to care about — each one dilutes the first scan. Keep what proves you fit this role; trim the rest to a line or drop it.

Check your draft against the requirement list

You now have a tailored draft and the requirement list you started from. Reading the draft on its own tells you nothing — it will read well, because you just wrote it. Read the two against each other instead, in this order:

1. Go requirement by requirement, not bullet by bullet. Take the must-haves in the order the posting listed them, find the line in your draft that answers each one, and mark both. Working from your CV instead means grading what you wrote rather than what they asked for.
2. Mark each requirement answered, partly answered, or unanswered. "Partly" is the useful category: the evidence exists, but it sits three bullets down inside a role, or it's implied by a duty instead of shown as an outcome. Those are edits, not gaps.
3. Note where their word doesn't appear in yours. For every answered requirement, check whether the employer's own term is in the sentence. If they wrote "incident response" and your line says "handled outages," the evidence is there and the word isn't — and a reader scanning for their phrase has to do the translation you were supposed to do for them.
4. Look at the unanswered ones last, and together. One unanswered nice-to-have is nothing. A run of unanswered must-haves is the posting telling you something, and no rewrite fixes it.

Run the same pass over the nice-to-haves only once the must-haves are clean. Their whole purpose is to break ties, and a tie you weren't in doesn't get broken.

A quick before-you-send checklist

• Every must-have from the posting is answered somewhere your evidence is visible.
• The employer's key terms appear in your words, truthfully.
• Your strongest, most relevant proof leads — not your most recent by default.
• Claims are quantified where you can stand behind the numbers.
• Nothing on the page is there out of habit rather than relevance.
• No cut left a gap behind it: every employer, title and date is still where it was.

If the same line on that list keeps failing every time you apply, the failure has a name — see the common CV tailoring mistakes for the six that undo otherwise careful work.

Done properly, the procedure above is one posting, one requirement list, one pass through your own history, and one draft that answers a single employer — and then all of it again, from the top, for the next role. HireReady24 exists to make that repetition survivable: it reads each posting, maps the requirements onto the history you've already given it, and hands you a draft to accept, edit, or throw out. What it can't do is the part this guide is really about. It cannot find evidence you don't have — where your record is silent the draft is silent too, and no phrasing changes that. And it cannot tell you whether to apply: when the must-haves genuinely aren't answered, that is a decision, and it stays with the person whose history it is.