← All guides

Resume Keywords: Find Them in a Job Posting

A job posting is a list of things the employer wants, written in the employer's own words. Your resume is a list of things you have done, written in yours. Resume keywords are where those two lists meet. If you call the same thing by a different name, a reader has to guess that you mean it, and a search may not find it at all.

This guide shows how to find the keywords in a posting, which ones matter most, and how to put them into your resume without claiming anything untrue. We say resume, and CV means the same thing.

What counts as a keyword

A keyword is not only a tool name. Look for these kinds of terms in a posting:

  • Hard skills and tools. SQL, Salesforce, Figma, a payroll system.
  • Methods and techniques. A/B testing, cohort analysis, agile planning.
  • Job titles. The title in the posting, and titles it mentions for related roles, such as "product, data or business analyst".
  • Qualifications and certifications. A degree, a licence, a named certificate. Write the full name.
  • The domain or industry. E-commerce, logistics, health care. These words show you know the setting.
  • Languages. Spoken languages, and the level the posting asks for.
  • Soft skills, written as actions. "Good communicator" says little. "Explained findings to non-technical stakeholders" says what you did, and it is the kind of phrase a posting uses.

A posting rarely asks for "communication" as a bare word. It asks for something you do, such as presenting to stakeholders. Keep those verbs.

Where to find them in a posting

Read the whole posting

Do not stop at the bullet points. Useful words also sit in the opening paragraph about the company and in the job title. Read it from top to bottom once before you mark anything.

Split the requirements from the duties

Most postings have two lists. One says what you will do. The other says what you bring. They serve different purposes:

  • The duties list shows the work: the methods, the tools in daily use and the people you will deal with.
  • The requirements list shows the entry bar: years of experience, named tools, qualifications, languages.

Collect terms from both.

Spot the must-haves and the nice-to-haves

Postings usually signal how firm a point is.

Signal What it usually means
"Required", "you bring", "must", "3+ years" Must-have
"Strong", "hands-on", "experience with" Usually a must-have
"A plus", "nice to have", "ideally", "bonus", "preferred" Nice-to-have
"Such as X or Y" Either one counts

Read "a BI tool such as Looker or Tableau" as one requirement that either tool meets. You do not need both.

Notice what appears twice

When a term shows up in both the duties and the requirements, it is usually central to the job. A posting that lists SQL under what you will do and again under what you bring is telling you twice. Give those terms the best place in your resume.

Use the company intro for domain words

The paragraph about the company often names the setting: the product, the customers, the industry. Those words are keywords too. If you have worked in the same setting, say so in the same words.

A worked example

Here is a posting. It is a fictional sample that we wrote for testing. The company, the role and the candidate we use below, Maya Jansen, are all made up.

Product Analyst (Rotterdam, hybrid)

We are a growing e-commerce fulfilment platform helping 400 online shops ship faster. Our product team is looking for a Product Analyst to turn data into decisions across checkout, warehousing and delivery.

What you will do

  • Own the product metrics for our merchant dashboard and define the KPIs each squad works towards
  • Design and analyse A/B tests and other experiments with product managers
  • Build reliable data models in SQL and dbt, and self-serve dashboards in Looker
  • Dig into funnels, cohorts and retention to find where merchants get stuck
  • Present findings to stakeholders from operations, commercial and engineering, and turn them into roadmap input

What you bring

  • 3+ years in a product, data or business analyst role
  • Strong SQL; Python for analysis is a plus
  • Hands-on experience with experimentation and statistics
  • Experience with dbt and a BI tool such as Looker or Tableau
  • You explain complex findings clearly to non-technical stakeholders
  • Fluent English; Dutch is a plus

Our free checker pulled 20 requirements out of this posting. Of those, 18 are must-haves and 2 are nice-to-haves: Python for analysis and Dutch language, both from the words "is a plus". Here is how some of the posting's words became requirements.

