Resume writing · Part of Resume writing guide
Resume Skills Section: What to List, How to Group It and What to Skip
By RedvicaUpdated October 4, 20266 min read
The skills section is a quick-scan list of the tools and abilities you can use. A recruiter or a parser can see at a glance whether you match the basics. It works best when it's short, relevant and backed up by your bullets. It fails when it's a long list of everything you've ever touched. This guide shows what to include, how to group it and what to leave out.
What the skills section is for
- Scanning: it lets a reader confirm the core requirements in seconds.
- Searching: recruiters can search resumes for terms, and some systems support keyword search (Greenhouse documents it: Greenhouse Support).
- Parsing: plain-text skills are easy for software to read, unlike icons or rating bars.
It doesn't replace proof. Each important skill should also appear in a bullet that shows you used it.
What to include
| Type | Examples | Notes |
|---|---|---|
| Tools and technologies | SQL, Power BI, Figma, Salesforce, AWS | The core of most skills sections |
| Hard skills and methods | Data visualization, A/B testing, financial modelling | Use the terms the postings use |
| Languages | Python, Java; or spoken languages with level | Separate programming and spoken languages |
| Certifications | PMP, Microsoft PL-300 | Or give them their own section |
| Soft skills | Stakeholder communication, mentoring | Use sparingly and prove them in bullets |
Group and order
Short lists can be a single line. Longer ones read better when grouped by type. Put the skills that matter most for the target job first in each group, then use the posting's wording for those you really have (keyword method).
| Role | Sample skills section |
|---|---|
| Data analyst | Languages: SQL, Python (basic) | BI tools: Power BI, Tableau (basic) | Other: Excel, KPI reporting, data cleaning |
| Software engineer | Languages: Java, Python, SQL | Frameworks: Spring, React | Tools: Git, Docker, AWS | Practices: CI/CD, code review |
| Marketing | Channels: Paid search, email, SEO | Tools: GA4, Google Ads, HubSpot | Methods: A/B testing, funnel analysis |
Proficiency: labels, not bars
Skill bars and star ratings are subjective, can't be read by a parser and invite questions (what does 4 out of 5 mean?). If level matters, use a plain word such as "basic", "working knowledge" or "advanced" next to the skill, and only where it adds honest information.
How many skills?
There's no verified magic number. Include the skills a posting for your target role would expect and that you genuinely have; a focused list is more convincing than a long one. If a skill isn't relevant to the jobs you're applying for, cut it.
Keep it consistent with the rest of your resume
- Every skill in the list should show up somewhere else: a bullet, a project or a certification.
- Don't list a tool you've only read about. Add it under a "Learning" line if relevant, or leave it out.
- Make sure your LinkedIn skills match (resume vs LinkedIn).
Mistakes to avoid
- A long, unfiltered list of every tool you've opened.
- Generic filler skills such as "Microsoft Word" for a technical role, unless the posting asks for them.
- Skill bars, stars, percentages or icons.
- Soft-skill lists with no evidence ("team player", "hard worker").
- Skills that don't appear in any bullet.
Not sure which skills are missing for a job? Job-specific tailoring lists matched and missing keywords against a posting. For the whole resume, see the writing guide.
Frequently asked questions
Should I include soft skills?
Sparingly, and show them in your bullets. A list of adjectives adds little.
Where should the skills section go?
Usually after experience, or higher up if you're early-career or the skills are your strongest evidence.
Do I need proficiency levels?
Only if they add honest information. Use plain words rather than bars or stars.
Can I list skills I'm still learning?
Label them honestly (for example "Python (learning)") or leave them for a projects section, rather than implying proficiency.