How to tailor your CV to a job description (with examples)

Most job seekers send the same CV to every role. That is not laziness — it is habit. But it is also one of the main reasons strong candidates get filtered out before a human ever reads their application. In 2026, with most mid-to-large companies routing applications through Applicant Tracking Systems before they reach a recruiter, a generic CV is structurally disadvantaged. This guide gives you a practical, repeatable framework for tailoring your CV to any job description, with real before-and-after examples so you can see what "tailored" actually means in practice.

Why tailoring matters in 2026

The problem is not that your experience is wrong for the role. The problem is that your CV does not speak the job description's language. ATS software — tools like Greenhouse, Lever, Workday, and iCIMS — parse your CV, extract structured data, and score it against the job requirements. They are looking for keyword overlap. If the job says "stakeholder management" and your CV says "worked with senior leaders," those may describe identical activities but the ATS scores them differently.

The recruiter reality compounds this. When an ATS passes a stack of CVs to a recruiter, they spend an average of six to ten seconds on each document during the first pass. They are scanning for signal. A CV tailored to the role will surface that signal at the top of the page; a generic one buries it under irrelevant experience or uses the wrong vocabulary.

The good news is that tailoring does not mean fabricating. It means translating your real experience into the language of the role you are applying for, and surfacing the parts of your background that are most relevant. The framework below will show you how.

The 6-step tailoring framework

1. Extract the must-have keywords from the JD

Start with the job description itself. Read it twice: once to understand the role, and once to inventory the language. You are looking for three categories of terms.

The first category is hard requirements: qualifications, tools, and technologies the JD explicitly marks as required or that appear three or more times. These are the terms that get you past the ATS filter. If the JD says "Kubernetes" four times, it belongs in your CV if you have touched it at all.

The second category is soft requirements: phrases like "cross-functional collaboration," "data-driven decision making," or "customer-facing communication." These appear in almost every JD, but the exact phrasing varies by company culture. Mirror the phrasing.

The third category is domain vocabulary: industry-specific terms, product names, frameworks, or methodologies that signal you understand the context. A fintech JD will mention things a generic tech JD will not.

Make a short list — fifteen to twenty terms is usually sufficient. Do not try to hit every single phrase; focus on the ones that appear most frequently or are marked as required.

2. Map them to experience you actually have

Go through your keyword list and match each term to a real project or role from your history. Some will map easily. Others will require you to think laterally: you may have done the thing without using the exact word.

This step is important because it is also your honesty check. If a keyword maps to something you did once, briefly, two years ago, you can include it — but honestly. If a keyword maps to something you have never done, you cannot include it. This is where generic AI tools cause the most damage: they confidently fabricate project details, metrics, and responsibilities that do not exist. That is a problem at the interview stage when you cannot answer questions about your own CV.

For each keyword where you have genuine experience, note the specific project or outcome you will use to support it. That note becomes the raw material for step three.

3. Rewrite bullets to surface outcomes in the JD's language

Now rewrite your experience bullets. The goal is not to stuff keywords into existing sentences — it is to reframe accurate descriptions of your work in the vocabulary of the role you are applying for.

A well-formed CV bullet has three components: what you did, how you did it (the method or tool), and what happened as a result (the outcome). The rewrite should keep all three but adjust the vocabulary and prioritise the outcome metrics that the JD cares about.

If the JD is for a product management role and emphasises "OKR alignment," and you have a bullet that says "Managed the Q3 roadmap and shipped four features," rewrite it to something like "Defined Q3 OKRs for the payments team and shipped four features that contributed to a 12% increase in conversion." You have not invented anything. You have made the connection explicit.

Aim to rewrite the five to eight bullets that are most relevant to the role. Do not rewrite every bullet on your CV — the less relevant experience at the bottom does not need to match the JD's vocabulary with the same precision.

4. Re-order experience by relevance, not chronology

A CV is conventionally ordered reverse-chronologically. That is a sensible default, but it can hurt you when your most recent role is less relevant to the target job than an earlier one.

Within each role, order your bullets so the most JD-relevant accomplishments appear first. Recruiters read top to bottom and stop reading well before they reach the end. If your most relevant project is bullet five, move it to bullet one.