In the posting Requirement Importance
"a BI tool such as Looker or Tableau" Looker or Tableau (either one meets it) Must-have
"Dig into funnels, cohorts and retention" Funnel analysis, Cohort analysis, Retention analysis Must-have, each
"turn them into roadmap input" Roadmap input Must-have
"with product managers" Product manager collaboration Must-have
"define the KPIs each squad works towards" Product KPIs Must-have
"Python for analysis is a plus" Python for analysis Nice-to-have
"Dutch is a plus" Dutch language Nice-to-have
"e-commerce fulfilment platform" (company intro) E-commerce fulfilment domain Must-have

Three things stand out.

First, the checker counted duties as must-haves. Funnels, cohorts, retention, roadmap input and working with product managers are all in the "what you will do" list, and none of them is in the "what you bring" list. A reader who only checks the requirements would miss them.

Second, the domain came from the company intro. The words "e-commerce fulfilment platform" are not in either list, which is why you read the whole posting.

Third, SQL, dbt, Looker and stakeholders each appear in both lists. Treat them as central.

Sort what you found

Once you have the list, sort every term into one of three piles. This step keeps the rest of the resume truthful.

  1. You have it and can show it. You did the work. Put it in an experience bullet, in the posting's wording.
  2. You have it but left it off. You did the work, but your resume never says so. This pile can be bigger than you expect, because old resumes were written for old jobs.
  3. You do not have it. Leave it out. Do not stretch a nearby skill to cover it.

Maya's resume shows all three. She had the SQL and A/B testing and could show both. She had done a returns funnel and monthly cohort analysis at work, but had left both off. And she had never used dbt. In every version of her resume, dbt stayed missing, and that is the honest answer. You do not need to match every line of a posting, and an honest gap is better than a claim you cannot support in an interview.

Where keywords count most

A keyword does the most good inside a bullet that shows the work. A term in a skills list says you know the word. A term in a bullet says what you did with it, and a human reader finds that far more believable.

Our checker follows the same idea, and the rules are simple. A must-have has weight 3 and a nice-to-have has weight 1. A requirement shown in your experience earns full credit. One that is only listed, such as in a skills line or the summary, earns half. A missing one earns none. The score is 100 times the sum of weight times credit, divided by the sum of the weights. It is worked out in code, so the same resume and posting always give the same score. It is our own estimate, and it is not any employer's system.

Maya's three versions show what moves it:

Requirement Raw notes Reworded Real work added
Product KPIs Missing In experience Listed only
Funnel analysis Missing Missing In experience
Cohort analysis Missing Missing In experience
Roadmap input Missing Missing In experience
dbt Missing Missing Missing
Score 43 51 70

Her raw notes scored 43. We reworded the same facts for the posting and the score rose to 51, with nothing new claimed. Then she added real work she had left out, a returns funnel and monthly cohort analysis, and the score reached 70. The biggest jump came from adding true evidence, not from rearranging words.

Phrasing matters

Look at the Product KPIs row. In the reworded version it counts in experience. In the last version it is only listed. Both versions describe KPI work, so what changed?

The reworded bullet says: "using clear KPI definitions". That matched the Product KPIs requirement, and it counted in experience. In the last version the bullet only says "Defined a single delivery KPI". None of the phrasings the checker accepted for that requirement appears there, so the requirement counted as listed only, from the skills line.

A person reads both bullets as KPI work. A keyword search reads words. If the posting says "KPI definition" and your bullet says "defined a KPI", a literal search may not see them as the same thing.

As a rule, when you do something the posting names, use the posting's noun for it at least once, in a bullet.

Wording tips

  • Use the posting's exact term for a skill you really have. If it says "stakeholder management" and you did that, write "stakeholder management".
  • Spell out an acronym once. Write "search engine optimisation (SEO)" the first time, then use either form. A posting or a search may use the long form, the short form or both.
  • Write the short term as well as the specific one. If the posting says SQL and you use PostgreSQL, write "SQL" somewhere too. Our checker matches whole words only, so "SQL" does not match inside "PostgreSQL". A search in some systems may be just as literal.
  • Use the posting's job title only if it truly describes you. If you were a Data Analyst and the posting says Product Analyst, keep your real title. Do not rename a job you held.
  • Write in the posting's language. If the posting is in German, French or Dutch, write your resume in that language. A search in German may not find English terms.

