Resume guide

How to tailor a resume to a job description.

Tailoring doesn't mean rewriting. It means adjusting the emphasis of an existing resume so that the strongest evidence for this specific job rises to the surface. Done well, it takes about twenty minutes and noticeably improves your fit in the eyes of a reader (and often an ATS).

By Advoke CV Editorial Team Published: January 2025 Reading time: ~7 minutes

1. Why tailoring matters

Hiring managers read a resume with one question in mind: does this person match the specific job? A resume that lists generic achievements may be impressive but hard to map onto the role. A tailored resume makes that mapping obvious.

Tailoring is not about keyword stuffing. It's about making the strongest relevant evidence easy to find. Two resumes can contain exactly the same facts and have very different effectiveness depending on what's emphasised.

2. The twenty-minute process

Step 1 — Read the job description twice (3 min)

The first read gives you the overall shape of the role. The second read is where you extract what the employer is actually looking for. On the second pass, highlight:

  • Specific technologies or tools named in the posting.
  • Repeated phrases — if "stakeholder communication" appears twice, it matters.
  • Explicit requirements — anything that says "must have" or "required".
  • The role's top three responsibilities — usually the first bullets under "What you'll do".

Step 2 — Identify your 3–5 strongest matches (3 min)

Look at your current resume and pick the 3–5 pieces of evidence that best prove you can do this job. These should be specific — "reduced build times by 40%" beats "experience with performance optimisation". Write them down on a notepad.

Step 3 — Update the summary (3 min)

Rewrite the summary so it leads with your strongest match for this specific role. Don't start from scratch — edit the existing summary to reflect what this job needs.

For example, if the job is "frontend developer with React and accessibility focus", your summary might start with "Frontend developer specialising in React and accessible interfaces." If the same job emphasised design systems, it might start with "Frontend developer with experience building and maintaining design systems in React."

Step 4 — Reorder bullets within roles (5 min)

Within your most recent role, move the bullets most relevant to this job to the top. Don't delete the others — just change their order. The reader will see the most relevant evidence first and may not even reach the bullets that are less relevant to this role.

Step 5 — Adjust the skills section (2 min)

Reorder the skills to match the job description. Ensure the top three to five skills are the ones the posting names (assuming you genuinely have them). If the posting names a skill you have but didn't include, add it.

Step 6 — Update the target role in the summary (1 min)

Make sure the target role mentioned in the summary matches this specific posting. If the posting says "Senior Backend Engineer" and your summary says "Backend Developer", update it.

Step 7 — Proofread and check length (3 min)

Read the whole resume once end to end. Does it read coherently? Are there sections that felt relevant before but don't now? If a section is completely irrelevant to this role and doesn't help you, consider removing it. If removing it would leave a gap or confusion, leave it — but don't let it dominate.

3. About keywords and ATS

Applicant tracking systems often parse resumes and match them against keywords from the job description. Matching keywords can help a resume surface in an ATS shortlist — but only if the resume is honest. There are two legitimate ways to match keywords:

  • Use the exact phrasing where it matches your actual skills. If the job says "React" and you know React, use "React" (not just "frontend frameworks").
  • Use the term once in a natural context — a bullet point is better than a keyword list.

What doesn't help and may hurt:

  • Keyword stuffing — including skills you don't have.
  • Invisible text — hiding keywords in white text or metadata. Modern ATS detect this.
  • Repeating a keyword in every bullet — reads badly to human reviewers and may not improve ATS ranking.

For more detail, see our guide to using relevant keywords naturally.

4. Should you keep one master version?

Yes. Maintain a "master resume" with everything you've ever done — every role, every project, every skill, every achievement. When you tailor for a specific job, you work from the master and select what to include. This is faster than starting from a tailored resume every time.

In the Advoke CV builder, use the JSON export to save your master resume, and create separate exported copies for each tailored version.

5. How often to tailor

Tailoring for every application is ideal but impractical if you're applying to dozens of roles. A useful middle ground: maintain three or four "base versions" of your resume, each tailored to a different type of role you're applying to, and do minor tweaks for each application.

For roles you really want (the ones you'd take in a heartbeat), always tailor fully. For roles you're applying to more speculatively, a base version is usually fine.

6. Final checklist

  • Does the summary lead with the strongest match for this role?
  • Are the most relevant bullets in the most recent role at the top?
  • Does the skills section include the specific tools named in the posting (where you have them)?
  • Does the target role in the summary match the posting's title?
  • Is everything still honest?
  • Did you proofread after making changes?