Start with evidence, not a score.

Change only what improves relevance or clarity. For a similar role, that may mean reordering a few bullets and adjusting the summary. For a career shift, you may select different projects and substantially change the emphasis. Keep factual identity, dates, credentials, employers and outcomes fixed.

Think in three layers

Fixed factsDo not tailor

Contact details, employers, dates, credentials, job level and verified outcomes.

Selected evidenceTailor most often

Bullets, projects, skills, ordering and the space each experience receives.

FramingTailor carefully

Headline and summary, using language that remains accurate and natural.

Let role distance determine the work

  • Same work, similar setting: run a requirement check; make a few targeted edits.
  • Same function, new industry: surface transferable outcomes and relevant domain exposure.
  • New function: choose different evidence from the master and explain the connection more deliberately.
  • New seniority: emphasize the real scope of decisions, leadership and accountability—without inflating titles or team size.

What a light edit and deeper edit look like

Light edit: support role → support role

Move the bullet about handling escalations higher, name the ticketing tool already used, and trim an unrelated stockroom task.

Deeper edit: teacher → learning designer

Lead with curriculum projects, learner research, facilitation and content evaluation; reduce routine classroom administration. Do not rename teaching experience as a learning-designer job.

Know when to stop editing

Your version is ready when a reader can quickly understand:

  • What direction you are pursuing
  • Which past evidence supports the central work
  • What scope and outcomes you can credibly discuss
  • Where any important gap remains

It is not ready merely because every phrase from the job posting appears somewhere. More edits can make the document less coherent, less human and harder to defend.

What should never change

Create a separate job-specific version

Start from your master and keep the original unchanged.

Create a separate job-specific version