How to List Skills on a Resume
5 min read
Learn which skills belong on a resume, how to choose them from the job description, and how to group them for recruiter and software searches.
Hard skills vs. soft skills
Hard skills are specific abilities such as Python, financial modeling, or phlebotomy. Soft skills describe how you work, such as communication, leadership, and problem-solving. Job-specific hard skills are often useful search terms, while soft skills are usually stronger when your experience demonstrates them.
Mirror the job description
Read the posting and list the hard skills it names that you genuinely have. Use clear, recognizable wording, such as "TypeScript" rather than an internal abbreviation. Employer search settings vary, so exact terminology can help without guaranteeing a match.
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 watermark.
Create my resume — FreeFrequently asked questions
How many skills should I list?
Use a focused list that covers the role’s important requirements without padding. For many resumes, 8–15 skills grouped into two or three categories is a readable starting point.
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.