04 Sept 2026
Your resume is clean, the dates line up, and the experience genuinely matches the roles you apply to. You have sent it out forty times this quarter and heard back twice. Somewhere in that stretch, someone told you to add resume keywords, and the advice sounded reasonable until you sat down to do it. Which words in this job posting count as keywords? Do you copy them exactly or write them your own way? Where on the page do they go, and how many times is enough before it starts to look like padding?
Generic keyword lists do not answer any of that. A list of two hundred action verbs, or the fifty best terms for your industry, is written for nobody in particular, while the job description open in your other tab is written for one opening with one stack. The words that matter to this employer are already in front of you, in their wording and their order of priority.
This guide gives you a repeatable procedure instead of a word bank: four reading passes, a copy or rewrite decision for every term, a placement map, a repeat budget, and a short audit before you submit. Budget about twenty minutes the first time and closer to ten after that.
Quick answer: Resume keywords are the specific terms an employer uses in their own posting: tools, platforms, certifications, job titles, methodologies, and concrete responsibilities. Pull them from the posting itself rather than from a general list, copy tool and certification names in the employer's spelling, and rewrite duties and qualities in your own language of results. Each term belongs in the section where it reads naturally, repeated two to four times for the central requirements and once for narrow ones. If a phrase does not describe work you actually did, it does not belong on your resume no matter how often the posting repeats it.
A keyword is a term the employer uses to describe the work, and later uses to search for candidates. Once your application lands in a company's system, a recruiter filtering a large applicant pool may search by tool, certification, title, or platform rather than opening every file. Your resume surfaces in that search or it does not.
Missing a term is usually not a rejection, it is an absence. Your file sits in the pile, technically qualified, and never comes up in the search that would have pulled it out. Keywords fall into a few recognizable types, and the type tells you where a term appears in the posting and how to handle it later.
| Keyword type | Example | Where it lives in the posting |
|---|---|---|
| Hard skill | forecasting, A/B testing, accounts payable | Requirements block, first two or three bullets |
| Tool or platform | Salesforce, Jira, Excel, NetSuite, Figma | Lines that start with "experience with" or a tools paragraph |
| Certification or license | CPA, PMP, CDL, state nursing license | Qualifications, often flagged as required |
| Job title | Operations Coordinator, Support Specialist | The title field, plus "reports to" and "partners with" lines |
| Methodology or framework | Agile, GAAP, HACCP, Lean | Responsibilities and the paragraph describing the team |
| Measurable responsibility | monthly close, ticket triage, vendor onboarding | Responsibilities block, phrased as verbs |
Adjectives about you are not keywords. Hard working, detail oriented, self starter, team player: these are rarely the strongest searchable terms by themselves, and they take the space where a tool name could sit. If you cannot picture a recruiter typing it into a search box, it is filler.
Three companies can post the same title and want three different things. A marketing coordinator at a small software company may spend the week in a CRM, email automation, and campaign reporting. A marketing coordinator at a regional retailer may spend it on print production, store promotions, and vendor coordination. Same person could do either job, but the first five lines of the resume have to look different.
A universal keyword list can only be a starting vocabulary for a job family, useful while you are exploring roles. To see the terms that recur in your function before you open a specific posting, browse our breakdown of keywords by role, then come back to the listing for the version that counts.
Read carefully is not a procedure. Four passes is. Each pass has one job, and you finish it before starting the next one.
Split requirements from responsibilities. The requirements block gives you nouns: tools, certifications, systems, years of experience with a named thing. The responsibilities block gives you verbs and processes. Both produce keywords, and they land in different parts of your resume, so keep the two lists apart.
Sort must have from nice to have using the posting's own language. Required, must have, and minimum qualifications signal one tier. Preferred, a plus, and nice to have signal another. A required term you genuinely have should appear early and more than once. A preferred term you have can appear once, in your skills line.
Notice what repeats, then verify it. A tool that shows up in the summary, the responsibilities, and the qualifications is a signal worth following, not a verdict, since repetition sometimes comes from a template rather than from real priority. Check a repeated term against the requirements block and the job title. If it holds up in both, it belongs on your list.
Read for priority, not just for coverage. The title and the opening paragraph usually tell you what the role is really for. Use that as a reading order rather than a scoring rule: decide what the core of the job is, and let that shape which four or five terms you push to the top of your page.
The requirements block is not always where the important terms live. Watch the paragraph describing the team and the stack, since tool names often appear there and nowhere else. Watch the certifications line, sometimes buried in a compliance note at the bottom. Watch the phrasing inside the qualifications: "comfortable owning the monthly reporting cycle" is a responsibility keyword written as a sentence, and monthly reporting is the term you extract.
The output of your four passes is a short table you fill in for this posting. Five columns, one row per term, and one of those columns is the honesty check that keeps the rest of the process clean. Here is a filled example for a hypothetical operations coordinator opening at a mid size logistics company.
| Term | Type | Verbatim or rephrase | Do you actually have it | Destination section |
|---|---|---|---|---|
| NetSuite | Tool | Verbatim | Yes, three years | Skills, one experience bullet |
| Salesforce | Tool | Verbatim | Yes, daily | Summary, skills, one bullet |
| Excel (pivot tables, VLOOKUP) | Tool | Verbatim | Yes | Skills |
| Vendor onboarding | Responsibility | Rephrase into a result | Yes, ran it for two regions | Experience bullet |
| Inventory reconciliation | Responsibility | Rephrase into a result | Yes, monthly | Experience bullet |
| Lean Six Sigma Green Belt | Certification | Verbatim | No | Leave out for now |
| Cross functional collaboration | Soft skill | Rephrase | Yes, in practice | Bullet, shown not claimed |
| Operations Coordinator | Job title | Verbatim | Close, internal title differs | Headline |
| SOP documentation | Responsibility | Rephrase | Yes, wrote six | Experience bullet |
Twelve to eighteen terms is the working range. Below that you are probably missing the tools paragraph, and above it you are collecting noise that pushes you toward cramming terms into sentences that do not want them.
Extraction is one piece of a larger job. If you also need to reorder sections, rewrite your summary, and decide which roles to compress, the full tailoring process lives in our guide to matching a resume to a job description.
The rule is short: anything the employer treats as a fact gets copied in their spelling, and anything describing your behavior or results gets written in your own words. A tool has one name, a certification one acronym, a standard one number, so paraphrasing loses the match and gains nothing. Ownership, collaboration, and communication are different: they stay claims until you attach them to something that happened.
| Term type | Example from a posting | Verbatim or rephrase | Why |
|---|---|---|---|
| Software and platforms | Workday, Tableau, Shopify | Verbatim | One correct name, and it is what people search for |
| Certifications and licenses | PMP, CompTIA Security+, RN license | Verbatim | Credential names are checked, not interpreted |
| Standards and regulations | SOC 2, GAAP, OSHA 30 | Verbatim | The number is part of the term |
| Named methodologies | Agile, Scrum, Kanban, Lean | Verbatim | Recognized labels with fixed spelling |
| Job titles | Operations Coordinator | Verbatim where it is truthful | The title is a search term you cannot invent |
| Technical processes | month end close, ticket triage | Verbatim noun, your own verb | Keeps the match, keeps the sentence yours |
| Duties written as sentences | "own the vendor relationship" | Rephrase | Becomes evidence only when you add scope |
| Soft skills | cross functional collaboration | Rephrase | Show it inside an action, do not claim it |
| Culture language | fast paced, wear many hats | Skip | Not a searchable term |
Abbreviations. Give both forms once, then use the short one: Search Engine Optimization (SEO) in your summary or skills line, then SEO everywhere else. That covers you whether the recruiter searches the acronym or the full phrase.
Spelling. Match the employer's rendering exactly on names. Salesforce, not Sales Force. JavaScript, not Java Script. Power BI, not PowerBI. If the posting uses an internal shorthand you cannot decode, use the common industry name instead of guessing.
Every term type has a home where it looks natural, a backup spot, and at least one place where it looks staged. The same word in the wrong section reads as filler.
| Keyword type | Primary home | Secondary home | Do not put it here |
|---|---|---|---|
| Tool or platform | Skills section | One experience bullet where you used it | Summary, unless it is central to the role |
| Hard skill | Experience bullets | Skills section | A standalone list of adjectives |
| Certification | Certifications section | Headline, if it is the hiring trigger | Scattered through unrelated bullets |
| Job title | Headline or target title line | Experience entry | Invented for a job you did not hold |
| Methodology | Experience bullet describing how you worked | Skills section | Summary, where it becomes a buzzword |
| Responsibility | Experience bullets with scope attached | Summary, if it is the core of the role | Skills section as a bare noun |
| Soft skill | Inside a bullet that demonstrates it | Nowhere else | Skills section as a claim |
Your summary is three or four lines and carries two or three keywords without strain: the title you are targeting, the platform the job revolves around, and the domain. Everything else waits. A summary carrying six terms turns into a list with punctuation, which is the pattern a reader registers as padding.
A keyword in a bullet needs a verb in front of it and an outcome behind it. Reconciled inventory in NetSuite across two warehouses, cutting month end variance investigations. That sentence carries two terms and still describes work, unlike a bullet that lists tools you touched with no action attached.
For the rest of the map, keep it simple. Your headline holds the target title and at most one credential. Your skills section holds grouped tools and technical skills, usually twelve to twenty entries rather than sixty. Certifications, tools, and projects sections hold the terms that would look forced anywhere else.
Your job title is the one term you cannot invent your way into. Use the truthful version of what you did, and if your internal title does not match market language, the wording options are covered in our guide to job titles and resume headlines.
Forget density percentages. Think in repeats, and keep the budget small. A term at the center of the job can appear two to four times across the whole document: once in the summary, once in the skills section, and once or twice inside bullets where you actually did the work. A narrow or preferred term appears once, in skills, and that is complete.
The rule that governs all of it: every mention lives inside a true statement about your work. If a sentence exists only so a term can appear in it, the sentence is surplus and a reader will feel it even if they cannot name why.
Here is the difference in practice. Three appropriate mentions of Salesforce: one in your summary line about CRM driven operations, one in your skills group, one in a bullet about migrating a reporting workflow. Six inappropriate mentions: those three plus the term appended to two bullets where you only saw the dashboards, plus a repeat in a second skills subsection. Nothing there is a lie exactly, and all of it reads as strain.
Do not chase a match percentage as a goal. A scanner score mainly reflects text overlap, not whether the resume is persuasive, and that number tells you whether you missed something obvious, not whether a person will call you.
Stuffing is not a rule violation, it is a reading experience. Someone who screens resumes all week recognizes it by your second line.
Stuffed summary: Detail oriented Operations Coordinator with expertise in NetSuite, Salesforce, Excel, SQL, Tableau, Lean Six Sigma, vendor management, inventory reconciliation, SOP documentation, and cross functional collaboration in fast paced environments.
Honest summary: Operations coordinator with four years in logistics, running vendor onboarding and monthly inventory reconciliation in NetSuite for a two warehouse network.
The first version has more terms and less information. It says nothing about scale, ownership, or what you personally moved. The second carries three keywords and answers the only question the reader has at that moment.
The same thing happens with a skills section running sixty entries across five columns. It stops being a selection and becomes a dump, so nothing in it looks chosen. A grouped list of sixteen tools in three labeled clusters signals judgment instead.
A word on hidden text. Keywords pasted in white font or at one point size surface in ordinary ways: the document size does not match the visible content, selection reveals it, a plain text preview shows everything. When it surfaces, you have lost the trust of the recruiter holding your file, with no upside. This guide is not about getting past software. It is about describing your work in the words your reader already uses.
A list of terms is not a resume. The bridge is a simple pattern: the term, what you did with it, and the scope or result you could defend in an interview. Use this skeleton and fill the brackets from your own history.
[Action verb] [tool or method from the posting] to [what changed], [scope or number you can defend]
Coordinator, before: Responsible for vendor communication and purchase orders. After: Managed vendor onboarding in NetSuite for [number] suppliers, cutting average setup time from [X] to [Y] days.
Support specialist, before: Handled customer tickets and escalations. After: Triaged [volume] weekly tickets in Zendesk, resolving [percentage you can verify] at first contact and routing the rest against published SLAs.
Analyst, before: Created reports for management. After: Built [number] recurring Tableau dashboards for [team], replacing a manual spreadsheet process that took [hours] each month.
Administrative role, before: Managed calendars and office operations. After: Coordinated scheduling and travel for a [size] team in Workday and Concur, and documented [number] SOPs adopted across two offices.
Bullets lifted from the posting do not replace your numbers. The posting supplies vocabulary, not content. Copy a duty line straight across and you have written a job description, not a resume line. Keep their noun, supply your own verb, scope, and outcome.
Some required terms will not be yours, and inventing them creates a credibility risk and should be avoided. There are four honest options.
| Requirement you lack | Honest option | How it reads on the page |
|---|---|---|
| A tool you never used, but you used a close equivalent | Name what you actually used, with the function spelled out | "Managed pipelines in HubSpot" next to a CRM posting reads as transferable, not as a gap |
| A skill you built outside a job | Show the coursework, lab, volunteer, or freelance project | A project entry with scope and outcome, in the same format as a job |
| Industry specific phrasing you have not used | Translate your own work into the target industry's nouns | Same duty, their vocabulary, no invented experience |
| A hard credential you do not hold | Leave it out, apply anyway if the rest fits | A clean absence, which is normal, since matches are rarely complete |
If you are early in your career, one well described project usually changes how a resume reads more than another term added to a list. Give it a real entry with tools, scope, and result rather than a line in an interests section. For how to group technical and transferable skills, see our guide to choosing resume skills.
Sometimes the terms are right and the page hides them. This is not about your taste. Certain layout choices simply make text hard to extract, and the fix is usually small.
Text inside tables and text boxes can make reading order harder to preserve, so terms come out scrambled or drop entirely. Two column layouts have the same problem when a skills column sits beside an experience column. Headers and footers, including contact details, can be missed by some parsing workflows, so keep important terms in the main body. Skills rendered as an image, an icon row, or a rating bar carry no text at all. Renamed sections cause a quieter failure, where Where I Have Worked does not register as work history. Keep labels standard, keep terms in ordinary body text, and let the design live in spacing and typography. The mechanics are covered in our guide to building an ATS friendly resume.
On file format, follow the posting or the application form.
Run these seven checks on the finished document.
You can do all of this correctly and still get a rejection, or nothing at all. That is worth saying plainly, because the next instinct is usually to rewrite the resume a sixth time.
Some reasons have nothing to do with your vocabulary. Popular postings collect very large applicant pools within days. An internal candidate may already be far along. The role may be on hold, filled, or reposted. Location, work authorization, and seniority filters get applied before anyone reads a bullet. A posting that vanishes right after your rejection usually means the search closed, not that your terms were wrong.
When your resume is genuinely aligned and responses still do not come, the useful adjustments are upstream: which roles you choose, how early you apply, and whether you reach anyone besides the application portal.
Resume keywords are the specific terms an employer uses to describe a job and later uses to search their candidate database: tools, platforms, certifications, job titles, methodologies, and concrete responsibilities. They come from the posting in front of you, not from a general list. Missing one usually does not mean rejection, it means your file does not surface in the search that would have found it.
Extract twelve to eighteen terms per posting and place the ones you can actually back up. Central requirements can appear two to four times across the summary, skills section, and bullets, while narrow or preferred terms appear once. Adding more than that pushes you into sentences written for the terms rather than for the reader.
Read the posting in four passes: separate requirements from responsibilities, sort required from preferred using the employer's own labels, verify recurring terms against the requirements and the title, then read top down for what the role is really for. Also check the paragraph describing the team and the stack, since tool names often appear only there.
Not by itself. Three mentions spread across a summary, a skills line, and a bullet about work you did are normal. It becomes stuffing when a mention exists only to place the word, which is why the test is whether each sentence would still earn its space if the term were removed.
Match the spelling exactly for names and credentials: software, platforms, certifications, standards, and named methodologies. Give an acronym in both forms once, such as Search Engine Optimization (SEO), then use the short form. Duties and soft skills are the opposite case, since those should be rewritten in your own words with scope attached.
No. A sixty entry list reads as a dump and signals that nothing was selected, while a grouped list of roughly twelve to twenty tools and technical skills signals judgment. Keep it to what you could discuss in an interview, and let your experience bullets carry the rest.
Only as a starting point. Two postings with the same title often name different tools and priorities, so the core of your resume can stay fixed while five to eight terms in the summary, skills, and a couple of bullets change per posting. Keep every version consistent on dates, titles, and facts.
Run this sequence for each posting. The audit above checks a finished document, while this is the order of operations that gets you there.
04 Sept 2026
A five-minute routine for tailoring a resume: pull the real requirements out of the posting, change four things, and leave the rest alone. Includes a priority table, a master resume workflow, and a reusable checklist.
10 Sept 2026
Learn how to create an ATS-friendly resume with the right format, keywords, template, file type, examples, and practical optimization tips
10 Sept 2026
Discover the best skills to put on a resume, with 100+ hard and soft skill examples, job-specific lists, ATS tips, and advice for every career level
10 Sept 2026
Explore 50+ resume summary examples by industry and experience level. Learn how to write a strong, ATS-friendly professional summary for your resume
05 Sept 2026
A practical look at what makes a resume template parse cleanly, with five layouts you can rebuild yourself and a 12-point check to run before you apply.
09 Sept 2026
A recruiter-side look at how a software engineer resume is screened in seconds, with first-bullet keyword sets for full-stack, backend, and frontend roles. Includes a before-and-after bullet rewrite and a signal-to-line mapping table.