Our checker ignores case and accents, treats a hyphen like a space, and accepts a plural "s" or "es". It matches whole words only, and each requirement carries a few accepted phrasings, chosen when the posting is read. Other systems will differ, so treat this as a picture of how literal matching can be, not as a promise.

Do not stuff keywords

More is not better. Avoid:

  • Hiding extra keywords in white text. A person who opens the file will see it, and it can end your chances at once.
  • Long lists of tools you have never used. They will not survive the interview.
  • Repeating a term again and again. It reads badly and adds no evidence.

If a keyword is true, show it once, in a bullet that proves it. If it is not true, leave it out.

A short method you can follow

  1. Read the posting once, top to bottom, including the company intro and the closing lines.
  2. Highlight the terms: tools, methods, titles, qualifications, domain words and languages.
  3. Mark each as a must-have or a nice-to-have, using the signals above. Note "such as X or Y" lists.
  4. Circle terms that appear in both the duties and the requirements. These come first.
  5. Sort every term into three piles: have and can show, have but left off, do not have.
  6. Write or rewrite bullets for the first two piles, using the posting's term for each skill you truly have.
  7. Leave out the third pile. Do not add a skill you cannot back up.
  8. Read it as a person. Does each bullet still sound like real work with a result? If not, rewrite it.

Next steps

To see where your own resume stands, paste it and a posting into the free ATS checker. It needs no sign-up and does not store your CV or the posting. Your CV is matched in code and is not sent to an AI model. The posting is sent to an AI model once, to pull out its requirements and mark each as a must-have or a nice-to-have. Only that requirement list is kept, under a fingerprint of the posting. You see which requirements your resume shows in experience, which it only lists, and which it misses.

For the wider picture, read our guides on what an ATS is, how to format an ATS-friendly resume and how to tailor your CV to a job description. Our page on how to tailor your resume to a job description shows the idea end to end.

When you are ready to apply, KnockCV can write the resume and a cover letter from the facts you give it, in the posting's wording wherever your experience supports it. It never adds skills you do not have. Start tailoring in the app. You get 3 free CVs when you sign up, then pay as you go with no subscription.

Frequently asked questions

What are resume keywords?
Resume keywords are the words and phrases a job posting uses for the skills, tools, methods, qualifications and job titles it wants, and that your resume uses for the same things. They are the terms a recruiter or a system may search for. They only help when they describe work you have really done.
How do I find the keywords in a job posting?
Read the whole posting, then list the tools, methods, qualifications, job titles, domain words and languages it names. Then sort them: words like 'required' and 'you bring' usually mark a must-have, and 'a plus' or 'ideally' a nice-to-have. Terms that appear in both the duties and the requirements are usually central. You can also paste the posting and your resume into the free ATS checker, which pulls out the requirements for you.
How many keywords should a resume have?
There is no right number. Use each term from the posting that honestly describes your work, in a bullet that shows the work. If you have done ten of the things a posting asks for, ten terms will appear naturally. Repeating a term to hit a count reads badly and does not add evidence.
Should I copy the wording of the job posting exactly?
Use the posting's exact term for a skill you really have, because a person or a search may look for those words. Do not copy whole sentences, and do not claim anything you have not done. If the posting says cohort analysis and you did cohort analysis, say cohort analysis.
Is it enough to list keywords in a skills section?
A skills line helps, but it is weaker evidence than a bullet that shows the skill in use. In the KnockCV checker, a requirement shown in your experience gets full credit and one that is only listed gets half. Put the term in a skills line and in a real bullet if it is true.
What if the posting asks for a skill I do not have?
Leave it out. Do not add a skill you cannot back up, because it will come up in the interview. If you have close experience, describe what you really did in plain words. A nice-to-have you lack matters much less than a must-have you lack, so weigh them differently.
Do I need different keywords for every application?
Usually yes, because every posting asks for a slightly different mix. Your facts stay the same. What changes is which ones you put first and which words you use for them. Keep a master list of everything you have done, and pick from it for each posting.
Does KnockCV add keywords to my resume?
KnockCV writes your resume and a cover letter from the facts you give it, in the posting's wording wherever your experience supports it. It never adds skills you do not have, and it writes in the posting's language. You get 3 free CVs when you sign up, then pay as you go with no subscription.