Common CV tailoring mistakes to avoid

Tailoring a CV well is mostly a matter of avoiding a handful of predictable mistakes. Most people get the idea — match the CV to the role — but then execute it in a way that quietly backfires. This guide names the errors that show up most often when you tailor a CV to a posting, shows each one as a line you can hold your own draft against, and gives a plain fix. If you're wondering whether you're doing this wrong, this is the page to check yourself against.

Mistake 1: keyword stuffing

The most common failure is treating the applicant-tracking system as the whole audience and packing in every term from the posting until the prose reads like spam. Software might pass it; the human who reads next won't.

Before: "Stakeholder management, cross-functional collaboration, agile delivery, roadmap ownership, KPI tracking — delivered agile roadmaps through cross-functional stakeholder collaboration with full KPI ownership."

After: "Owned the payments roadmap: ran the weekly prioritisation call with engineering, support and finance, and published what changed and why after each one."

The second version carries fewer of the posting's words and more of its meaning. Every term left in it is attached to something that happened.

Fix: put keywords inside true sentences that describe what you did. Mirror the employer's language, but only where it's genuinely accurate — a term earns its place by sitting on top of real evidence, not by appearing often. Choosing which terms to mirror in the first place is covered in pulling keywords from a posting.

Mistake 2: cosmetic tailoring

Changing the job title in your summary and calling it tailored. Swapping one line while the other 90% of the CV still argues for a different role. Recruiters read a lot of CVs and spot a find-and-replace job instantly.

Before: "Experienced Marketing Manager seeking a Product Marketing Manager role in a fast-paced environment." — with the bullets underneath unchanged from the last application.

After: "Marketing manager whose last three years have been launches: positioning, sales enablement and first-quarter messaging for four B2B products." — with the launch bullets moved above the campaign-reporting ones.

The test is what happens if you delete the summary. If the CV underneath still argues for the old role, only the label moved.

Fix: tailoring is reordering and reframing throughout — leading with the evidence that answers the top requirements, not editing a single line at the top. If only the header changed, you haven't tailored; you've relabelled.

Mistake 3: dishonest framing

The most damaging mistake, because it's the hardest to recover from. Borrowing a required skill you don't have, inflating a role, implying ownership of work you supported. It may survive the scan, but it collapses in the interview — and a claim that unravels in person costs you far more than an honest gap ever would.

Before: "Led the migration to Kubernetes."

After: "Supported the Kubernetes migration: wrote the rollback runbook and ran the staging cutover rehearsals."

The second line is shorter, more specific, and survives the follow-up question the first one invites.

Fix: every line points at something you actually did. If you can't evidence a hard requirement, that's real signal about fit, not a hole to paper over. Honesty isn't only ethics here; it's the only version that holds up when someone asks a follow-up question.

Where reframing ends and inflating begins

This is the line the whole guide rests on, and it is an easy one to lose. Tailoring requires rewriting your history in the reader's vocabulary — a career-changer who refuses to do that will never be understood. Inflating looks almost identical from the outside and is a different act entirely.

The distinction isn't how far the words travel. It's whether the facts travel with them. A reframe changes the vocabulary; an inflation changes what happened. One workable test: could a colleague who was in the room read the line and recognise it as accurate?

| What happened | How it's written | Verdict | |---|---|---| | You planned lessons for classes with mixed prior knowledge | "Designed and delivered structured programmes for audiences with varied prior knowledge" | Reframing. Every element maps to a real one; only the vocabulary crossed industries. | | You ran a community group's accounts, unpaid, for two years | "Managed the annual budget and reporting for a volunteer organisation" | Reframing — as long as the volunteer context stays visible. Professional language for unpaid work is fair; letting it read as employment is not. | | You were one of four engineers on a migration someone else owned | "Led the migration" | Inflating. It adds a fact — ownership — that didn't occur. "Supported", or the specific piece you did own, is both truer and more interesting. | | You used a tool for a two-week evaluation spike | "Proficient in [tool]" | Inflating. The claim asserts a durability the evidence doesn't have. "Evaluated [tool] in a two-week spike" is honest and still puts the term on the page. |

Read the middle two rows together. The same permission that lets a career-changer describe teaching as programme design is the permission "led" abuses. The difference is that one renames an event and the other invents one.

Mistake 4: over-tailoring into a thin CV

The opposite failure: cutting so aggressively toward one posting that the CV loses the context that makes you credible. A page with three hyper-targeted bullets and no sense of your actual trajectory reads as thin, not focused.

