Pull the right keywords from a job posting

By The HireReady24 team · Updated 1 September 2026

Every job posting is a keyword list in disguise. The employer has already told you the exact words they want to see — the skills, tools, and outcomes they'll scan for and, often, the terms an applicant-tracking system (ATS) scores you against. Extracting them well is the mechanical skill underneath tailoring a CV: before you can mirror the posting's language, you have to know which words actually matter.

This guide walks through how to pull those keywords by hand, decide which ones earn a place on your CV, and place them without ever writing something that isn't true.

Read the posting for nouns, not vibes

Skim once for the gist, then read again for the concrete nouns. Keywords are almost never adjectives like "dynamic" or "passionate" — they're the named things the job runs on:

Hard skills and tools — "SQL," "Kubernetes," "double-entry bookkeeping," "Figma."
Methods and frameworks — "Agile," "GAAP," "user research," "incident response."
Responsibilities and outcomes — "owned the release pipeline," "reduced churn," "managed a £2m budget."
Certifications and standards — "CPA," "ISO 27001," "AWS Solutions Architect."

Write each one down verbatim. The exact wording is the point — you'll reuse it, not paraphrase it.

Worked: one posting paragraph, extracted

Here is a composite posting excerpt — assembled from phrasing common to real listings, not lifted from any one of them:

Operations Analyst — Logistics. You'll own our weekly capacity forecast, working cross-functionally with warehouse leads and the commercial team to keep service levels on track. You'll rebuild the reporting layer in SQL and Looker, replacing the spreadsheet process we've outgrown. Experience with demand planning is required; exposure to WMS migrations is a plus. We're a fast-paced environment and you'll wear many hats. Familiarity with Lean or Six Sigma welcome.

What comes out, verbatim:

Tools: SQL, Looker, WMS.
Methods: demand planning, capacity forecast, Lean, Six Sigma.
Responsibilities and outcomes: own the weekly capacity forecast, rebuild the reporting layer, keep service levels on track.
Certifications: none named — worth noticing, because nothing here is gated behind a qualification you either hold or don't.

What stays on the page, and why:

"fast-paced environment," "wear many hats" — filler. Nothing you could write answers them.
"warehouse leads," "the commercial team" — the org chart, not a skill.
"the spreadsheet process we've outgrown" — the problem they're hiring against. Cover-letter material, not a keyword.
"cross-functionally" — undecided. Exactly the kind of term the next section exists for.

Notice how little of the paragraph survived. That's the point: most of the value of extraction is in what you refuse to carry forward.

Rank keywords by how hard the employer leans on them

Not every term carries the same weight. Sort what you found into three tiers:

Repeated or required. Anything that appears in the title, the first few bullets, or under "requirements" is load-bearing. These are the terms your CV must answer.
Named once, in context. A specific tool or method mentioned once still signals genuine need — include it if it's true of you.
Boilerplate. "Team player," "fast-paced environment," "wears many hats." These are filler. Ignore them; matching them proves nothing.

A term that shows up three times in one posting is the single strongest signal you'll get about what the reader is looking for. Treat it that way.

The borderline terms, adjudicated

Tier one and tier three are easy. The terms that cost people an evening are the ones that sound like skills and might not be. Here are the recurring offenders and how they actually resolve:

| Term | Verdict | Why | |---|---|---| | "fast-paced environment" | Discard | It names no skill and no artefact. No sentence you could write would settle whether you have it. | | "cross-functional" | Tier 2 — if you name the functions | As a claim it's a vibe; as evidence it's a fact. The posting above already says which functions it means. | | "ownership" | Depends on what follows it | "Own the weekly capacity forecast" is a tier-one responsibility with an object attached. "A strong sense of ownership" is tier three. | | "stakeholder management" | Tier 2, and rewrite before use | An abstraction over specific acts — running a planning sync, renegotiating a deadline, refusing a request. Keep the employer's phrase, but put it next to the concrete line, never instead of it. | | "attention to detail" | Discard as a claim | Nobody has ever been believed on it. It's an instruction about how to write the rest of your CV, not a term to place in it. | | "self-starter" | Discard the word, answer the question | The only proof is something you started. If you have one it belongs inside an achievement bullet, where the adjective adds nothing to it. |

The rule underneath all six: a term is worth keeping if you can imagine the sentence that would prove it. If no sentence would settle the question it's boilerplate, however often the posting repeats it.

Map each keyword to real evidence before you use it

A keyword only belongs on your CV if you can stand behind it. Take each tier-one term and ask: where did I actually do this? If the posting says "stakeholder management," the keyword earns its place only when there's a real line beneath it — "ran the weekly planning sync across three teams" — not a bare entry in a skills list.

