How to tailor your CV to a specific role without starting from scratch

"Tailor your CV to the role" is standard advice that rarely comes with specifics. It doesn't mean writing a new CV for every application. It means knowing which handful of lines actually need to change, and changing them properly instead of just swapping in a few keywords.

Start with the job description, not your CV

Read the listing and underline the three or four requirements that show up first or repeat. Those are what the screener is actually filtering for. Everything else on your CV stays roughly the same, this pass is about making sure those specific three or four things are unmistakable near the top of the page, not buried in a bullet on page two.

Rewrite the bullet, don't just insert the keyword

If the listing emphasises "cross-functional collaboration" and your CV says "worked with the design team on a new feature", don't just bold the word collaboration. Rewrite the bullet to lead with what you coordinated and the measurable result, "coordinated with design and data science to ship a feature that lifted signup conversion 12%" does the same job of proving collaboration, and it's a stronger sentence regardless of the keyword.

Reorder before you rewrite

A screener spends seconds, not minutes, on a first pass. Before changing any wording, check whether your most relevant experience is actually near the top. Moving a project from the bottom of your CV to the top, with no changes to the text at all, is often the single highest-impact edit you can make for a specific application.

Never invent what isn't there

It's tempting to stretch a bullet to match a requirement you don't actually have experience with. Don't. An interviewer who reads "led a team of 6 engineers" will ask about it in the first five minutes, and a CV claim you can't back up in person does far more damage than an honest gap. Tailoring means sharpening what's true, not inventing what isn't.

This is the same principle Antrenor's CV coaching runs on: every suggested rewrite is grounded in what you actually wrote, matched to the specific role and company, nothing invented.