The skills section is one of the most important parts of your resume — and one of the most misunderstood. Many candidates either list too few skills, too many vague ones, or format them in a way that confuses applicant tracking systems.
This guide explains how to choose the right skills, where to put them, and how to present them so both ATS software and human recruiters respond positively.
Hard Skills vs. Soft Skills
Hard skills are specific, teachable abilities: Python, Adobe Illustrator, financial modelling, SQL. Soft skills are interpersonal and behavioural: communication, teamwork, problem-solving.
Prioritise hard skills on your resume. ATS systems are designed to scan for specific technical keywords — they cannot reliably evaluate "strong communicator." Soft skills belong in your summary or work experience bullets where you can demonstrate them with context, not just claim them.
How to Choose Which Skills to Include
The golden rule: mirror the job description. Open the job posting, identify every skill, technology, and tool mentioned, and include the ones you genuinely have. Use the exact phrasing from the posting — not synonyms.
- Job says "data analysis" → write "data analysis" (not "analyzing data")
- Job says "React.js" → write "React.js" (not just "React")
- Job says "stakeholder management" → write "stakeholder management"
- Job says "Google Analytics" → write "Google Analytics" (not just "analytics tools")
How to Format Your Skills Section
The most ATS-friendly format is a simple categorised list. Group related skills under a clear category name, then list them as comma-separated values or tags.
- Programming Languages: Python, JavaScript, TypeScript, SQL
- Frameworks & Libraries: React, Node.js, Django, FastAPI
- Tools: Git, Docker, Figma, Jira, Notion
- Cloud: AWS (EC2, S3, Lambda), Google Cloud Platform
Avoid using star ratings, progress bars, or percentage scores for skill levels (e.g. "Python ★★★★☆"). ATS cannot parse these and they look unprofessional to experienced recruiters.
How Many Skills Should You List?
For most professionals, 15–25 skills is the right range. Too few looks thin. Too many (50+) looks like keyword stuffing and reduces credibility. Focus on relevance over volume.
Where to Put Your Skills on the Resume
For most roles, place the skills section after your work experience. Recruiters want to see your experience first. The exception is for very technical roles (software engineering, data science) or fresh graduates — in those cases, skills near the top makes sense.
Skills to Avoid Listing
- Microsoft Word / Excel — too basic unless the job specifically requires advanced spreadsheet skills
- "Hard worker", "Team player", "Good communicator" — unverifiable claims
- Outdated technologies (Flash, Internet Explorer compatibility) — makes you look out of date
- Obvious skills for your field — listing "email" as a skill for a marketing role wastes space
Example Skills Section (Software Engineer)
- Languages: Python, JavaScript, TypeScript, Go
- Frontend: React, Next.js, Tailwind CSS
- Backend: Node.js, FastAPI, PostgreSQL, Redis
- DevOps: Docker, Kubernetes, AWS, CI/CD (GitHub Actions)
- Tools: Git, Figma, Jira, Postman
Build your skills section with ResumiQ.online — add categories, tag skills, and export a clean ATS-ready PDF for free.
Build My Resume Free →