Tailoring a CV: what actually changes
from one application to the next

Note: we use "CV" and "resume" interchangeably here. Same document, different name depending on where you are (resume in the US, CV in the UK and most of Europe).

"Tailor your CV for each job" is the single most-repeated piece of job-search advice. It's also the one most candidates either ignore (and apply with a generic CV) or overdo (and rewrite their whole history from scratch, producing slightly different lies for each application). The practical middle (what actually changes when tailoring is done well) rarely gets explained concretely.

So here it is. What moves when you tailor, what doesn't, and what a real before-and-after looks like when you're applying to two different versions of a nominally-similar role.

What tailoring is not

Let's clear the misconceptions first, because they drive most of the bad tailoring.

Tailoring is not rewriting your job history. Your experience is what it is. Tailoring doesn't change the facts; it changes which facts are prominent.

Tailoring is not keyword-stuffing. Dumping every keyword from the JD into your resume fails ATS semantic matching and reads as desperate to humans. The keywords you include should match what you actually did.

Tailoring is not writing a different resume from scratch each time. You already know your work. Tailoring produces a per-application emphasis of it, not a new version built from zero.

Tailoring is not lying. Moving a bullet up, dropping a bullet that doesn't fit, rephrasing an achievement in language the target role would recognize: these are framing. Claiming you did something you didn't is different. Don't.

What tailoring is: the practice of producing a version of your CV that emphasizes the experience most relevant to a specific role, in language the recruiter and ATS will pattern-match positively against.

The four things that actually move

Tailoring, done well, touches four layers of the CV. Nothing else.

1. The summary / headline

This is the single most impactful part of a tailored CV, and the part most candidates leave generic.

Generic version:

Senior software engineer with 8 years of experience building scalable web applications across SaaS and fintech companies. Passionate about clean code and mentorship.

That's a summary of a person. It's not a pitch for a specific role. It pattern-matches against nothing.

Tailored for an infrastructure role at a B2B company:

Senior engineer with 8 years shipping backend infrastructure at SaaS companies. Led the migration of Acme's billing service from monolith to event-driven architecture (40M daily writes). Most comfortable in the systems-design layer; weakest at frontend.

Tailored for a product-engineering role at a consumer company:

Senior engineer with 8 years shipping end-to-end product features, including the checkout redesign that lifted conversion by 14%. Comfortable owning work from PRD to production across frontend and backend.

Same person. Same eight years. The summary changes because the role being pitched is different. The infrastructure role sees the infrastructure summary; the consumer role sees the product one.

2. The order of bullets within each role

Every role in your history has multiple bullets. You don't delete them when tailoring: you reorder them, so the most relevant ones appear first.

If you worked at a previous company and did five things (shipped a feature, improved observability, mentored juniors, ran an RFC process, led a migration), and you're applying for an infrastructure role, the reorder puts migration → observability → RFC process at the top. For a product role, it's shipping the feature → mentorship → RFC process first. The bullets about the work that matters to the target role rise to the visible portion of the resume: the first few lines a recruiter's eye actually scans.

The principle: recruiters scan the top of each section, not the bottom. Moving your most relevant bullets up is not a cosmetic choice: it's what determines whether the relevant experience even gets read in the six-second scan.

3. The weight of each role

Sometimes (not always) the amount you say about each role changes per application.

If you're applying for a PM role and one of your past roles was very PM-adjacent, that role gets four bullets when applying for PM positions and two when applying for engineering positions. Space is zero-sum on a one- or two-page CV. Give more of the page to the roles that map onto what's being asked for.

Be careful here: you cannot shrink your most recent role to a stub just because it's off-target. Recruiters expect the most recent role to have the most detail. What you can do is shift which bullets of the recent role you include.

4. The skills section

The skills section is where ATS matching lives. A thoughtful tailor reviews which skills from the JD appear in your experience and makes sure they're listed explicitly.

Some skills you'll have and not have bothered listing (you know Redis because you've used it for three years, but it wasn't on your CV because you didn't think of it as a differentiator). Others you'll have mentioned but not in the same terminology the JD uses ("CI/CD pipelines" on your resume vs "build automation" in the JD, both are you, both matter).