At the section level, consider whether to move a skills section, a relevant project section, or a specific role above another. The rule is: surface the most relevant material as early as possible without being dishonest about your career history.

5. Rewrite the summary last

The professional summary or profile statement at the top of your CV is the highest-value real estate on the page. Most people write their summary first and leave it generic — which means it does not reflect the specific tailoring work done in steps one through four.

Write the summary last, after you have done the rest of the tailoring. Use it to front-load the two or three most important things about your candidacy for this specific role. If the JD is looking for a senior backend engineer with distributed systems experience, your summary should say "Senior backend engineer with eight years building distributed systems at scale" — not "Experienced software professional with a passion for technology."

Keep it to three or four sentences. Do not use phrases like "dynamic," "results-driven," or "passionate" — they say nothing and waste the recruiter's six seconds.

6. Verify ATS parseability

Before sending, run a quick ATS check. Copy your CV into a plain-text editor. If the structure holds together in plain text — sections are clearly labelled, dates are readable, job titles are distinct — the ATS will parse it correctly. Common parse failures include tables, text boxes, headers and footers in Word documents, and graphics.

The ATS CV checker can also automate this scan, flagging missing keywords and structural issues against a specific job description.

Before-and-after example

Here is a realistic example. The job description is for a Senior Product Manager at a B2B SaaS company. It mentions: "customer discovery," "PRD ownership," "cross-functional delivery," "OKR definition," and "0-to-1 product experience."

Notice that the "after" bullets contain no invented information. The outcomes — PRDs, 0-to-1 features, 60 customer sessions, six engineers, Fortune 500 accounts — all come from the candidate's real experience. The tailoring work is in the language choice and the emphasis on outcomes that the JD signals it cares about.

Common mistakes

Keyword stuffing. Inserting a keyword into a bullet where it does not belong is easy to spot — and easy to get caught on in an interview. "Leveraged stakeholder management to implement Kubernetes deployment pipelines" is not a coherent sentence. Stick to keywords you can genuinely defend.

Hallucination and exaggeration. This is the AI-specific trap. Generic AI tools, when asked to tailor a CV to a JD, frequently invent project names, inflate metrics, and add experience that does not exist. A CV that says you "increased ARR by 40%" when you cannot remember the actual number will collapse under a single interview question. If a metric you use is approximate, own that — "contributed to a significant increase in trial-to-paid conversion" is honest; a made-up percentage is not.

Tone shift. Different industries and companies have different tones. A startup JD written in casual, direct language expects a CV with a similar register. A government or legal role expects formality. Read the JD for tone and match it. A jarring mismatch between a casual JD and an overly formal CV is a subtle signal to recruiters that the candidate has not read carefully.

Leaving the old summary in place. The most common tailoring mistake is rewriting six bullets and forgetting to update the summary. The summary is what a recruiter reads first. If it says "marketing professional with 10 years of experience" and you are applying for a sales operations role, you have created a mismatch in the first five words.

Doing this in 30 seconds with RecastCV

The framework above works. It also takes between thirty minutes and two hours per application, depending on how different the role is from your recent experience. That is a reasonable investment for a dream role but not sustainable across twenty applications.

RecastCV automates the tailoring work while enforcing the grounding rules: it only rewrites bullets using experience from your master CV and project library, which means every tailored bullet is traceable back to something real. You paste the job description URL, and it produces a tailored CV — including summary rewrite — in under thirty seconds. The ATS CV checker then scores the result against the JD so you can see exactly which keywords are covered and which are missing.

The output is a .docx file you can download, tweak, and send. For high-volume job searching, that speed difference is significant. For a specific dream role, you might still want to run through steps one to six manually — but starting from a RecastCV draft and editing rather than writing from scratch is still faster than starting with a blank page.

The tailoring framework and the tool serve different ends. Use both where they fit. The goal in either case is the same: make sure your CV speaks the job description's language, surfaces your most relevant experience first, and passes the ATS filter before it reaches a recruiter's eyes.

Check out ATS resume format 2026 for the companion guide on formatting your CV so that ATS systems parse it correctly — tailored content inside a broken structure will still fail. And if you want to see how credits-based pricing works, visit the pricing page.