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 is not. Done properly it is about twenty minutes of reordering and re-wording, and it is the single highest-return thing a job seeker can do.

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, you are asking them to do work. Most will not.

The software reason. Automated screening scores you against requirements the employer has defined. It is looking for evidence of those specific things. Experience you have but did not surface does not get credit — not because the system is stupid, but because it cannot see what is not there.

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

The 20-minute 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, a specific certification. If you fail one, do not apply; nothing else will save it.
• 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 the highest-value real estate on the page and most people waste it on adjectives. It should say what you are, at what level, in their domain, in two lines.

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, bullets go in order of relevance to this posting, not chronology and not what you are proudest of. The first bullet under your most recent job is the second-most-read line on the page after your summary.

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

The posting is for a Demand Planning Analyst, and it repeatedly mentions forecasting accuracy, cross-functional work with buying teams, and SQL.

Before — from the 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 — targeted:

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 gained the numbers it was missing.
• Cross-functional work with buying — a named requirement — was pulled out of nowhere. It was always part of the job; it just was not written down.
• SQL is now visible, because the posting names it.
• Onboarding new analysts dropped. Real, creditable, irrelevant here.

No facts were invented. Everything in the "after" was true in the "before" or true and unwritten. That is what targeting is: surfacing what was already there.

What not to do

Do not stuff keywords. Screening moved from string matching to language models some time ago — "led a team of six" satisfies a people-management requirement without the phrase. Hidden white text and 1pt keyword blocks are detectable and read as dishonesty when a human sees them. 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 that scrambles on extraction makes the targeting invisible. 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 happens after you send it. Your resume is parsed into structured fields, scored against the requirements the employer defined, and ranked. The scoring reads for evidence of specific requirements — which is exactly why surfacing the relevant thing works, and why burying it costs you.

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.