How to write the skills section of a resume
The skills section is a quick reference. It lets a reader confirm, in one quick glance, that you have the tools, methods and certifications a role needs, before they read any of the details underneath.
It works best when it is short, grouped and honest. A long dump of every program you have ever opened simply adds noise. A focused list that matches your actual experience adds real credibility to the page.
What belongs in the section
List skills a hiring manager could reasonably ask you about: software, equipment, methods, languages, licenses and certifications. These are concrete and checkable. They also tend to be the terms a posting uses, which helps both people and screening software find a match.
Leave out anything you could not discuss for two minutes. If you used a tool once years ago, either omit it or label your level honestly. The section should reflect what you can do today.
- Microsoft Office
- Teamwork
- Hard worker
- Excel
- Windows
- Communication
- Photoshop (once)
- Problem solving
- SQL
- Tableau
- Excel (pivot tables)
- Looker
- Stakeholder reviews
- Python
- dbt
- Git
Hard skills, soft skills and where each goes
Hard skills are teachable and often testable, such as using a spreadsheet function, operating a machine or writing in a programming language. They belong in the skills section. Soft skills like communication or leadership are harder to claim in a word.
Show soft skills through your bullets instead. A line about training six new hires says more than the word leadership in a list. If a posting stresses a soft skill, prove it in experience and let the skills section stay concrete.
- SQL and Python
- Tableau and Looker
- Salesforce
- Six Sigma Green Belt
- Communication: briefed 40 stakeholders a month
- Leadership: mentored 3 new analysts
- Problem solving: halved report errors
Grouping and ordering
Group skills under short labels so the section scans quickly. The right labels depend on your field: tools, methods, languages, clinical systems or equipment. Three to five groups is usually enough, with the most relevant one first.
Within each group, put the skills the job asks for first. Spell out acronyms once if they are not universal in your field, and use the official name of tools so they are easy to recognize.
- SQL
- Tableau
- Looker
- Python
- dbt
- Git
- A/B testing
- Forecasting
Showing level without rating bars
Skill bars, stars and percentage scores are subjective and carry no real meaning. A reader cannot tell what eighty percent in a program represents, so they tend to ignore the graphic or doubt it.
Show depth with plain words if needed, such as advanced, working knowledge or familiar, and back it up with experience. Another option is to note how you used the skill, for example by naming the type of project or the volume of work.
Python 80% · SQL 60%
Python: built 12 data pipelines in 3 years
Show level through what you built, not a score.
Matching the posting honestly
Read the job description and note the tools and methods it names. If you genuinely have them, make sure they appear in your skills section using the same wording. This helps both a human reader and any software that scans for terms.
If you lack a listed skill, do not add it. Instead, highlight related experience that shows you can learn quickly. Honest overlap holds up in interviews, while stretched claims tend to fall apart on the first follow-up question.
SQL reporting
SQL: weekly sales reports
Tableau dashboards
Tableau: 6 dashboards for regional leads
Experience with Snowflake
Not used it yet, so leave it off
See it in real resumes
- Salesforce
- Agency management
- Budget management
- Lifecycle marketing
- Marketo
- Sales enablement
- SEO
- Team leadership
- Forecasting
- GA4
- Google Ads
- HubSpot
- Positioning
- Shopify
Run your draft through this
Checklist
- Every skill listed is one you could discuss or demonstrate today
- Skills are grouped under short labels instead of one long run
- The group matching the job's main needs appears first
- Each major skill also shows up in at least one bullet
- Tool names use their standard spelling and wording
- There are no rating bars, stars or percentage scores anywhere
Common slips
- Listing every program you have ever opened, including ones you barely used.
- Using rating bars or percentages that mean nothing to a reader.
- Filling the section with vague traits like team player and hard worker.
- Adding skills from the posting that you do not actually have.
- Burying the most relevant skills at the end of a long list.
FAQ
How many skills should I list?
Enough to cover what the job needs, and no more. For many people that means somewhere between eight and fifteen well-chosen items in a few groups. A shorter list you can fully defend is more useful than a long one that raises doubts.
Should I include soft skills in the skills section?
Usually it is better to demonstrate them in your bullets. Words like communication or teamwork are easy to claim and hard to verify. If you do list one, make sure at least one bullet gives a concrete example of using it.
Where should the skills section go on the page?
It depends on your field and experience. People whose tools are central to the job often place it near the top. Others put it after experience or beside education. Choose the spot that helps a reader confirm your fit quickly for the role.
More resume guides
- How to tailor a resume to a job descriptionAdjust your resume to each posting by reordering and rewording real experience, never stretching it.Read the guide
- How to write resume bullets that show resultsTurn a list of duties into bullets that show what changed because of your work.Read the guide
- Resume format, length and layoutChoose a clean layout, a sensible length and readable type so your content does the talking.Read the guide
Read a complete resume written this way.
Every example on ResumeGeenie uses the XYZ formula, with the reasoning shown beside it.
