Resume Keywords: What ATS Scanners Look For
Resume keywords are the words from the job description that a recruiter types into the applicant tracking system (ATS) to find candidates: the job title, hard skills and tools, certifications, and the domain the role sits in. An ATS scanner checks how many of those words your resume contains, in the same wording the posting uses. The keywords that matter are the ones in the specific job description you're applying to, not a generic list, and they count only when they sit next to real evidence of the skill.
Want to see which keywords your resume is missing for a specific job? Paste the job description into the free ATS resume scanner. It lists the skills you match and the ones you are missing, no sign-up.
What counts as a resume keyword
Not every word in a job description is a keyword. Scanners, and the recruiters searching the ATS, focus on five kinds:
| Type | Examples | Why it matters |
|---|---|---|
| Job title | Frontend Engineer, Data Analyst, Product Manager | Recruiters often search by title first. A close title match ranks you up |
| Hard skills and tools | TypeScript, React, SQL, Kubernetes, Figma, Salesforce | The bulk of the match score; usually the "Requirements" list |
| Certifications | AWS Solutions Architect, PMP, CPA, Scrum Master | Often a hard filter: you have it or the search skips you |
| Domain and methods | B2B SaaS, payments, A/B testing, CI/CD, GDPR | Separates "knows the tool" from "has done this kind of work" |
| Seniority and scope | led a team of 5, owned the roadmap, on-call | Tells the reader which level you are, beyond the title |
Soft skills ("team player", "strong communicator", "detail-oriented") are rarely what anyone searches for. Leave them to your bullet points, where you can show them instead of claiming them.
How to find the keywords in a job description
You don't need a tool for this, just five minutes and the posting.
- Copy the job title exactly. "Senior Frontend Engineer" and "Senior Front-End Developer" are different strings to a search.
- Go through the requirements and list every noun that names a skill, tool, or certification. Skip adjectives and filler.
- Mark what appears more than once, or in both the summary and the requirements. Repetition is the posting telling you what matters most.
- Split must-haves from nice-to-haves. "Required" and "you have" lists come first; "bonus" or "nice to have" lists come second.
- Strike out everything you can't back up with real experience. That list is your gap, not your keyword list. See where the line is.
Here's what that looks like on a short example posting:
Senior Frontend Engineer. You'll build our customer dashboard in React and TypeScript, own our design system, and improve Core Web Vitals across the app. You have 5+ years of frontend experience, strong TypeScript, experience with GraphQL and testing (Jest, Playwright). Nice to have: Next.js, accessibility (WCAG), B2B SaaS.
The keywords: Senior Frontend Engineer (title); React, TypeScript, GraphQL, Jest, Playwright (tools, TypeScript twice so weight it); design system, Core Web Vitals, testing (methods); Next.js, WCAG accessibility, B2B SaaS (nice-to-haves). Everything else in the posting is context.
Where to put keywords on your resume
Keywords work best in the places both the scanner and the recruiter read:
- Headline or title line. Mirror the posting's title if it honestly describes you: "Senior Frontend Engineer", not "Creative Technologist".
- Summary. Two or three sentences naming your core stack and the kind of work you do. This is where the most important keywords go first.
- Skills section. A plain list of tools and technologies, grouped if it's long. Scanners pick up a dedicated skills section reliably; it's also the fastest place for a recruiter to check.
- Experience bullets. The keywords that count most sit inside a bullet with a result: "Cut dashboard load time by 40% by moving to Next.js server components and fixing Core Web Vitals regressions." That's a keyword and the proof in one line.
A keyword that only exists in your skills list and never shows up in your experience reads as a claim. One that shows up in a bullet with a number reads as evidence.
Use the posting's exact wording
Scanners match strings, and so does a recruiter typing a search. A few rules that cover most misses:
- Write acronyms both ways once: "Amazon Web Services (AWS)", "search engine optimization (SEO)". After that, either form is fine.
- Match the posting's spelling: if it says "Node.js", don't write "NodeJS"; if it says "front-end", use "front-end" at least once.
- Name the tool, not just the category: "CI/CD with GitHub Actions" matches both "CI/CD" and "GitHub Actions" searches. "Automated pipelines" matches neither.
- Keep the job title close to the posting's, as long as it's still accurate. A "Software Engineer II" applying for a "Backend Developer" role can write "Software Engineer II (Backend)".
How many keywords is too many?
There's no magic number. A useful target is to cover most of the posting's must-have keywords that you genuinely have, each in context at least once, and the important ones (the job title and the top two or three skills) two or three times across summary, skills, and experience.
Past that, more repetition doesn't help. A resume that lists the same tool eight times or carries a block of every technology you've ever touched reads as padding to the recruiter who opens it, and the recruiter is the one who decides. The keyword stuffing guide covers where tailoring ends and misrepresentation starts.
Should you bold keywords on your resume?
It makes no difference to the ATS: parsers extract the text and ignore formatting. For the human reader, bolding a few key results or technologies can help them scan, but bolding every keyword makes the page noisy and nothing stands out. If you bold anything, bold outcomes ("40% faster"), not skills.
What does matter to the parser is layout. Keep keywords in plain text: not inside images, text boxes, headers and footers, or multi-column tables, which some parsers read out of order or skip.
Resume keywords by role: examples
These are common must-have keywords in postings for a few roles. Use them to sanity-check your resume, not as a list to copy. The posting you're applying to always wins.
| Role | Common keywords |
|---|---|
| Frontend engineer | JavaScript, TypeScript, React, Next.js, CSS, accessibility (WCAG), Core Web Vitals, testing, design systems |
| Backend engineer | Python, Go, Java, Node.js, REST, GraphQL, PostgreSQL, microservices, AWS, Docker, Kubernetes |
| Data analyst | SQL, Python, Excel, Tableau, Power BI, dashboards, A/B testing, stakeholder reporting, statistics |
| Product manager | roadmap, discovery, user research, prioritization, OKRs, A/B testing, Jira, cross-functional, B2B SaaS |
| DevOps / platform | CI/CD, Terraform, Kubernetes, AWS, GCP, observability, incident response, on-call, Linux |
Check your keywords against a real job description
Doing the extraction by hand works. Doing it for every application is where most people stop tailoring. The free ATS resume scanner does the comparison for you: paste a job description, upload your resume, and see the skills you match, the ones you're missing, and an overall fit score. No account needed.
If the gaps are things you have but didn't write down, JobJam's resume optimizer rewrites your resume for that posting from your real experience and rescores it, so you can see the match improve before you apply. For the full picture of what scanners check beyond keywords, see how to improve your ATS score, and for a comparison of tools, the best ATS resume scanners.
JobJam uses a one-time credit model. No subscription, no auto-renewal. Try the scanner free → · See pricing