Your resume skills section is the most-scanned part of your resume. Recruiters look here first to check off must-have tools and competencies. ATS systems keyword-match against it. Yet most candidates waste the section — either stuffing it with 40 vague skills or listing three things and moving on.
Here's how to build a resume skills section that survives ATS, helps recruiters, and doesn't read like a buzzword bingo card.
Hard skills vs soft skills
Hard skills are teachable and measurable: tools, languages, frameworks, methodologies, certifications. Soft skills are behavioral: communication, leadership, adaptability.
List hard skills in your skills section. Show soft skills in your bullets — "led a 6-person team" beats listing "leadership" ever could.
How many skills should you list?
Aim for 10-15 skills total, grouped into 3-4 categories. More than 20 starts to look like padding. Fewer than 6 makes the section look thin.
The point isn't to list everything you've ever touched. It's to surface the skills most relevant to the role you're targeting.
How to format your resume skills section
Group by category. A flat list of 15 tools is hard to scan. A grouped list tells a story.
- Languages: Python, JavaScript, SQL, Go
- Frameworks: React, Node.js, Flask, FastAPI
- Tools: Git, Docker, AWS, Tableau
- Methodologies: Agile, Scrum, A/B testing
Keep proficiency labels honest. "Familiar," "Proficient," and "Advanced" are all fine — "Expert" should mean you could teach it. If you can't answer a basic question about a skill, don't list it.
Resume skills examples by industry
Engineering
- Languages: Python, Go, TypeScript, SQL
- Backend: Node.js, FastAPI, gRPC, PostgreSQL
- Infra: AWS, Docker, Kubernetes, Terraform
- Practices: TDD, code review, on-call rotation
Design
- Tools: Figma, Sketch, Adobe XD, Photoshop
- Disciplines: Product design, design systems, prototyping, accessibility
- Research: User interviews, usability testing, surveys
- Code: HTML/CSS, basic React
Marketing
- Paid: Google Ads, Meta Ads, LinkedIn Ads
- SEO: Ahrefs, Semrush, content strategy
- Analytics: GA4, Looker, Mixpanel
- CRM: HubSpot, Marketo, Salesforce
Data & analytics
- Languages: SQL, Python, R
- Tools: dbt, Airflow, Snowflake, BigQuery
- Visualization: Tableau, Looker, Power BI
- Methods: A/B testing, causal inference, forecasting
Finance
- Accounting: QuickBooks, NetSuite, Excel modeling
- FP&A: Anaplan, Adaptive Insights
- Reporting: SEC filings, month-end close
- Certifications: CPA, CFA Level II
Project & program management
- Methodologies: Agile, Scrum, Kanban, Waterfall
- Tools: Jira, Asana, Linear, Smartsheet
- Practices: Roadmapping, stakeholder management, RACI
- Certifications: PMP, CSM, SAFe
How ATS reads your skills section
ATS software matches your skills against the job description. If the job posting says 'project management' and your resume says 'PM,' you might miss the match. Mirror the job description's vocabulary.
- Print the job description. Highlight every required skill, tool, and qualification.
- For each one, confirm you actually have it. If yes, make sure it's in your skills section or your bullets.
- Use the recruiter's exact phrasing. If they say 'stakeholder management,' don't write 'cross-functional collaboration.'
- Put skills in context. 'Python (built 3 production APIs)' beats a bare 'Python.'
Soft skills: how to show, not tell
Don't list soft skills in your skills section. Show them in your bullets with evidence.
- Leadership → 'Led a 6-person team through a 9-month product launch'
- Communication → 'Wrote technical specs reviewed by 15+ engineers'
- Problem-solving → 'Diagnosed and fixed a memory leak causing 5% daily crash rate'
- Adaptability → 'Shipped 3 product pivots in 18 months as strategy evolved'
A bullet with evidence is worth 10 adjectives in a skills list. We cover this in more depth in our resume mistakes to avoid guide.
Skills you should leave off
- Anything you can't back up in an interview
- Outdated tools (MS-DOS, Internet Explorer)
- Generic soft skills ('team player,' 'hard worker') — prove them in bullets
- Hobbies and interests unless directly relevant
- Skills that aren't relevant to the target role
The skills section checklist
Before you submit, run this:
- 10-15 skills total, grouped by category
- All skills relevant to the target role
- Vocabulary matches the job description
- No proficiency inflation
- Soft skills shown in bullets, not listed
- Skills you could actually answer a technical question about
“The skills section isn't a trophy case. It's a directory of the tools a recruiter needs to see to put you in the 'yes' pile.”
Tailoring your skills section per application
Keep a master skills list — every tool, language, framework, and methodology you've ever used. For each application, copy it and cut to the 10-15 most relevant. Twenty minutes of tailoring per application is plenty.
Your skills section is one of the few resume sections where more specific is always better. List the tools, group them logically, mirror the job description, and skip the adjectives. That's the entire playbook. ⚒️