How to List Skills on a Resume
5 min read
Which skills belong on your resume, how to choose them from the job description, and how to format them so ATS and recruiters both find what they need.
Hard skills vs. soft skills
Hard skills are specific, teachable abilities (Python, financial modeling, phlebotomy). Soft skills are how you work (communication, leadership, problem-solving). Your skills section should lean heavily on hard skills — they’re what ATS filters search for — while soft skills are best demonstrated through your achievement bullets.
Mirror the job description
The fastest way to choose skills is to read the job posting and list the hard skills it names that you genuinely have, using the same wording. If the posting says "TypeScript," write "TypeScript," not "TS." ATS keyword matching is often literal.
Group skills for scannability
Instead of one long list, group related skills under labels:
- Languages: TypeScript, Python, SQL
- Frameworks & Tools: React, Node.js, Docker, AWS
- Methods: Agile, A/B testing, CI/CD
Don’t pad or lie
Only list skills you can speak to in an interview. A bloated skills list with abilities you can’t demonstrate is a fast way to lose trust. Quality and relevance beat quantity.
Put this into practice
Build an ATS-friendly resume on a live canvas — free, no sign-up.
Create my resume — FreeFrequently asked questions
How many skills should I list?
Typically 8–15, grouped into 2–3 categories. Enough to cover the role’s key requirements without padding.
Should I include proficiency levels?
It’s optional. For languages (spoken) and some technical tools it can help; for most skills, demonstrating them in your experience bullets is stronger than a self-rated bar.
Where should the skills section go?
Near the top for technical or skills-based roles; after experience for roles where work history is the main selling point.