What belongs in a skills section
A skills section is a short list of the specific capabilities that make you qualified for the job you are applying to. It is not an inventory of everything you have ever learned. Three rules decide what to include.
- The skill must be relevant to the target job. If it does not appear in the posting or in related postings for the role, leave it out.
- The skill must be defensible. If an interviewer asks you to demonstrate it, you must be able to. Do not list skills you used once in a class project.
- The skill must be named the way the industry names it. If the posting says React, do not write JavaScript frontend library.
How to group skills
Long lists of unstructured skills are harder to scan and harder to parse. Group skills into categories that match the way recruiters and hiring managers think about the role.
Common groupings by role family
- Technology: Languages, Frameworks, Tools, Cloud and Infrastructure, Databases.
- Marketing: Channels, Tools, Analytics, Content, Strategy.
- Finance: Technical, Software, Reporting, Regulatory, Modeling.
- Healthcare: Clinical, Systems, Procedures, Certifications.
- Design: Tools, Methods, Disciplines, Prototyping.
- Management: Leadership, Functional, Tools, Methodologies.
When to use a single group
If you have fewer than ten skills, a single list is fine. Once the list runs past ten items, grouping helps the reader scan faster. Grouping also helps ATS systems categorize your capabilities into the right buckets.
How to format skills
Plain text lists
The safest format is a comma-separated plain-text list under each category heading. Example: Python, Go, TypeScript, SQL. This format parses cleanly in every ATS and reads quickly for humans.
Two-column skill blocks
For resumes with a sidebar, skills often appear in a two-column block. Keep the columns narrow enough that each skill stays on one line. Avoid wrapping skill names.
What to avoid
- Proficiency bars, star ratings, and percentage scales. These cannot be parsed by ATS and are subjective to human readers.
- Skill clouds or tag visualizations. They look modern but convey nothing useful.
- Icons standing in for skill names. Nobody can tell what a generic icon is supposed to mean.
- Emoji or decorative characters between skill names.
Spelling out acronyms
Write the first form out fully with the acronym in parentheses the first time a term appears, then use the acronym afterward. Example: Search Engine Optimization (SEO). This matches both forms in keyword searches so the ATS can find you regardless of which form the recruiter searches for.
The same rule applies to technologies that are commonly written in two ways: PostgreSQL (Postgres), JavaScript (JS), Kubernetes (K8s). Include both forms if the posting uses one of them.
Where skills should sit on the page
The position of the skills section depends on how central your skills are to the role.
- If skills are your strongest signal: place skills directly after the summary, before experience.
- If experience is your strongest signal: place skills after experience, before education.
- If you have strong certifications: place skills after certifications or in a sidebar.
- For entry-level and career-change candidates: skills often lead the resume after the summary.
How many skills to list
Eight to fifteen skills is the sweet spot. Fewer than eight makes the section feel thin. More than fifteen and the reader stops reading them. Focus on the ones that best match the target job.
If you genuinely have more than fifteen relevant skills, prioritize the ones from the job posting first, then fill in with the next most important. Never pad the list to reach a number.
Skills versus experience
Skills and experience serve different purposes. Skills tell the reader what you can do. Experience shows what you have done with those skills. A bullet under experience should show the skill in action, not just list it.
Example: Listing SQL as a skill is good. Writing a bullet that says Built a Snowflake warehouse querying 3TB of transactional data with SQL is stronger. The bullet proves the skill.
Skills to leave off
- Microsoft Office, unless the role specifically requires advanced Excel or PowerPoint.
- Email, unless the role is unusually specific about the platform.
- Typing speed, unless you are applying for transcription or data entry.
- Soft skills like teamwork or communication, unless you can back them up with specific evidence.
- Personal traits like hardworking or detail-oriented. These are claims, not skills.
- Operating systems, unless you are applying for IT support or systems administration.
Frequently asked questions
Should I list soft skills on my resume?
Only if you can back them up with evidence. Teamwork is weak on its own. Led a cross-functional team of twelve is strong. Prefer specific evidence over generic labels.
How do I show proficiency levels without bars?
Use words if you must: Expert, Advanced, Intermediate, Beginner. Or show proficiency through experience: 8 years of Go, shipped 3 production services in Go. The second approach is stronger.
Should I list every programming language I have used?
No. List the ones you would be comfortable using in a job. Depth in three languages reads stronger than familiarity with twenty.
Where should I put certifications, in skills or their own section?
Their own section if you have more than two. Certifications are a strong signal in many industries and deserve their own heading for ATS parsing.
Do I need a skills section if my experience bullets already prove the skills?
Yes. Skills sections help ATS keyword matching and give a recruiter a fast summary. Even if the experience proves the skills, the section helps the reader find them quickly.