How to find resume keywords in a job description

Short answerThe keywords that matter are the concrete things a recruiter would type into a search: tools and technologies, hard skills, job titles, certifications and the industry. Take them from the job title and the requirements, not the company description. Ignore soft-skill adjectives. For each one you genuinely have, use the posting's exact wording once or twice, in the experience bullet where you used it.

"Add the keywords from the job description" is the most common resume advice there is, and it is half right. A posting is full of words, and most of them are not keywords. Copying the wrong ones makes a resume longer and vaguer without making it easier to find. This is the method we use, and the same one Shortlist's quick check follows when it reads a posting.

What a keyword is

A keyword is a term a recruiter would type into their applicant tracking system's search, or look for in the first ten seconds of reading. In practice that means:

Tools and technologies: Kubernetes, Salesforce, SAP FICO, Figma, Tableau.
Hard skills and methods: financial modelling, SEO, contract negotiation, A/B testing, IFRS reporting.
Job titles: "Product Manager", "Site Reliability Engineer", "Staff Accountant".
Certifications and licences: CPA, PMP, AWS Solutions Architect, a nursing licence.
The domain: payments, B2B SaaS, clinical trials, logistics.

Things that are not keywords, even when the posting repeats them: "communication", "team player", "self-starter", "passionate", "fast-paced", "stakeholders", "ownership". Every candidate claims them and no recruiter searches for them. They are judged in the interview, not in the database.

Broad words such as "development", "design", "cloud", "software" or "analysis" are not keywords on their own either. "Cloud" means nothing until the posting says which cloud. Shortlist's own keyword check skips words like these for the same reason.

Where to look in a posting

Postings follow a pattern, and the keywords are not spread evenly across them.

The job title. The single most important line. If you have done this job under a different title, that matters (see below).
The first three or four requirements. Employers put the core of the role first. A tool named here is usually a must.
Anything named more than once. A technology that appears in the summary, the duties and the requirements is central to the role.
The "nice to have" or "preferred" list. These count, but less. Missing one rarely matters.

Skip the company description, the benefits and the equal-opportunity statement. They describe the employer, not you.

A worked example

Here is part of a typical posting:

Senior Backend Engineer, Payments You will design and build the services behind our checkout. You are a collaborative engineer who thrives in a fast-paced environment.

5+ years building backend services in Java or Kotlin

Strong experience with Spring Boot and PostgreSQL

Event-driven systems with Kafka

Running services on Kubernetes in AWS

Nice to have: experience with PCI DSS, Terraform

The keywords are: Senior Backend Engineer, payments, Java, Kotlin, Spring Boot, PostgreSQL, Kafka, event-driven, Kubernetes, AWS, and less important, PCI DSS and Terraform.

Not keywords: "collaborative", "fast-paced", "design and build", "services" on its own. "5+ years" is a requirement, but it is checked against your dates, not your wording.

Exact terms, acronyms and other names

Search is often literal. If the posting says "PostgreSQL" and your resume says "Postgres", a simple search can miss you, even though a person would not.

Use the posting's spelling for a skill you have. Write "PostgreSQL" if that is what they wrote.
Write out an acronym once, with the short form: "Amazon Web Services (AWS)", "Search Engine Optimisation (SEO)". After that, the short form is enough.
Versions usually do not matter. "Java 17" in a posting is satisfied by Java experience; mention the version only if you used it.
Titles can be translated, honestly. If your official title was "Member of Technical Staff" and the posting says "Software Engineer", you can write "Member of Technical Staff (Software Engineer)". Do not change the title itself.

Where to put them

A keyword only helps where it is believable.

In your experience bullets, first. "Built the refund service in Spring Boot and PostgreSQL, handling 2M events a day through Kafka" carries three keywords and the evidence for them.
In the skills section, second. Group it ("Languages: Java, Kotlin, SQL"), with the posting's core tools first.
In the summary, the two or three that define the role. "Backend engineer, six years building payment services in Java and Spring Boot."

Once or twice each is enough. Repeating a term ten times does not help a recruiter's search, and it reads badly to the person who opens the resume. Hidden or white text is worse: parsers read it, and recruiters see it in the parsed version.

Only the ones you have

The point of this exercise is not to cover every keyword. It is to make sure that the ones you genuinely have are written the way the employer wrote them, and to see clearly which ones you do not have.

A missing nice-to-have is normal. A missing core keyword, the tool in the title or the first requirement, is worth knowing before you apply; our guide on whether to apply when you don't meet every requirement covers that decision. Adding a tool you have not used is the fastest way to fail an interview, and our guide to tailoring a resume without making things up explains the honest version step by step.

Check that they can be read

Keywords only count if the system can read the text they are in. Columns, text boxes, headers and images can hide them from a parser; we saw this happen in our test of seven resume templates. The free ATS checker shows the text a system would extract from your file, so you can check that your keywords survive.

How Shortlist does this

When you open a job posting, Shortlist lists the technologies the posting names and marks which ones are already in your profile, before anything else. That check is a fixed list of tools run in code, not AI, and it skips generic words. The full score then reads every requirement against your experience, so a tool you used under another name, or one implied by your work, is counted. When you tailor a resume for the job, it uses the posting's terms only for what your profile shows you have.

FAQ

How many keywords should a resume have?

There is no target number. Include each core skill from the posting that you genuinely have, once or twice, where you describe using it. For a typical posting that is somewhere between five and fifteen terms.

Should I copy the job description into my resume?

No. Copy the names of the tools, skills and qualifications you have, written the way the posting writes them. Copying sentences makes the resume read like the posting instead of like your experience.

Do soft skills count as resume keywords?

Rarely. Words like "communication" and "leadership" are in almost every posting and almost every resume, so recruiters do not search for them. Show them through results in your bullets, such as leading a team of five or presenting to clients.

Do I need a different resume for every job?

You need one resume that reads cleanly, then small changes for each job: the order of bullets, the summary and the exact terms. For similar roles the changes take a few minutes.