Skills Section Done Right: What to Include (And What to Remove)
A step-by-step guide to building a resume skills section that passes ATS filters and impresses hiring managers. Learn what to include, what to remove, and see concrete examples.
Your skills section gets read twice. First by ATS software that filters resumes before any human sees them. Then by a recruiter spending about six seconds scanning your qualifications. Most skills sections fail both audiences.
This guide fixes that. You'll know exactly what to include, what to cut, how to format it, and what ATS systems actually scan for — with real examples by job type.
Hard Skills vs Soft Skills: What to Include
Hard skills are specific, teachable, and measurable. Python. Google Analytics. Financial modeling. SOLIDWORKS. These are what ATS systems scan for because they appear directly in job descriptions as requirements.
Soft skills are interpersonal. Communication. Leadership. Problem-solving. They matter to hiring managers, but ATS systems rarely filter on them. More importantly, listing "great communicator" proves nothing to anyone. Every candidate writes that.
Always lead with hard skills. Fill your skills section with concrete, technical competencies. Add soft skills only when the job description explicitly calls for them — and only two or three at most.
A good ratio is roughly 80% hard skills, 20% soft skills. For technical roles — engineering, data, IT — push that to 90/10.
Hard skills worth including:
- Tools and software (Salesforce, Figma, Tableau, HubSpot)
- Programming languages and frameworks (Python, React, SQL, TypeScript)
- Industry methodologies (Agile, Six Sigma, GAAP, IFRS)
- Certifications (AWS Certified Solutions Architect, PMP, CPA)
- Platforms and systems (Shopify, SAP, Workday, Snowflake)
Soft skills worth including — sparingly:
- Cross-functional collaboration — if the role explicitly requires it
- Executive communication — for senior and client-facing roles
- Team leadership — only if backed up by your experience bullets
If you list a soft skill, you need to prove it somewhere in your work experience. "Leadership" means nothing without a bullet like "Led a team of 8 engineers to ship a product three weeks ahead of schedule."
Skills That ATS Systems Look For
ATS systems work by matching keywords in your resume to keywords in the job description. No match — no interview. It's that mechanical.
There are four categories of skills that score well in ATS parsing:
Exact tool and software names. ATS doesn't always know that "MS Excel" and "Microsoft Excel" are the same thing. Use the exact phrasing from the job description. If they write "Salesforce CRM," you write "Salesforce CRM."
Both abbreviations and full names. Write "Search Engine Optimization (SEO)" the first time you use the term. This catches both search patterns. Same with "Pay-Per-Click (PPC)" or "Project Management Professional (PMP)."
Industry-specific methodologies. Agile. Scrum. Kanban. Six Sigma. ITIL. DevOps. These are high-weight keywords in their respective industries. If you know them, list them by name.
Role-specific platforms over generic categories. "CRM software" is vague and scores low. "HubSpot CRM" and "Salesforce" are specific and searchable. Always name the actual tool.
One critical mistake to avoid: keyword stuffing. Listing 40 skills in a dense block doesn't improve your ATS score. Most modern systems score on relevance and match quality, not raw volume. 12 highly relevant skills consistently outperform 40 generic ones.
Before you apply anywhere, check your resume ATS score free — it shows exactly which keywords are missing against the job description you're targeting.
Skills to Remove Immediately
A cluttered skills section hurts you in two ways. It dilutes the keywords that actually matter. And it signals to recruiters that you haven't tailored your resume.
Cut these now:
Generic soft skills with no proof. "Team player." "Hard worker." "Detail-oriented." "Self-starter." Every single candidate writes these. They communicate nothing. If you're detail-oriented, prove it with an accurate, well-formatted resume — not by claiming it in a list.
Universal computer skills. Microsoft Word. Email. Google Docs. Internet browsing. These are assumed for any office role. Listing them wastes space and makes your resume look like it was written in 2009.
Obsolete technologies. "Proficient in Windows XP." "Experienced with Adobe Flash." Unless a job description explicitly asks for a legacy system, these don't belong. They can make recruiters question how current your knowledge actually is.
Skills you can't defend in an interview. If "machine learning" appears on your resume, expect questions about model evaluation, overfitting, and cross-validation. Only list what you can actually discuss. Exaggerating proficiency backfires fast — and visibly.
Overly broad category labels masquerading as skills. "Marketing" is not a skill. "Microsoft Office" is not a skill. Break these down into specific tools: "Content Marketing," "Meta Ads Manager," "Excel (PivotTables, VLOOKUP, Power Query)."
When in doubt, ask yourself: Would a recruiter specifically filter applicants on this keyword? If the answer is no, remove it.
How to Format the Skills Section
Formatting matters more than most candidates realize. A disorganized skills section won't get read — even if the underlying skills are strong.
Placement. For most roles, put the skills section directly below your professional summary. This places your most relevant keywords in the top third of the page — where both ATS and recruiters prioritize their attention. Senior professionals with 15+ years of experience can place it after their work history, since their career record carries more weight.
Use categories, not a wall of text. Group related skills under short headers. This makes the section scannable in two seconds rather than ten. Two to four categories is the right range.
| Format | Human-Readable | ATS-Friendly |
|---|---|---|
| 30 skills in one unparagraphed block | No | Partially |
| 2–4 categories with 4–6 skills each | Yes | Yes |
| Visual skill bars or percentage meters | Looks modern | No |
| Single inline comma-separated list | Moderate | Yes |
Skip the skill bars. Visual proficiency meters — the kind showing "Python: 80%" — look polished but communicate nothing useful. Who decides what 80% means? Recruiters ignore them. ATS systems can't parse the data inside them. Use plain text only.
Target 10 to 15 skills total. Fewer than 8 looks thin. More than 20 looks like padding. Spread them across your 2 to 4 categories so each group has 4 to 6 items.
Use simple formatting only. Multi-column layouts and decorative tables often break ATS parsing. A clean, single-column format with plain text category labels reads correctly every time. The goal is to be parsed, not to look impressive on screen.
Skills by Job Type (With Examples)
The right skills depend entirely on the role. Here's what strong, tailored skills sections look like across the most common job types.
Marketing
Digital Marketing: SEO/SEM, Google Analytics (GA4), Email Marketing (Mailchimp, Klaviyo), Content Strategy, Meta Ads Manager, A/B Testing
Tools: HubSpot, Canva, Adobe Creative Suite (Photoshop, Illustrator), WordPress, Hootsuite
Analytics: Conversion Rate Optimization, Campaign Reporting, Customer Segmentation
Software Engineering
Languages & Frameworks: Python (Django, FastAPI), JavaScript (React, Node.js), TypeScript, SQL
Infrastructure & Tools: AWS (EC2, S3, Lambda), Docker, Kubernetes, Git, CI/CD Pipelines
Practices: Agile/Scrum, Test-Driven Development (TDD), REST API Design, Code Review
Finance & Accounting
Technical Skills: Financial Modeling, DCF Analysis, Excel (PivotTables, Power Query, Macros), SAP, QuickBooks
Compliance & Reporting: GAAP, IFRS, SOX Compliance, Financial Statement Analysis, Variance Analysis
Tools: Bloomberg Terminal, Tableau, Power BI
Project Management & Operations
Methodologies: Agile, Scrum, Waterfall, Kanban, Six Sigma (Green Belt)
Tools: Jira, Asana, Monday.com, Microsoft Project, Smartsheet
Skills: Budget Management, Stakeholder Communication, Risk Assessment, Resource Allocation, Vendor Management
Data & Analytics
Languages & Tools: Python (Pandas, NumPy, Scikit-learn), R, SQL, Tableau, Power BI
Data Engineering: ETL Pipelines, Apache Spark, Snowflake, BigQuery, dbt
Methods: Statistical Modeling, A/B Testing, Regression Analysis, Data Visualization, Predictive Analytics
Notice the pattern across every example: specific tool names, not generic labels. "Data analysis" is not a skill. "Python (Pandas, NumPy)" is. The difference is the difference between getting filtered out and getting a call.
Frequently Asked Questions
How many skills should I list on my resume?
10 to 15 is the target range, organized into 2 to 4 categories. More than 20 starts to look like padding. Fewer than 8 looks thin for most roles. Quality and relevance always beat volume.
Should I change my skills section for every job application?
Yes. ATS systems match your resume against each specific job description. A skills section tailored to the role you're applying for consistently scores higher than a generic one. Even small keyword adjustments — swapping "project management" for "program management" — can make the difference.
Where is the best place to put the skills section on a resume?
Directly below your professional summary for most candidates. This puts key qualifications in the top third of the page, where both ATS systems and recruiters look first. Senior professionals with extensive work histories can place it after the experience section, since their track record carries more weight than a skills list.
Can I list skills I'm still learning?
Yes, but label them honestly. Use "Familiar with" or "Currently learning" for skills you're still developing. Don't position them at the same level as your proven competencies. Misrepresenting proficiency gets exposed fast in technical interviews.
Do ATS systems parse skills listed in tables or multi-column layouts?
Not reliably. Many ATS systems struggle with multi-column formats and complex tables. Simple, single-column plain text parses correctly every time. It looks less visually interesting but it reaches the recruiter, which is the whole point.
What's the difference between a skills section and a core competencies section?
They serve the same purpose. "Core Competencies" tends to appear on executive resumes and often blends hard and soft skills. "Skills" or "Technical Skills" is more common for individual contributor roles and leans heavily on hard skills. The label matters less than the content inside it.
Should I include a separate technical skills section?
Yes, for technical roles. Engineers, data professionals, and IT candidates benefit from a dedicated "Technical Skills" section because recruiters in those fields scan for specific tools and languages before reading anything else. For non-technical roles, a single unified skills section is cleaner.