Tailoring your CV per application: what it actually means

Everyone is told to tailor their CV for each application. Almost nobody is told what to change, so it usually collapses into one of two failure modes: pasting the job title at the top and calling it tailored, or rewriting the whole document each time until the effort makes you stop applying.

The useful version is narrower than the second and much more than the first.

What tailoring is not

It is not keyword stuffing. The folk wisdom says applicant tracking systems reject CVs that don't contain enough matching terms, so you should smuggle in every phrase from the posting. This gets the mechanism wrong. Most ATS software does not auto-reject on keyword density — it stores, sorts and searches applications. A recruiter runs a search, skims results, and reads a shortlist.

Keywords matter because they affect whether you surface in that search, not because a robot is scoring you out of a hundred. And a CV written for a keyword parser reads badly to the person who opens it, which is where the actual decision happens.

It is not a new CV each time. If tailoring takes an hour, you will do it for three applications and then stop. A process you abandon is worse than a lighter one you sustain.

The parts that should change

Think of a CV as having a fixed spine and a variable surface.

The spine is factual: where you worked, when, job titles, education, the technologies you genuinely used. This should never change, for the obvious reason that it's a record of things that happened, and for the practical one that inconsistencies across versions surface in background checks and second interviews.

The surface is editorial: what gets emphasised, what order things appear in, which of your accomplishments make the cut, and how each is phrased. This is what should change, and it's a smaller job than rewriting.

Concretely, four things:

1. The opening summary. The two or three lines at the top are the highest- leverage text in the document, because they're the only part guaranteed to be read. They should describe the person the posting is looking for, if that person is honestly you.

2. Which bullets survive. Most roles you've held produced more accomplishments than fit on a page. Which ones you keep should depend on the role you're applying for. A backend-heavy posting and a platform-heavy posting can pull entirely different bullets from the same job.

3. The vocabulary for the same fact. If you built a system that moved data between services on a schedule, that is "ETL pipelines" on a data posting and "service integration" on a platform posting. Same work, and the posting tells you which framing the reader already has in their head. This is where keyword alignment is legitimate — you're describing real work in the reader's language, not inventing it.

4. Ordering. Putting the most relevant role first within a section, or the most relevant bullet first within a role, costs nothing and changes what someone sees in the six seconds they spend on the first pass.

The parts that must not change

Worth stating explicitly, because tailoring shades into fabrication more easily than people expect:

• Dates, titles and employers.
• Technologies you have not used. Reframing "wrote SQL queries" as "data engineering" is a stretch; adding Kafka because the posting mentions it is a lie you will be asked about in a technical interview.
• Quantified claims. If you don't know the number, don't invent one. "Reduced latency" is weaker than "reduced p99 latency by 40%" and infinitely better than a fabricated 40%.
• Anything you would not be comfortable being asked to expand on for ten minutes. That is the actual test, and it's the one interviews apply.

Making it sustainable

The reason tailoring gets skipped is that it competes with applying to more roles, and volume feels like progress. Two things make it survivable.

Keep a master document. Not a CV — a longer file with every role, every project and every accomplishment, including the ones that never fit on a page. Tailoring then becomes selection from a menu rather than composition from a blank page. This is most of the work, and you do it once.

Be honest about which applications deserve it. If a role is a marginal fit, a tailored CV will not rescue it, and the time is better spent on one you'd actually take. Tailoring is a multiplier on a decent match, not a substitute for one.

This is where automation earns its place. Selecting the relevant bullets and rephrasing them for a specific posting is a bounded, repetitive editorial task with a clear input and a clear output — the kind of thing software does well. Deciding which roles are worth applying to, and checking that the result is true, remain yours. Quarrion drafts the tailored version per role and gives it to you to approve, which is the right split: the machine does the tedious part, and a human signs off on the claims.

A test for whether you've done it

Read the opening summary. If you could paste it onto an application for a different role at a different company without changing a word, you haven't tailored the CV — you've reformatted it.