Which skills belong in the section, which belong inside your bullets, why proficiency bars hurt you, and how to handle it after a career break.
Open ten resumes and the skills section will look nearly identical on all ten: a block of twenty-five words including "Microsoft Office", "Communication", "Team Player", "Problem Solving", and "Attention to Detail".
It is the most padded region of the document and the least read, and the reason is simple. A list of unverifiable claims is not information. A recruiter reading "excellent communication skills" learns nothing, because no one has ever written the opposite.
The section can be genuinely useful. It just has to contain a different kind of thing.
The test that decides what belongs
Before adding anything, ask: could someone check this in an interview?
"Python" passes. Someone can ask what you built with it. "SAP MM" passes. "Registered Nurse, licence #12345" passes. "Conversational Portuguese" passes, uncomfortably, because they might switch languages.
"Hard-working" fails. "Detail-oriented" fails. "Passionate about technology" fails. Not because the traits are worthless, but because listing them proves nothing, and the space costs you something that would.
That single test resolves most of the difficulty. The skills section is for checkable nouns. Everything else belongs somewhere it can be demonstrated.
Hard skills go in the section
These are the ones with names: software, systems, languages, certifications, techniques, equipment, frameworks, standards.
Group them. An ungrouped run of eighteen comma-separated words is a wall; two or three labelled clusters can be scanned in a second.
Clinical ACLS, PALS, IV therapy, wound care, triage, Epic (Beacon, ASAP)
Systems Epic, Cerner, Meditech
Certification RN (State of Ohio, active), BLS, ACLS — renewed 2026
Languages Python, TypeScript, SQL, Go
Infrastructure AWS (ECS, RDS, Lambda), Terraform, Docker, GitHub Actions
Data dbt, Airflow, Snowflake, Postgres
Note what those look like: specific, current, and precise enough to be wrong. "AWS (ECS, RDS, Lambda)" tells a reader more than "Cloud technologies", and it matches how a recruiter searches.
Three rules keep the section honest.
Use the employer's vocabulary. If the posting says "Power BI" and you wrote "data visualisation tools", a recruiter filtering their database on the first term does not find you. Where the industry genuinely uses two names, carry both.
Drop what has aged out. Microsoft Office has been assumed for twenty years; listing it signals that you needed something to fill the line. The same is now true of "email", "internet research", and in most fields, "social media". If a skill is a precondition for having the job at all, it is not a differentiator.
Do not list what you cannot defend. Everything in this section is a standing invitation to be asked about. If you used Tableau twice in 2021, either put it under a "Familiar with" grouping or leave it out.
Soft skills go in the bullets
Communication, leadership, judgment and resilience are frequently the reason someone gets hired. They just cannot be asserted.
"Skills: Leadership, Communication, Conflict Resolution, Stakeholder Management"
"Took over a team of nine after two resignations in one month; rebuilt the on-call rota with the team rather than for them, and had zero further departures in the following year."
That is the whole technique. Find the bullet where the trait was necessary, and let the situation carry the claim. A reader draws the conclusion themselves, which is far more persuasive than being told.
If a posting explicitly asks for a named soft skill — some do, particularly in healthcare, education and public sector roles — you can include it in the section, but pair it with something concrete: "Stakeholder communication (chaired monthly board reporting)".
How long the section should be
Eight to fifteen items, in two or three groups.
The instinct to list everything is understandable, especially early in a career when the section feels like the strongest part of the page. Resist it. A list of thirty tools reads as an inventory of everything you have ever opened, and it dilutes the six that matter for this job. The reader's attention is fixed; adding items divides it.
If cutting feels impossible, sort by relevance to the specific posting and keep the top twelve. The rest can come up in conversation.
Where to put it
Experienced candidates: below work experience. Your history is the argument; skills are supporting evidence.
Early career, or changing fields: above work experience. When your job titles do not describe the job you are applying for, the skills block does the translating and gets read first.
Technical roles: near the top regardless of seniority, because recruiters screening for a stack read it first and everything else second.
Proficiency bars, star ratings, and percentages
Do not.
They are self-assessed, which means they contain no information — nobody has ever drawn themselves at two bars out of five. They consume an enormous amount of space relative to their content. And they parse badly, since a rating drawn as a graphic contains no text, so the extracted record shows a skill name with nothing attached.
If you need to distinguish depth, use words and be honest about it: an "Expert" group and a "Working knowledge" group communicates more in two labels than fifteen bars.
The skills section after a career break
This is where the section does its most useful work, and it is worth treating separately.
If you have been out of employment — caring, illness, study, redundancy, relocation — the reflex is to worry that the gap dominates the page. In practice the gap is noticed, briefly, and what determines the outcome is whether your capability reads as current.
That is a skills problem more than a history problem, and there are three things that help.
Keep the section current, not historical. Name the versions and platforms in use now. A skills block that describes the tooling of four years ago tells a reader more about the gap than the dates do.
Give anything you did during the break its own entry. A contract, a course, a certification, a volunteer role, a family business you helped run — these are real and they belong in the employment history with dates, not hidden. A three-month course listed plainly closes a year-long gap far better than silence does.
Say what happened, once, in one line. In the summary or the cover letter, not both, and without apology: "Career break 2024–2025 for family care; returned to practice with recertification in March." Stated plainly it becomes a fact. Left unstated it becomes the question the reader is holding while they read everything else.
What does not work is the functional resume — the format that groups everything by skill and buries dates at the bottom. Recruiters know why people choose it, and it converts a small question into a large one. Keep the reverse-chronological structure and let a strong, current skills section carry the weight.
Checking yours
Read your skills section and, for each item, find where in your work experience it appears doing something. Anything you cannot trace either needs a bullet that demonstrates it, or needs to come out.
That exercise usually removes a third of the section and improves the resume twice — once by cutting filler, and once by revealing which bullets were describing duties instead of showing capability.
For the vocabulary that actually appears in postings for your specific job title, our resume examples by role list the tools and terms employers use, role by role.
Land more interviews with ATS-optimized resume tools
Build Your Resume FreeFrequently Asked Questions
What skills should I put on my resume?
Named, checkable things: tools, systems, languages, certifications, methods. Anything a reader could verify in an interview. Leave out traits like 'hard-working' and 'team player' — they are claims about character, and every applicant makes them.
Should I include soft skills?
Not as a list. Communication, leadership and problem-solving are real and they matter, but stated flatly they carry no weight. Demonstrate them inside a work-experience bullet where the situation makes the claim credible.
How many skills should I list?
Between eight and fifteen, grouped into two or three labelled categories. Beyond that the section stops being a summary and becomes an inventory, and readers skim rather than read.
Do proficiency bars and star ratings help?
No. They are self-assessed, so they carry no information, and they consume a large amount of space to say nothing. They also parse badly, since a rating rendered as a graphic contains no text at all.
CraftMyDocs Editorial Team
Resume & Career Experts
The CraftMyDocs editorial team writes practical, tested guidance on resumes, cover letters, ATS, and job searching — drawing on recruiter feedback and the data behind thousands of resumes built on the platform.