Tailoring the skills section per application ensures the JD's vocabulary is reflected in yours, without fabricating anything. If a skill is in the JD but you don't have it, leave it off. Don't list skills you can't demonstrate.

A complete before-and-after

Imagine a senior PM applying to two different jobs.

Role A: Senior PM at a developer-tools company, owning the API gateway product. Role B: Senior PM at a consumer subscription company, owning the onboarding funnel.

The same underlying career (same person, same facts) has the following elements (abbreviated):

• Summary: 6 years PM, B2B SaaS, led pricing + onboarding + infra platform roadmaps.
• Current role (Acme, 3y): pricing redesign, onboarding funnel redesign, infra API versioning project, team lead for two junior PMs.
• Previous role (Widget Co, 2y): launched B2C mobile feature, ran user research, improved activation rate.
• Skills: product discovery, pricing, roadmap, SQL, Figma, user interviews, A/B testing, Segment.

Now watch what changes per role.

Tailored for Role A (dev tools, API gateway)

• Summary: "Senior PM with 6 years shipping B2B SaaS products, including an API versioning project that migrated 200+ enterprise customers across a breaking change with zero regressions."
• Acme bullets, reordered: infra API versioning → pricing redesign → team lead → onboarding redesign.
• Widget Co weight: reduced to 2 bullets (less relevant).
• Skills listed first: API design, product discovery, roadmap, technical-spec writing, SQL.

Tailored for Role B (consumer subscription onboarding)

• Summary: "Senior PM with 6 years shipping product, including the onboarding funnel redesign that lifted Acme's D7 activation from 31% to 44%."
• Acme bullets, reordered: onboarding redesign → pricing redesign → team lead → infra API versioning.
• Widget Co weight: expanded to 3 bullets with focus on the B2C mobile feature and user research.
• Skills listed first: product discovery, A/B testing, Figma, user interviews, Segment, SQL.

Same career. Same truth. Two documents that each read as "this person's last six years led to exactly the role they're applying for."

That's what tailoring produces. Not a different truth, a different angle on the same truth.

How long tailoring should take

Here's the tension: real tailoring is cognitively expensive. Reading the JD carefully, deciding what's relevant, rewriting the summary, reordering the bullets, adjusting the skills: it's easily 20–40 minutes done manually.

If you're applying to 30 roles a week, 30 × 30 minutes is 15 hours of pure tailoring, on top of researching companies, writing cover letters, and living your actual life. Nobody sustains this. Which is why most "tailored" applications are actually generic applications with two words swapped. Recruiters notice.

The way to sustain tailoring at volume is to make the mechanical part (formatting, bullet reordering, skills re-listing) cheap, so the minutes you do spend go into the parts that actually require human judgment: the summary rewrite, the one or two specific claims that map your history onto their specific problem. Those are the parts that matter. Everything else is reformatting, which is not a good use of your time to do by hand. For the upstream habit that keeps the raw material worth tailoring from, see keeping your CV current.

What to tailor vs what to leave

Not everything should be tailored. Some parts of the CV are stable across applications.

Tailor: summary/headline, bullet order within recent roles, skills list, optional sections (certifications, projects, publications if they're relevant to the role).

Don't tailor: education details, dates, job titles (unless you have a genuine variant, "Senior Engineer / Tech Lead" is fine, inventing a title isn't), number of roles, total years of experience.

The litmus test: if you're changing something that a reference check would contradict, stop. You've crossed from tailoring to fabrication, and the downstream risk is not worth the upside.

The closing thought

Tailoring has a bad reputation because most of what gets called tailoring is either lazy (keyword-stuff) or panicked (rewriting from scratch every time). Neither produces the outcome the advice is pointing at.

Real tailoring is quiet. The summary shifts by thirty words. Three bullets move up. The skills list reorders. The document is 95% the same as the last one you sent and reads as 40% more relevant because the 5% that changed was the 5% the recruiter's eye lands on.

Done at volume, tailoring is a formatting problem, not a writing problem. Done once, it's writing. Both are worth doing. Neither is rewriting your life story for every job.

If the 20-minute tailoring pass per role is what you can't sustain at volume, Jobiz absorbs the mechanical part, so the minutes you do spend go into the sentences that actually require your judgment.