Keyverta
Sign in

Resume keywords: how to choose them with examples

· Keyverta team · OnruTech

Keywords help explain the relationship between your background and a posting. There is no universal list that works for every role. Choose terms that describe real knowledge or activities, sort them by what the posting actually requires and give them context.

Must-have, nice-to-have or job condition

Before underlining words, classify what the posting asks for. That tells you what must appear with evidence, what you can mention if you have it and what better wording cannot fix.

  • Must-have: usually “required”, “essential”, “must” or the list of requirements. If you have it, it should be visible with evidence.
  • Nice-to-have: “desirable”, “a plus”, “preferred”. Include it only if it is true; lacking it does not always stop you from applying.
  • Duties: what you will do in the role. They tell you which experiences or projects to prioritise.
  • Conditions: schedule, location, contract type or permits. They are not keywords; check them before applying.

Annotated posting 1: administrative assistant

This posting is fictional. Note duties, tools and conditions separately so you do not confuse knowing a program with being available at the requested hours.

Fictional exampleAdministrative assistant posting
We are looking for an administrative assistant to record invoices and maintain the digital archive. Excel skills to sort and filter lists and telephone support are required. Experience with an ERP is a plus. Morning hours.

MUST-HAVE: Excel (sorting and filtering), telephone support.
DUTIES: invoice recording, digital archive.
NICE-TO-HAVE: ERP; no specific product is named.
CONDITION: morning availability.
Fictional exampleRequirement, evidence and wording
Excel → expenses sheet from a class project → “Organised expenses in Excel with category filters”.
Telephone support → answering calls at the association → “Answered members' calls and noted their enquiries”.
Digital archive → association documents → “Filed documents in folders by activity and date”.
Invoice recording → course exercises only → “Training exercise in invoice recording”.
ERP → never used → do not list it as a skill.
Morning hours → clashes with classes → check whether the application is feasible.

Complete this mapping with your own evidence before writing. A missing word is not always a wording problem: it may be a skill you have yet to gain.

Annotated posting 2: shop assistant

The second posting, also fictional, shows that a duty is not always a requirement, and that a nice-to-have can stay off your resume if you do not have it.

Fictional exampleSports shop assistant posting
We are looking for a weekend shop assistant. Duties: serving customers on the shop floor, restocking and operating the till. Requirements: experience or training in customer service and availability on Saturdays and Sundays. Knowledge of sports equipment and basic English for serving tourists are a plus.

MUST-HAVE: customer service (experience or training), weekends.
DUTIES: shop floor service, restocking, till.
NICE-TO-HAVE: sports equipment, basic English.
COMMENT: operating the till is a duty learned on the job; if you have already done it, mention it.
Fictional exampleResume sentences for this posting
Customer service → “Served customers at the counter of the family business at weekends”.
Till → “Operated the till and balanced the cash at closing” (only if you did).
Sports equipment → “Have played for a basketball club for six years and know training equipment” (if true and relevant).
Basic English → state your real level; do not write “fluent” to fit.
Weekends → in the availability section, not as a skill.

Each sentence is a model. If you cannot explain the context in an interview, do not use it.

Where to include them without repeating the posting

In the profile, highlight the most relevant abilities. In projects or experience, explain how you used them. In skills, specify tools and tasks. You do not need every term in every section.

Keep official names for tools and qualifications. If you use an uncommon abbreviation, spell it out too. You can adopt the posting's vocabulary to describe an equivalent task, but not change a past job title to one you never held.

Fictional exampleBefore and after
BEFORE: Organised person with computer and communication skills.
AFTER: In a class project, organised an Excel expense register with supplier filters. Presented a summary of outstanding payments to the team.
WHY IT CHANGES: it states the tool, the context and the work done.

Next steps

What to avoid and how to review the result

Do not add hidden text, lists of programs you do not know or literal copies of the posting. A document that is hard to explain in an interview does not improve by containing more matches.

Read the resume without looking at the posting: it should make sense on its own. Then go back to the list of requirements and check that every claim is supported. If you use the checker, make sure its suggestions respect your level and the difference between academic practice and employment.

Next steps

Sources and references

Written and reviewed by the Keyverta team (OnruTech). The examples are fictional and no recommendation guarantees an outcome in a hiring process. How we work and contact

Related guides

See all guides