Module 5: Keywords and the Skills Section — Where Keywords Go and How to Find Them

← Return to the Resume Optimization Course #

ATS systems compare your resume text against the job description word-for-word. Using synonyms, even precise and accurate ones, costs you score points. A candidate who writes “containerized deployments” when the job says “Docker” may score 15–20 points lower than a candidate with identical experience who used the matching term.

This module takes about 10 minutes. After reading it, you’ll know how to extract keywords, where to place them, and how to structure a skills section recruiters can scan in 5 seconds.

How to Find the Right Keywords #

Step 1: Start with the Job Description #

Paste the full job description text. Look for:

• Repeated nouns and technical terms — if “Kubernetes” appears three times, it’s a required keyword
• Required vs. preferred qualifications — keywords mentioned in “required” sections are non-negotiable
• The exact job title they use — “Software Development Engineer,” “SDE,” and “Software Engineer” are different strings
• Tools and platforms listed — AWS, Salesforce, Tableau, PyTorch — use these exact strings

Step 2: Compare Against Your Resume #

Read your resume with the job description open. Make a list of:

• Terms in the job description that you have genuine experience with but haven’t mentioned
• Terms you’ve mentioned using a synonym the ATS won’t match

Step 3: Use the ATS Resume Improver #

Paste both documents into the ATS Resume Improver keyword gap view. It shows you every keyword present in the job description, which ones appear in your resume, and which ones are missing — including importance ratings when an AI provider is configured.

A keyword gap showing “Critical — missing from resume” means adding that term is worth doing now. “Low — missing from resume” means less urgent.

Where to Put Keywords #

Keywords belong in four places:

Put the most important keywords in at least two locations. A keyword appearing once is weaker than one appearing organically in the skills section and in a work experience bullet.

What Not to Do #

Don’t Keyword-Stuff #

Cramming keywords into sentences that don’t make sense hurts more than it helps.

“Managed Python Python Python Django REST APIs” — ATS may flag this as spam; human reader will reject immediately

Every keyword must appear in a grammatically sensible context. If you can’t work a keyword into a real sentence, put it in the skills section where a list format is expected.

Don’t Claim Skills You Don’t Have #

Keywords lead to interview questions. If you add “Machine Learning” as a keyword without being able to discuss it, you’ll fail the technical screen.

Only add keywords that represent genuine experience or knowledge you can speak to for 2+ minutes in an interview.

Don’t Skip Acronym Expansion #

Use both the spelled-out version and the acronym at least once each. ATS systems vary in how they handle acronym matching.

• “Kubernetes (K8s)” — covers both strings
• “Distributed Denial of Service (DDoS)” — covers both
• “Natural Language Processing (NLP)” — covers both

The Skills Section #

When to Include It #

Almost always. The skills section is one of the fastest ways to add keyword density and it’s the first place many technical recruiters scan. The only exception is highly executive roles where a skills section looks abbreviated — at that level, skills show up in the context of achievements.

How to Structure It #

Group by category, not in one flat list. A flat list of 30 skills is hard to scan and provides no context.

Languages:       Python, Go, TypeScript, SQL
Frameworks:      Django, FastAPI, React, Node.js
Infrastructure:  AWS (EC2, S3, RDS, Lambda), Terraform, Kubernetes, Docker
Tools:           GitHub Actions, Datadog, PagerDuty, Jira

This format:

• Makes it scannable in under 5 seconds
• Groups related terms (which helps context-aware ATS systems)
• Shows depth within categories

What to Leave Out #

Skills you’d be embarrassed to answer a question about. If you list Python and the interviewer asks you a basic Python question you can’t answer, you’ve lost the opportunity.

Tools you used once four years ago and barely remember. Listing them adds keywords but creates risk in the technical screen.

Soft skills as line items. “Communication,” “teamwork,” “leadership” — these belong in bullet points as demonstrated behaviors, not as items in a list. “Facilitated 50+ stakeholder interviews to define product requirements” is a better way to show communication than listing “Communication” in Your skills section.

Level Indicators (Optional) #

Most people skip level indicators, but they can add useful context and differentiate depth:

• “Proficient in Python, working knowledge of Go”
• “AWS (3 yrs), Azure (basic)”

Use them when the difference between depth levels matters for the role — for example, a job requiring “strong Python” where your Python is genuinely stronger than your other listed languages.

Keyword Gap Analysis with the ATS Tool #

Run the full keyword check using the ATS Resume Improver :

1. Upload your resume
2. Paste the job description
3. Open the Keyword Analysis tab
4. Review the gap list — add high-importance missing keywords where accurate

With an AI provider configured, you get semantic analysis: “Kubernetes — Strong match: found in Skills and 2 job descriptions” vs. “Docker — Critical gap: appears 4 times in job description, 0 times in resume.” This tells you exactly where to spend your editing time.

Run the check after every tailoring pass. A before-and-after comparison shows the scoring impact of each keyword addition.

Next Steps #

Keywords match you to the role. The next module covers the three main content sections in detail — Experience, Projects, and Education — and what each one needs to contain.

→ Module 6: Experience, Projects, and Education

Or return to the course hub: Resume Optimization Course Start