If you can't find honest evidence for a required keyword, that's real information about fit. Note it, but never close the gap by adding a word you can't defend in an interview. A CV that keywords its way past the filter and then falls apart in the first conversation has wasted everyone's time.

The keyword you half-have

Most real cases aren't yes or no. You used the tool once, on a side project. You ran the process but didn't own it. It was two roles ago. Dropping the term loses you something you legitimately hold; claiming it flat invites a question you can't answer. The way out is to say which of these it was:

Used it once. Put it in a bullet, never in a skills list — a list implies a fluency the sentence doesn't. "Built a prototype capacity forecast in Looker for a side project." The words "prototype" and "side project" cost you nothing and turn a claim into a fact.
Used it in production. The term is yours and the skills-list entry is earned. "Reported weekly on service levels in Looker for the commercial team." Naming who consumed the work is what separates using a tool from having opened it.
Owned it. Use verbs of authorship — designed, rebuilt, maintained, decided. "Designed and maintained the Looker reporting layer, including the weekly forecast."

Two rules make this work. Say when, if it was long ago — "in a previous role," or the year, pre-empts the awkward version of the question. And check the phrasing survives a follow-up: read your line, then ask yourself "tell me about that" out loud. If you have a few minutes of true detail behind it the line is fine; if you'd immediately start qualifying it, downgrade the phrasing until you wouldn't. None of this is licence to hedge — "familiar with" describes your comfort rather than your work, and a reader can do nothing with it.

Place keywords where both readers will find them

Two things read your CV: a human skimming quickly, and often software matching text. Both are served by putting keywords where they carry weight, in your own true sentences:

In your bullet points, inside the achievement — "cut deploy time using Terraform," not a lonely "Terraform" in a list.
In your summary, if you keep one, naming the two or three terms most central to the role.
In a skills section, for the concrete tools and certifications that are genuinely yours — this is the one place a plain list of terms is legitimate.

Avoid the two failure modes: keyword stuffing (repeating terms until the prose reads like spam) and keyword hiding (burying a critical skill in the last line of your oldest role).

Three bullets, before and after

That rule is easy to agree with and easy not to apply. Three shapes it usually takes, written against the posting extracted earlier.

Stuffed → placed. Every term present, not one of them evidenced:

Before: "Skilled in SQL, Looker, demand planning, capacity planning, forecasting, stakeholder management, cross-functional collaboration, and process improvement."
After: "Rebuilt the weekly capacity forecast in SQL and Looker, replacing a spreadsheet the warehouse and commercial teams had both outgrown."

Buried → surfaced. The keyword is there — in the last line of a role from years ago:

Before: "Assisted with various reporting tasks, including some WMS migration support."
After: "Supported the WMS migration as reporting lead — rebuilt the standard report set against the new schema and ran the parallel period with the warehouse team."

Listed → evidenced. A skills entry with a self-assessed level, which no reader can check:

Before: "Demand planning (advanced)"
After: "Ran monthly demand planning for the ambient range, then moved it to a weekly cycle after a season of stockouts."

In all three the number of keywords barely changes. What changes is that each term now sits next to the thing that proves it — the one edit a careful human reader and a text matcher both reward, for different reasons.

From a ranked list to actual edits

You now have terms, tiers, and evidence. Turning that into a document is three passes:

Answer tier one in bullets you already have. For each required term, find the closest existing bullet and rewrite it to carry the employer's wording. Adding new bullets is a later and much larger decision.
Run tier two through the half-have scale. Anything surviving at "used it once" or better gets phrased at that level. Anything that doesn't, drop without regret.
Rebuild the skills section from what's left, and only from what's left. It decays fastest between applications, because nothing forces you to reread it.

Then stop. Which roles to keep, how far back to go, what order the document runs in and what comes out of it are tailoring decisions, and they live in how to tailor your CV to a job description. This guide's job ends when you have a ranked, evidenced list and know which bullets it lands in.

A quick keyword-extraction checklist

You've listed every hard skill, tool, method, and named outcome from the posting, verbatim.
You've ranked them — repeated/required first, boilerplate discarded.
Every borderline term has a verdict and a reason behind it, not a shrug.
Every keyword you plan to use maps to something you actually did, at the level you did it.
Each one sits inside a true sentence, not stranded in a list to game a filter.
Nothing on the page is a term you couldn't speak to if asked.

Do this once and the posting stops looking like a wall of text and starts looking like an answer key. The work is genuinely dull by hand: read twice, transcribe verbatim, argue with yourself about the ambiguous ones, then hunt back through your own history for the line that proves each survivor. HireReady24 does the first half — it parses the posting, separates the load-bearing terms from the filler, and shows where your existing experience already answers them. The adjudication in the middle of this guide is the half that stays yours, because it rests on work only you can vouch for.

Next, see common CV tailoring mistakes for the errors that undo good keyword work.