How to Write a Targeted Resume (With a Worked Example)

"Tailor your resume to the job" is advice everyone has heard and few people follow, mostly because it sounds like rewriting your resume from scratch for every application. It does not have to be. A focused pass can be mostly reordering and clarifying the evidence that matters for that role.

Here is the method, then a worked example.

Why it works

Two reasons, and only one of them is about software.

The human reason. Whoever reads your resume is holding a specific role in their head and scanning for evidence against it. If the relevant experience is your fourth bullet under your second job, it can be harder to find and evaluate.

The software reason. Some employers use software to sort or score resumes against role requirements. When relevant evidence is buried or absent, an automated process may not surface it clearly for review.

Both reasons point at the same fix: put the relevant thing first, in their words.

A practical targeting method

1. Build a master resume once (60 minutes, once)

This is the part that makes everything else fast. A master resume is a long, private document containing every role, every project, and every achievement with numbers attached — far more than you would ever send. Three pages, five, it does not matter; nobody sees it.

Targeting then becomes selecting and ordering from the master, not writing. If you find yourself composing new bullets for each application, your master is too thin.

2. Read the posting properly (5 minutes)

Not skimming. You are extracting three things:

• Hard requirements — the binary ones. Licence, authorisation, clearance, or a specific certification. Check whether you meet them, or can realistically meet them, before you invest time applying.
• Repeated themes — whatever the posting says three different ways is what the job actually is. If "stakeholder management" appears in the summary, the responsibilities and the requirements, that is the role.
• Their vocabulary — the exact words they use. "Demand planning" or "forecasting". "Client" or "customer". "Programme" or "project".

3. Rewrite the summary (5 minutes)

Your summary is prominent space on the page. It should say what you are, at what level, and in which domain, using concise evidence rather than only adjectives.

Generic: Results-driven professional with a proven track record of success in fast-paced environments.

Targeted: Operations analyst, six years in e-commerce logistics. Built the demand-planning model that cut stockouts 40% at a £30M retailer.

The second one is targeted at a demand-planning role because it leads with demand planning.

4. Reorder, do not rewrite (5 minutes)

Within each role, put bullets in order of relevance to this posting, rather than chronology or personal preference. The first bullets under your recent job are likely to be among the first details a reviewer sees.

5. Align vocabulary (3 minutes)

Where you did the thing they named, use their word for it. Not to fool a matcher — because you want the match to be effortless for the person reading.

The rule is accuracy. Mirroring their term for work you genuinely did is good practice. Mirroring a requirement you do not meet is a claim that collapses in the first interview.

6. Cut what is not relevant (2 minutes)

The hardest step. That project you loved which has nothing to do with this role is costing you space and attention. Move it down, shorten it to one line, or drop it.

A worked example

This illustrative example uses a hypothetical Demand Planning Analyst posting that repeatedly mentions forecasting accuracy, cross-functional work with buying teams, and SQL.

Before - a short version of a hypothetical master resume:

Operations Analyst — Northfield Retail Group (2021–2026) · Produced weekly and monthly reporting for the operations leadership team · Supported the annual budgeting cycle across four business units · Built a demand forecasting model in Python and SQL, reducing stockouts · Managed relationships with third-party logistics providers · Ran onboarding for new analysts joining the team

After - a targeted version using additional facts from that hypothetical master resume:

Operations Analyst — Northfield Retail Group (2021–2026) · Built the demand forecasting model (Python, SQL) that cut stockouts 40% and improved forecast accuracy from 71% to 88% across 1,200 SKUs · Ran the weekly forecast review with buying and merchandising, reconciling their commercial view against the model · Produced the operations reporting pack used in monthly leadership review · Managed three 3PL relationships and the annual budgeting cycle for four business units

What changed:

• The forecasting bullet moved from third to first and includes the known outcome details.
• Cross-functional work with buying - a named requirement - was added from the broader hypothetical record.
• SQL is now visible, because the posting names it.
• Onboarding new analysts dropped. Real, creditable, irrelevant here.

The targeted version uses details that are assumed to exist in the hypothetical candidate's master record. In a real resume, targeting means surfacing evidence that is true and relevant, not inventing experience.

What not to do

Do not stuff keywords. Many systems do more than count exact strings, and a human reviewer can spot claims you cannot support. Hidden text and keyword blocks make a resume harder to trust. More on what keyword advice still holds.

Do not target so hard you look narrow. If you strip everything but the exact job, you read as a one-trick candidate. Keep the range, reorder the emphasis.

Do not target a resume that will not parse. All of this is downstream of the document being readable in the first place. A two-column layout can scramble in some extraction tools and make the targeting hard to see. Fix that first - how to write an ATS-friendly resume.

Do not target a job you cannot do. Targeting surfaces genuine fit. It cannot manufacture it, and getting an interview you cannot survive is worse than not getting it.

What this looks like from the other side

Worth knowing what can happen after you send it. Depending on the employer's workflow, your resume may be parsed into structured fields and compared with role requirements. Putting relevant evidence where a reviewer can find it makes that process clearer.

We build the software on that side of the process, and wrote up the mechanism honestly, including where it goes wrong: AI resume screening: how it works, where it fails.