Tailoring your CV without lying: a practical method

Recruiters search their applicant tracking system with the job's own vocabulary, then skim what comes back. In the Harvard Business School and Accenture Hidden Workers study, 88% of employers agreed that qualified high-skill candidates were screened out because they didn't match the exact criteria in the job description (HBS). Your experience may fit; the words may not.

Job seekers' own data points the same way. In Huntr's Q2 2026 report, applications sent with a tailored resume had a recorded interview rate of 5.71%, against 3.09% for untailored ones (Huntr). That's an association, not proof: people who tailor may also choose jobs more carefully. But it's consistent with how recruiters search.

Tailoring is not adding skills you don't have, inflating titles, or pasting the ad into your CV. It's choosing which true things to say first, and saying them in the words this employer uses.

Copy the requirements and responsibilities into a note. Ignore the company pitch and the benefits. Then sort each line into one of three buckets:

• Must-have: "required", "you have", "minimum", or anything repeated more than once.
• Nice-to-have: "bonus", "a plus", "preferred", "ideally".
• Context: the team, the product, the scale. Useful for your summary and cover letter, not for keywords.

Write down the exact terms, product names and acronyms: "Terraform", "stakeholder management", "SOC 2", "B2B SaaS". Those are what a recruiter will type into a search box.

For each must-have, find the line on your CV that proves it, or note that there isn't one. A small table is enough:

This table is the whole job. Rows marked "yes, but" need a wording change. "Only in Skills" rows need a bullet. "No" rows with real evidence need a line added. And a "No, and that's accurate" row stays a gap: you'll address it honestly, not hide it.

Now edit only the rows that need it:

• Swap synonyms for their term when they mean the same thing: "build pipelines" becomes "CI/CD pipelines (GitHub Actions)".
• Add the acronym and the long form once: "infrastructure as code (Terraform)".
• Move a skill from the list into a bullet that shows how you used it: "Ran three production EKS clusters (Kubernetes) serving 40 services."
• Add the missing true line: "Mentored three junior engineers through onboarding and their first on-call rotation."

Keep everything else byte-for-byte the same. Bullets that already fit don't need polishing, and a CV that reads like it was written for the ad, line by line, is as off-putting as one that ignores it.

• Within each job, move the most relevant bullet to the top. Recruiters read the first two.
• In Skills, keep your existing groups and order; add a missing skill to the group it belongs in.
• In the summary, adjust one phrase so the first line names the role and the two or three things this job cares about most. Keep the rest.
• Leave the section order alone. Moving Education above Experience for one application creates mistakes and buys nothing.

Small, targeted edits are also easier to keep track of: when a recruiter calls about "the Kubernetes work", you know exactly which version they read.

Take a platform engineer applying for a role whose ad leads with "Kubernetes at scale", "Terraform" and "developer experience". Their current summary:

Infrastructure engineer with 6 years of experience building cloud platforms and automating deployments for product teams.

The tailored version changes one phrase and adds two true specifics:

Platform engineer with 6 years of experience running Kubernetes (EKS) and Terraform-managed AWS platforms, focused on developer experience: self-service deploys for 12 product teams.

What changed: "infrastructure" became "platform" because that's the ad's word and an honest description; the two must-have tools are named; and "developer experience" is backed by a fact already in the CV. What didn't: the years, the claims and the tone. If the original CV didn't mention the 12 teams anywhere, that number wouldn't belong in the summary either.

Apply the same test to every edit: could you point to the bullet, project or reference that proves it? If yes, the wording is fair game. If not, leave it out.

Most job ads are wish lists. Missing one or two must-haves isn't disqualifying, but pretending is. Honest options:

• Adjacent experience: "Used Pulumi (TypeScript) for IaC; reading Terraform modules daily" is true and relevant to a Terraform requirement.
• Recent learning with evidence: a certification, a course project or a public repository, listed as what it is.
• The cover letter: one sentence that names the gap and how you'd close it is more convincing than silence.
• Skip the job when the gap is the core of the role. That's a better use of your time than a long shot.

• Job titles and dates. Never change them. They're the first things background and reference checks confirm.
• Degrees and certifications you haven't completed. "In progress, expected 2027" is fine; "certified" isn't.
• Skills you can't discuss for five minutes. Technical interviews will find them.
• Numbers you can't back up. "Cut costs 40%" invites "how did you measure that?".
• Hidden text or a pasted job ad. It appears in the parsed text recruiters read.
• Turning the job's title into a skill. "Senior Platform Engineer" is not a skill to list; it reads as filler at best.

1. Check the job can hire you where you live: remote eligibility checker (30 seconds).
2. Run your current CV against the ad with the free CV score checker: it lists the keywords you're missing, so step 1 is mostly done for you.
3. Build the requirement-to-evidence table for the must-haves the checker flagged.
4. Edit only the flagged lines, reorder bullets, adjust one summary phrase.
5. Re-check the score, save the file as "Firstname-Lastname-CV-Company.pdf", and note which version you sent.

If you'd rather not do the edits by hand, an account can draft them for you under the same rules: it keeps your section order and skills grouping, leaves bullets that already fit unchanged, only adds keywords your CV gives evidence for, and never invents experience. You review every change before using it.

For role-wide context (which skills most postings in your field mention), see resume keywords by role.