Resume Skills: What to List and How to Organize Them
6 min read
The skills section looks like the simplest part of a resume and is the most commonly wasted. Done well, it feeds ATS keyword matching, tells recruiters in four seconds what you are, and sets up your interview. Done badly, it is a wall of every software title you have ever opened. Here is how to build a skills section that works.
Hard skills first, chosen by the posting
Hard skills are tools, methods, and domains: SQL, Figma, GA4, SOC 2 compliance, demand generation. These are what ATS searches and what recruiters scan for. Build your list from the posting first (their exact words), then add your genuine secondary skills.
Rule of thumb: 8-15 skills total. Fewer looks thin, more dilutes the ones you are actually great at. Every skill listed must be interview-safe: expect to be asked about anything on the page.
Organize by category, not alphabet
Grouped skills read as competence; flat lists read as dumping. Three or four labeled groups let a recruiter find your fit instantly and let parsers associate skills with context.
Analysis: SQL, Python, Excel (advanced), statistics Visualization: Tableau, Power BI, Looker Methods: cohort analysis, A/B test support, KPI definition
Soft skills: show, do not list
'Communication', 'leadership', and 'teamwork' listed bare are noise; everyone lists them. The professional move is to demonstrate them in bullets ('trained 9 new hires', 'ran steering committees for a 12-stakeholder program') and keep only role-relevant soft hybrids in the skills line (e.g., 'stakeholder management', 'incident communication').
Skill levels and honesty
Skip star ratings and percentage bars: they mean nothing to parsers and invite skepticism. Instead, control precision through grouping and wording. If you are beginner at something the posting needs, list it only if you can discuss it; otherwise leave it off and let your strengths carry the match.
Keep the skills section synchronized
Your three strongest skills should appear in the summary, the skills line, and at least one bullet each. That repetition is what makes a recruiter remember you as 'the Kubernetes person' rather than a generic applicant, and it satisfies keyword matching at the same time.
Key takeaways
- 8-15 skills, sourced first from the posting's exact vocabulary
- Group into 3-4 labeled categories
- Demonstrate soft skills in bullets instead of listing them bare
- No ratings or bars; only interview-safe skills
- Synchronize top skills across summary, skills, and bullets
Frequently asked questions
How many skills should be on a resume?
Eight to fifteen, grouped by category. The exact number matters less than coverage of the posting's core requirements plus one or two differentiators.
Should I list soft skills on my resume?
List only role-relevant hybrids (stakeholder management, incident communication) and prove them in bullets. Bare adjectives like 'team player' add nothing that recruiters trust.
Do skills go before or after experience?
After experience for most candidates, since experience is the evidence. Technical roles sometimes place a compact skills line above experience for instant fit-checking; both are acceptable if consistent.
Apply this to your resume now
Upload your resume and get a score, a roast, and a prioritized fix list built on these patterns. Free, no signup.
Check my resume freeRelated resume examples
Related guides
Fixed your resume? Now practice defending it.
VibeJudge handles resume preparation. When the resume is sharp, Rehearse helps you answer the questions a recruiter will ask about it.
Practice with Rehearse →