How to List Skills on a Resume
By Muhammad Ali, Founder of InstantCV · Last updated: September 15, 2026 · 7 min read
List eight to fifteen skills in two or three named groups — tools, technical skills, and role-specific methods — using the same words the job posting uses. Prove the important ones inside your experience bullets rather than only naming them, and never use rating bars, percentages or star charts.
Where should the skills section go?
Directly under your work experience for most people, and directly under the summary if you are changing careers, returning after a break, or applying for a technical role where the tool list is the first screen. Either position parses correctly; what matters is that the section is a plain list under a heading called "Skills".
Keep it to a compact block of eight to fifteen entries. A thirty-item list reads as unfiltered, and the reader stops trusting any single item on it.
Which skills belong on a resume?
The ones the posting names, that you can defend in an interview, and that not every applicant will have. Skip anything assumed at your level — email, Microsoft Word, "internet research" — because listing the baseline suggests it is your ceiling.
| Type | Include? | How to write it |
|---|---|---|
| Software and tools | Yes, always | Name versions or modules where they matter: "SAP FI/CO", "Excel (Power Query, pivot tables)" |
| Technical methods | Yes | Name the method, not the buzzword: "multivariate testing", "variance analysis" |
| Certifications and licences | Yes, in Education | With issuer and expiry: "CPR/AED, American Heart Association, exp. 2027" |
| Languages | Yes, if relevant | By level: "Spanish — professional working proficiency" |
| Soft skills | Sparingly | Two or three at most, and only ones the posting names; prove them in bullets |
| Baseline office software | No | Assumed at every level; it dilutes the list |
| Skills you have read about | No | Anything you cannot answer a follow-up question on |
How do you group skills so the section is readable?
Use two or three labelled groups on one line each. Grouping tells the reader what kind of practitioner you are before they read a single item, and it lets a recruiter find the one thing they are scanning for in a second.
Grouping patterns that work
- Data analyst — Languages & tools: SQL, Python (pandas), dbt, Looker · Methods: cohort analysis, A/B test design, forecasting · Domains: subscription retention, pricing
- Registered nurse — Clinical: IV therapy, wound care, telemetry monitoring · Systems: Epic, Meditech · Certifications: BLS, ACLS, PALS
- Marketing manager — Channels: paid search, lifecycle email, SEO · Platforms: GA4, HubSpot, Google Ads · Analysis: attribution modelling, LTV/CAC
- Electrician — Trade: conduit bending, three-phase installs, fault finding · Compliance: NEC 2023, lockout/tagout · Tickets: OSHA 30, journeyman licence
How do you match skills to the job posting?
Copy the employer's wording when it is honest to do so. If the posting says "customer relationship management (CRM)" and you use Salesforce, write "CRM (Salesforce)" so both the phrase and the product appear. Semantic matching tools connect the two, but a human skimming for their own vocabulary finds it faster when it is literally there.
A five-minute matching pass
- Paste the posting into a document and highlight every tool, method and qualification named
- Mark each one: have it and can prove it, have it partly, do not have it
- Put every "have it and can prove it" item into your skills groups using the posting's words
- Move the three most important ones into experience bullets, with a number attached
- Leave the rest out — do not list a skill you cannot discuss for two minutes
Should you rate your skill levels?
No. Rating bars, five-star rows and "Excel: 90%" all fail twice: a parser reads the label and loses the graphic, and a human has no idea what your 90% means against anyone else's. If a level genuinely matters, state it in words — beginner, working, advanced — or better, prove it with evidence.
Language levels are the exception, because CEFR bands and phrases like "professional working proficiency" are standard and comparable.
Prove instead of rate
Instead of "SQL ●●●●○": "Wrote the 40-table reporting model behind the weekly exec dashboard in SQL and dbt."
Instead of "Leadership ★★★★☆": "Managed 6 support agents across two shifts, cutting first-response time from 9h to 2h."
Instead of "Excel: expert": "Rebuilt the 12-month cash forecast in Excel, reducing forecast variance from 11% to 3%."
How many skills should you list?
Eight to fifteen. Below eight, a technical role looks under-equipped; above fifteen, nothing stands out and the reader assumes padding. If you cannot get under fifteen, you are listing features of a tool as separate skills — collapse them into the tool.
Apply this in the builder
InstantCV is free, runs entirely in your browser and exports an A4 PDF with selectable text. Nothing is uploaded and no account is required.
Open the free resume builderResume examples for this guide
Related guides
Frequently asked questions
How many skills should I list on a resume?
Eight to fifteen. Fewer looks under-equipped for technical roles; more reads as unfiltered padding and stops the reader trusting any single entry.
Where should the skills section go?
Under your work experience for most people, and above it for career changers, returners and technical roles where the tool list is the first thing screened.
Should I list soft skills?
Two or three at most, and only ones the posting names. Soft skills are believed when a quantified bullet demonstrates them, not when they are asserted in a list.
Should I rate my skill levels?
No. Rating bars, stars and percentages lose their meaning to a parser and mean nothing to a human. State a level in words or prove it inside an achievement bullet.
How do I group skills?
Two or three labelled groups on one line each — for example tools, methods and certifications — so the reader can find what they are scanning for in a second.
Should I copy skills from the job posting?
Copy the wording for skills you genuinely have, and pair the phrase with the product: "CRM (Salesforce)". Never list a skill you cannot discuss for two minutes.