Recruiters do not read every application. They search. They open the applicant tracking system, type the two or three capabilities the hiring manager keeps asking about, and work through whoever comes back. If your resume does not contain those terms in a recognisable form, you are not in the result set — regardless of how well you could do the job.
The good news is that the search terms are not a mystery. They are in the job description, written down, usually in priority order. This is a method for extracting them.
Step 1: Separate requirements from atmosphere
A typical posting is half specification, half marketing. “We are a fast-paced team that values ownership” tells you nothing you can put on a resume. “Experience building REST APIs in Python, with exposure to AWS” tells you exactly what to demonstrate.
Copy the posting into a scratch document and highlight only the concrete, checkable items:
- Tools and technologies — named languages, frameworks, platforms, and products.
- Methods and processes — Agile, CI/CD, design systems, financial close, clinical audit.
- Deliverables — dashboards, migrations, campaigns, onboarding flows, quarterly reports.
- Scope markers — team size, budget, region, user counts, regulatory environment.
- Certifications and credentials — the ones stated as required or preferred.
Ignore everything about culture, energy, and passion. It is real to the employer but it is not searchable, and it is not what you are being filtered on.
Step 2: Rank by how often and where they appear
Not all requirements carry equal weight. Two signals tell you which ones the hiring manager actually cares about:
- Repetition. A term that shows up in the job title, the summary paragraph, and the requirements list is the spine of the role. A term mentioned once at the bottom of “nice to have” is decoration.
- Position. The first three bullets of a requirements list are usually written by the hiring manager. The rest often comes from a template.
Sort your highlighted list into three tiers: must appear (repeated or in the title), should appear (stated as required, mentioned once), and optional (nice-to-haves). You will place them differently.
Step 3: Match honestly, and name the equivalents
Now go through your tiers and mark each term as one of three things.
| Your situation | What to do |
|---|---|
| You have done exactly this | Use the posting's exact term, inside a bullet that shows the outcome. |
| You have done the equivalent under a different name | Name both: “container orchestration (Kubernetes)” or “BI dashboards (Looker, similar to Tableau)”. |
| You have not done it | Leave it out. Do not list it in skills “because you could learn it”. |
That third row is where people go wrong, and it backfires in a specific way: listing a tool you cannot discuss means the first technical question of the screening call exposes it. You lose the interview and the benefit of the doubt at the same time.
Step 4: Place them where they carry evidence
A keyword in a comma-separated skills list proves nothing. The same keyword inside an achievement bullet proves you used it and shows what happened. Both have a place, but the ratio matters.
Same keyword, different weight
Works
- Rebuilt the checkout service in Go, cutting p95 latency from 840ms to 210ms
- Ran quarterly SOC 2 evidence collection across 6 engineering teams
- Automated weekly reporting in SQL and Looker, saving ~5 analyst hours a week
Avoid
- Skills: Go, SOC 2, SQL, Looker, Kubernetes, Terraform, Python, React, AWS, GCP
- Familiar with a wide range of modern tools and frameworks
- Strong understanding of cloud infrastructure and reporting
A workable distribution for a one-page resume:
- Tier 1 terms appear in your summary line and in at least one experience bullet.
- Tier 2 terms appear once, in a bullet or in the skills section.
- Tier 3 terms appear only if you genuinely have them and there is room.
Use the exact form the posting uses, then add your variant if it differs. Spell out abbreviations the first time — “search engine optimisation (SEO)” — because recruiters search both forms and you cannot predict which.
Step 5: Check it reads like a person wrote it
Read the finished resume aloud. If a sentence exists only to hold a keyword, cut it. Keyword-stuffed resumes are obvious to the human reviewer, and the human reviewer is the one who decides.
A useful last pass: for each tier 1 term, ask “if the interviewer opens on this, do I have a two-minute story ready?” If not, either soften the claim or prepare the story. Your resume is a set of promises about the conversation you are about to have.
Frequently asked questions
How do I find keywords if the job description is vague?
Look at two or three other postings for the same title at comparable companies and use the terms common to all of them. You can also check the LinkedIn profiles of people currently in that role at the company — the vocabulary they use is usually the vocabulary the recruiter searches.
Should I copy the job description wording exactly?
Copy the specific nouns — tool names, methods, credentials — because those are what recruiters search on. Do not copy whole phrases or sentences; a resume that echoes the posting verbatim reads as automated and gives the reviewer nothing new.
Where is the best place to put keywords on a resume?
Inside experience bullets, where they sit next to a result. A skills section is useful as a scannable index of your tools, but a term that only appears there carries no evidence. The strongest keywords appear in both places.
Is it worth using an online resume keyword scanner?
They can be a useful sanity check on coverage, but most of them score keyword overlap rather than whether your experience is convincing. Reading the posting carefully and mapping requirements by hand gets you further, and takes about the same amount of time.