Before: three bullets under one role, every earlier position deleted, nothing on the page before the most recent job.

After: the same three bullets kept in front, earlier roles compressed to a line each — title, employer, dates — so the shape of the career is still legible underneath the argument.

Fix: cut what doesn't serve the role, but keep enough real history to stay believable. Knowing what to cut from your CV is a balance — subtraction in service of clarity, not a race to the shortest possible page.

Mistake 5: ignoring the must-have you can't meet

Seeing a hard requirement you don't satisfy and tailoring around it as if it isn't there. If it's genuinely required, the gap doesn't disappear because you didn't mention it.

Before: "Extensive experience across the modern data stack and its associated tooling."

After: "Built and maintained the analytics warehouse in Snowflake, modelling in SQL and orchestrating in Airflow."

The first line is written to make a missing tool unnoticeable, and a reader who knows the field notices the blur rather than the tool. The second names exactly what you hold and leaves the gap where it actually is — where you can address it directly.

Deciding whether to apply. There's no honest percentage rule here. You'll find one repeated all over the internet, and nobody can tell you where it came from. Use the composition of the gap instead of a score:

1. Write out only the must-haves — the posting's "essential" or "required" list, not the nice-to-haves alongside it.
2. Sort each one into three piles: you hold it, you hold something adjacent to it, or you hold nothing near it.
3. Ask what kind of requirement is sitting in that last pile. A hard credential — a licence, a registration, a specific degree, right to work — is usually a stop, because no framing substitutes for it. A named tool or method with a close cousin in your history usually isn't: "I've done this in Airflow rather than Dagster" is a sentence, not a barrier.
4. Decide on that, and if you apply, say it plainly. Naming the gap yourself and pointing at the adjacent evidence is stronger than hoping nobody checks.

Fix: be honest with yourself about must-haves. If you meet most and can evidence adjacent strengths, apply and address it directly. If the pile with nothing near it holds the credential the job is built on, your effort is better spent on a role you can actually win than on out-tailoring a requirement you don't hold.

Mistake 6: tailoring once and reusing forever

Building one "tailored" CV and sending it to every similar-looking role. Two postings for the same job title can weight their requirements completely differently, and a CV tuned to the first will quietly miss the second.

Before: the version you sent last week, with the company name changed.

After: one underlying fact, derived twice — "Cut checkout drop-off by rebuilding the payment retry flow" for a growth-facing posting, "Rebuilt the payment retry flow across three providers, reducing checkout drop-off" for one that asks about integrations. Same event, different emphasis, nothing invented.

Keep a master, send a derivation. Re-tailoring feels expensive mostly because there's nothing to tailor from. The working method is two documents rather than one:

• The master. One complete, honest record of everything you've done — every role, every date, the full inventory of bullets, including the ones no current posting wants. It is never sent anywhere and never trimmed to fit a job.
• The application. Derived from the master each time: select what answers this posting, order it by what the posting weights first, reword within the truth of what's already there.

The rule that makes this work is that edits only flow one way. New work goes into the master when it happens; a posting never edits it. The moment you start pruning the master to suit one application, it stops being able to serve the next one — and you're back to sending a version tuned for somebody else's job.

Fix: re-read each posting and re-derive from the master. The work gets faster with practice, but it doesn't disappear — each application is its own argument, and it gets one brief hearing.

Check yourself against these six

One question per mistake. Ask them of the draft you're about to send, not of your CV in general.

• Read it aloud: does every term you took from the posting sit inside a sentence that says what you actually did?
• If you deleted your summary, would the rest of the page still argue for this role?
• Could a colleague who was there sign every line as written?
• Can a reader still tell what your career has been about, or only what this posting asked for?
• Have you named to yourself the must-haves you don't hold, and decided rather than avoided?
• Was this version derived from your master for this posting, or is it last week's with a new company name?

Six no's is a rewrite. One no is usually ten minutes.

The pattern behind all six

Every mistake here is a shortcut, and every shortcut buys the same thing: getting the application out sooner. That's why they happen to careful people rather than careless ones — the honest version of tailoring is slow, the deadline isn't, and the six errors above are simply the six cheapest places to save time. HireReady24 is built to take away the time pressure instead of the standard: it reads each posting against your full history and drafts a version that claims only what your record supports, so the quick route and the defensible route stop being different routes. Nothing leaves unread — you see the draft first, and every line in it is one you can be asked about.