Most ATS keyword articles treat all keywords equally. They're not.
ATS systems extract keywords from the job description and weight them based on where they appear: job title > required qualifications > preferred qualifications > job description body. A keyword in the required qualifications section scores more heavily than the same keyword appearing once in the role description. That distinction changes which terms you prioritize — and where on your resume you put them.
The implication: before you pull keywords from a JD, scan its structure first. Required qualifications keywords belong in your Skills section and your first experience bullet. Preferred qualifications keywords go into supporting bullets. Body keywords are good-to-have but not worth forcing.
The lists in this post are organized by weight. Use them in that order. For how ATS weights keywords by section in more detail, the pillar post covers the full mechanics.
One more distinction worth making before the lists: not all keywords are universal. A Series B startup's ATS is often configured more aggressively around tool-specific and metrics keywords because the hiring team is small and screening for immediate contribution. An enterprise ATS is more likely to weight process and methodology terms — Agile, stakeholder management, compliance — because those roles require navigating existing systems. The category notes below flag which terms are universal and which are more context-dependent.
One more note before the lists: if your keywords came from an AI builder rather than the specific JD, the list below is a starting inventory, not a copy-paste source. Read why an AI-generated keyword list scores lower than a JD-specific one — and how to close that gap in one step.
Software Engineer ATS Keywords
Category 1 — Core technical skills (Highest ATS weight — these appear in job title and required qualifications sections)
`Python`, `JavaScript`, `Java`, `TypeScript`, `SQL`, `REST APIs`, `GraphQL`, `Git`
These are the terms that appear in the job title line or the first bullet of required qualifications. If any of these apply to you and aren't on your resume, they're costing you score on every application you submit.
Category 2 — Infrastructure and systems (High weight for senior roles — typically in required qualifications)
`AWS`, `GCP`, `Azure`, `Docker`, `Kubernetes`, `CI/CD`, `Terraform`, `infrastructure-as-code`, `microservices`
Missing tool-specific keywords in this category — Docker, Kubernetes, CI/CD — reduces ATS scores by 30+ points (ResumeAdapter 2026 analysis). These are not vague skills. They're named tools. Adding one named tool you genuinely have experience with can swing a 61% score to 78%. Note: these terms are near-universal for startups and growth-stage companies. Enterprise ATS systems are more variable — some weight cloud provider certifications (AWS Certified, GCP Professional) over raw tool mentions.
Category 3 — Scale and performance indicators (Use as phrases in bullet context, not just as keywords)
"distributed systems," "high availability," "99.9% uptime," "horizontal scaling," "latency optimization"
ATS systems trained on engineering JDs weight these phrases because they signal production experience, not academic knowledge. They belong in experience bullets, not in the Skills section: "Optimized service for 99.9% uptime across distributed systems handling 2M daily requests" scores differently than a lone keyword in a list.
Category 4 — Process and collaboration (Lower weight but necessary for completeness — typically in preferred qualifications or body)
`Agile`, `Scrum`, `code review`, `pair programming`, `technical documentation`
These are near-universal requirements but low-differentiating — almost every candidate includes them. They matter for completeness, not for competitive advantage.
Note for after ATS: Engineering managers reviewing 500+ resumes report scanning for three things in under 10 seconds — system scale (users, requests, data volume), technical decision ownership (you architected it, not just implemented), and measurable impact (performance improved by X%). The keyword list gets you read. These three patterns determine what happens next (Mentorcruise / Tech Interview Handbook).
Product Manager ATS Keywords
Category 1 — Core strategy keywords (Highest ATS weight — appear in job title and required sections)
`product roadmap`, `go-to-market`, `GTM`, `OKRs`, `KPIs`, `product vision`, `product strategy`
These terms define the role at the top of the JD. If your resume uses "strategic planning" instead of "product strategy" or "goals" instead of "OKRs," you're not matching the strings the ATS is scoring against.
Category 2 — Execution keywords (Required qualifications territory)
`Agile`, `Scrum`, `user stories`, `backlog`, `sprint planning`, `A/B testing`, `feature prioritization`
These appear consistently in the required section across PM JDs at Series A through enterprise. They're expected — not having them is a gap; having them doesn't differentiate you.
Category 3 — Metrics and outcomes (High weight for growth-stage companies — often in required qualifications)
`user retention`, `churn rate`, `DAU`, `MAU`, `NPS`, `conversion rate`, `ARPU`, `LTV`
Growth-stage ATS systems are often configured to score heavily on metrics language because the companies are hiring for quantitative rigor, not just product thinking. Missing this category is a consistent source of score gaps on startup PM applications. Enterprise PM roles are less likely to weight ARPU and LTV heavily — they'll weight process and governance keywords instead, which fall into Category 2.
Category 4 — Tools (Where 30+ point score gaps occur — ResumeAdapter 2026)
`Jira`, `Confluence`, `Figma`, `Amplitude`, `Mixpanel`, `Productboard`, `Notion`, `SQL`, `Looker`
This is the category where most PM resumes fail. A PM with 8 years of experience who doesn't list Amplitude — or a comparable analytics tool — scores significantly lower on any modern startup ATS, even if they've been running analytics their entire career using a different tool. The fix is simple: list the tool name, even if you used it only once. The keyword match matters.
Running the right keywords isn't enough if they're matched to the wrong JD. RolePitch extracts the exact keywords from the specific job you're applying to and shows you which ones you're missing. Paste the job link — see your gaps in 60 seconds. Try it free →
Marketing Manager ATS Keywords
Category 1 — Channel keywords (Highest weight — appear in required qualifications)
`SEO`, `SEM`, `paid search`, `email marketing`, `content marketing`, `social media`, `performance marketing`, `growth marketing`
Channel keywords are the most role-defining terms in a marketing JD and almost always appear in required qualifications. The specific channels listed tell you exactly which ones to prioritize on your resume — don't list all channels equally if the JD emphasizes three.
Category 2 — Analytics and measurement (High weight for data-driven roles)
`Google Analytics`, `GA4`, `conversion rate optimization`, `CRO`, `CAC`, `ROAS`, `attribution modeling`, `A/B testing`
GA4 specifically is worth calling out: many marketing resumes still list "Google Analytics" without specifying GA4, and some ATS systems score these as distinct keywords. List both if accurate.
Category 3 — Strategy and GTM (Appears in senior role JDs — required and preferred qualifications)
`go-to-market strategy`, `ICP`, `positioning`, `campaign management`, `demand generation`, `marketing automation`, `HubSpot`, `Salesforce`, `Marketo`
Tool names in this category — HubSpot, Salesforce, Marketo — follow the same logic as the PM tools category. A missing tool name is a missing keyword match, regardless of whether you've done equivalent work in a different platform.
How to Use This List Without Keyword Stuffing
Copying the full keyword list and pasting it into a Skills section is the most common mistake. ATS systems are getting better at detecting keyword stuffing — and even where they don't penalize it, the human who reads after ATS will.
Rules for natural integration:
- Use each keyword in context at least once — in an experience bullet or your summary — before listing it in Skills
- If the JD uses a keyword 4 times, aim to use it 3–4 times across your resume (keyword density, not padding)
- Use both the acronym and the expanded form at least once: "OKR (Objectives and Key Results)" — ATS systems match both, and some only match one
- Don't add keywords for tools you've genuinely never used. A competent interviewer will expose it in 60 seconds.
Before applying, also make sure the format doesn't break keyword parsing — a resume with the right keywords in the wrong structure still scores poorly.
97% of Fortune 500 companies use ATS to filter PM and software engineer resumes (ResumeAdapter 2026). The keyword gaps in this post are not edge cases — they're what's separating applicants who get read from applicants who don't.
Running the right keywords isn't enough if they're matched to the wrong JD. RolePitch extracts the exact keywords from the specific job you're applying to and shows you which ones you're missing. Paste the job link — see your gaps in 60 seconds. Try it free →
Sources
- ResumeAdapter 2026: missing tool-specific keywords reduces ATS scores by 30+ points
- ResumeAdapter 2026: 97% of Fortune 500 use ATS to filter PM and SWE resumes
- Mentorcruise / Tech Interview Handbook: engineering manager scanning patterns (system scale, decision ownership, measurable impact)
- RolePitch analysis: 61% median match score before tailoring across 4,000+ applications
Once you know which keywords are missing, reading your full ATS score report shows you how to weight which gaps to fix first.
Find out if your resume can pass ATS.
Upload your resume — RolePitch checks parseability, keywords, structure, and impact before you apply.
Check my ATS score free →