Resume keywords: how to pick the right ones from a job description

What "keywords" really means

"Add keywords" is common resume advice, and it is usually explained badly. A keyword is not a magic word that unlocks a filter. It is a word or phrase a person is likely to search for when looking for someone like you.

That search is real. In Greenhouse, one of the widely used applicant tracking systems, recruiters can turn on a full-text search across candidates' resumes. Its Talent Filtering page describes searching "job titles, skills, locations, and other keywords in the full text of resumes" during application review, marking terms as Preferred (any one must appear) or Required (all must appear). It also says the search term "must exactly match the keyword in the application", and that Greenhouse can suggest keywords "generated from your public job post".

So the best source of keywords for a specific application is the job post itself. A generic list of 500 "power words" will not tell you what this reviewer is likely to type.

Four kinds of keyword, and one kind of filler

When you read a posting, the useful terms fall into four groups:

Hard skills and methods: SQL, financial modelling, regression testing, requirements elicitation, A/B testing.
Tools and platforms: Excel, Power BI, Jira, Salesforce, AWS, Figma.
Certifications and qualifications: a CA or CPA, PMP, AWS certifications, a specific degree, a driving licence.
Domain terms: the industry's own words, such as KYC, claims processing, supply chain planning, clinical trials.

Then there is filler: "team player", "self-starter", "results-driven", "excellent communication skills". These describe almost every candidate, so they rarely help a search. Soft skills still matter, but they are better shown in a bullet ("presented weekly status to [audience]") than stated as an adjective.

How to extract keywords from one posting: a worked method

Take the posting you want to apply for and work through it in this order:

Read the requirements section line by line. Underline every noun phrase that names a skill, tool, qualification or domain. Ignore adjectives.
Read the responsibilities. Underline the activities, for example "run user acceptance testing", "build monthly forecasts". Convert each to its skill name ("user acceptance testing", "forecasting").
Note the exact form. If the posting writes "Microsoft Power BI", note that; if it writes "PowerBI", note that too. Include both the abbreviation and the full term where a reader might search either ("CI/CD" and "continuous integration").
Count repeats. A term that appears in the title, the requirements and the responsibilities is central. A term mentioned once under "nice to have" is not.
Mark each term with Yes, Partly or No depending on whether you have real evidence for it.

You end up with a short list, usually ten to twenty terms, ranked by how central they are to the job and labelled by how honestly you can claim them. Only the Yes and Partly terms go on your resume.

Looking across many postings

One posting tells you what one employer wants. If you are targeting a role in general, look at several postings for the same title. Terms that show up again and again are worth building your resume and your learning plan around.

ROLIVA publishes skills insights for roles where it has enough current listings to count. Each report shows how many current listings mention each term, with the number of listings and the date they were counted. A mention is not a requirement, and the reports are counted from the listings ROLIVA reads on employers' own careers pages, not from the whole job market.

For a broader, occupation-level view of skills, the US Department of Labor's O*NET OnLine describes the skills, knowledge and tools associated with many occupations. It is US-centred, so treat it as background reading rather than a list for a specific employer.

Where to put keywords on your resume

A keyword helps most where it also has evidence around it:

Summary: your target role title and two or three of the most central skills you have.
Skills section: the tools and skills you can genuinely use, using the posting's spelling.
Experience and project bullets: each central skill should appear at least once in a bullet that shows you using it, for example [Action verb] [what] using [tool], which [result].
Certifications: the full name as the issuer writes it, plus the common abbreviation.

A skill that appears only in a list is a claim. A skill that appears in a bullet with a result is evidence. Reviewers read both, but they believe the second.

Synonyms, abbreviations and spelling

Because a search term may need to match exactly, small differences matter more than people expect:

Abbreviation and full form. Write the full term once with the abbreviation in brackets, such as "search engine optimisation (SEO)" or "user acceptance testing (UAT)". After that, either form reads naturally.
Product names. Use the vendor's spelling: "PostgreSQL", "Power BI", "Salesforce". A misspelt tool name is both a search miss and a proofreading error.
British and American spelling. If the posting says "optimization" and you write "optimisation", a strict literal match may miss it. Follow the posting's spelling for skill names; keep your own spelling elsewhere.
Job titles. If your official title was unusual, keep it, and describe the work in the bullets using the common term. Never rename a past job.

Keywords if you are a fresher or changing careers

With less direct experience, the same method still works, but the evidence comes from different places. For a fresher, projects, internships, coursework and competitions are where a skill keyword gets its proof. For a career changer, look for the posting's terms in work you have already done under a different name, and in any training or projects in the new field. In both cases, a short "Relevant projects" section above your experience can carry the keywords that your job titles do not.

Keyword stuffing and hidden text, and why they backfire

Some advice suggests pasting the whole job description into your resume in white text, or repeating a term ten times. Both are bad ideas:

Parsers extract text regardless of colour, so hidden text ends up in the parsed profile a person reviews.
A skills list that mirrors the posting word for word, with no evidence below it, reads as copied.
Every keyword is something you may be asked about. Canada's Job Bank puts it simply: "Lying on your resume is never a good idea", and advises using "simple words and action verbs" that a non-specialist reviewer can follow (Job Bank).

The aim is not to maximise matches. It is to make sure that the true, relevant things you have done are described in the words a reviewer will search for.

Check your coverage

Once you have tailored your resume, compare it with the posting. ROLIVA's free ATS resume checker takes your resume and a job description and lists which of the job's recognised skills, tools and methods your resume mentions and which it does not. The summary is a plain count, such as "mentions 14 of 22", not a score, and it also flags structure that can cause misreads. It uses fixed rules and no AI model, and nothing you paste is stored.

Treat a missing term as a question, not a verdict. If you have the experience, add it to a bullet with evidence. If you do not, leave it out and decide whether it is worth learning.

For the full process of adapting a resume to one posting, read how to tailor your resume to a job description. To see what to stress for a particular role, browse the resume examples by role.