The skills section is the easiest part of a resume to write and the easiest to get wrong, because padding it feels productive. Twenty-five comma-separated tools looks like competence and reads like noise.
Its actual job is narrow: give a recruiter a scannable index of the concrete things you can do, using the words they will search for. Everything else belongs in your bullets.
What belongs there
Only skills that are specific, verifiable, and relevant to the role you are applying for. In practice that means:
- Tools and software — Figma, Salesforce, Kubernetes, SAP, AutoCAD, Xero.
- Languages and frameworks — Python, TypeScript, React, SQL, R.
- Methods and standards — GAAP, HACCP, SOC 2, Scrum, GDPR, HL7.
- Techniques — regression analysis, load testing, motion graphics, phlebotomy.
- Spoken languages — with an honest level: native, fluent, professional, conversational.
- Certifications — either here or in their own section, not both.
Each of these is something a hiring manager can ask you about and you can demonstrate. That is the test.
What does not belong
Skills sections
Works
- Languages: Python, Go, SQL
- Data: dbt, Airflow, BigQuery, Looker
- Infrastructure: Docker, Terraform, AWS (ECS, RDS, S3)
- Languages: English (native), Spanish (professional)
Avoid
- Microsoft Office, email, internet research, typing
- Team player, hard worker, fast learner, detail-oriented
- Leadership ★★★★☆ Communication ★★★★★ Python ★★★☆☆
- Python, Java, C++, Go, Rust, Ruby, PHP, Scala, Kotlin, Swift, Perl, Haskell
Three specific problems in that second column.
- Baseline software
Word, email, and web browsing are assumed for any office role. Listing them suggests you had nothing else to list. Advanced Excel — pivot tables, Power Query, modelling — is a real skill and worth naming as such.
- Soft skills as a list
“Team player” and “excellent communicator” are self-assessments with no evidence behind them, and every applicant claims them. Demonstrate them in a bullet instead: leading a project, training staff, resolving an escalation.
- Rating bars and star systems
They fail twice. The rating is meaningless without a scale — your four out of five and mine are not comparable — and the visual is usually drawn as a graphic, so applicant tracking systems read the label and lose the level entirely. If proficiency matters, write it: “Python (primary language, 5 years)”.
Group them, do not dump them
A flat list of twenty items is unreadable. Two to four labelled groups of three to six items each is scannable in a couple of seconds and shows you understand how the work is organised.
| Field | Groupings that work |
|---|---|
| Software engineering | Languages · Frameworks · Infrastructure · Testing |
| Data | Languages · Warehousing · Visualisation · Statistics |
| Design | Tools · Research methods · Deliverables |
| Marketing | Channels · Analytics · Content · Automation |
| Finance | Standards · Systems · Analysis · Reporting |
| Healthcare | Clinical · Systems · Certifications · Languages |
Order matters twice over. Put the group most relevant to the posting first, and within each group put the strongest item first — readers and skimmers both weight the opening item disproportionately.
Match the posting's vocabulary
Recruiters search the applicant tracking system using the exact terms from the job description. If the posting says “Kubernetes” and you wrote “K8s”, a keyword search may not connect them. Write the full term, and add the shorthand only where it is genuinely the common form.
Where your experience is equivalent but named differently, show both: “BI dashboards (Looker; comparable to Tableau)”. This is honest and searchable at once. The full method for extracting those terms is in pulling keywords out of a job description.
Where to put the section
- Above experience when the tools are the point — engineering, data, design, trades, and most technical roles. Recruiters look for them first.
- Below experience when your track record is the point — management, sales, operations, and senior roles generally.
- Never in a sidebar text box unless your template builds columns on a real grid; floating boxes are a common cause of scrambled parsing.
Frequently asked questions
How many skills should I list on a resume?
Roughly 8 to 15, arranged in two to four labelled groups. Beyond that the section stops being scannable and starts reading as padding, and it dilutes the terms that actually match the posting.
Should I include soft skills on my resume?
Not as a list. Claims like “team player” and “strong communicator” are unverifiable and universal. Show them through evidence instead — leading a project, training new staff, presenting to a client — inside your experience bullets.
Are skill rating bars or star ratings a bad idea?
Yes, for two reasons. The scale is undefined, so the rating conveys nothing comparable, and the levels are usually drawn as graphics that applicant tracking systems cannot read. If proficiency matters, state it in words: “Python (primary language, 5 years)”.
Should the skills section go before or after experience?
Before, if the specific tools are the main hiring criterion, as in most technical and trade roles. After, if your track record and scope matter more, as in management, sales, and senior positions.