How to Write a Resume Skills Section (With Examples)

Hands typing a resume skills section on a laptop

To write a resume skills section that actually gets read, stop listing adjectives and start listing evidence. A skills section has two readers - the software that scans for the exact terms in the job description, and the human who spends a few seconds deciding whether to keep reading - and it has to satisfy both. This guide shows you how to choose the right skills, where to put them, how to format them so the parser does not mangle them, and how to prove each one in the bullets below.

You know the section. Team player. Detail-oriented. Hard-working. Strong communicator. You wrote it because every resume template has a skills box and it felt wrong to leave it empty. Then you sent the resume out and heard nothing, and you started to wonder whether the problem was the skills you chose, the way you listed them, or the fact that you listed them at all. It is usually the third thing, and then the first two.

What the skills section is actually for

A skills section is not a summary of your personality. It is a matching surface. Most applications are read by software before a person sees them, and that software is looking for the terms in the job description. Your skills section is where you put those terms in plain, exact language so the match is obvious. The human reader uses the same section differently: they scan it to answer one question - does this person have the specific things this job needs? - and they answer it in seconds. Two readers, two jobs, one short list.

The reframe: name the skill, then prove it

The mistake almost everyone makes is treating the skills section as a place to make claims. A claim with no proof is noise. The section that works is a two-part system: the skills list names the skill in the employer's own words, and a bullet in the experience section proves it with a result. The list is the index; the bullets are the evidence. If a skill appears in the list and nowhere else, a sharp reader will assume you are padding - and they will be right.

Step 1: Sort your skills into three buckets

Before you write anything, empty your head onto a page and sort it. Three buckets keep the list honest.

Tools and technical skills. The software, platforms, languages and methods you actually use. These are the easiest to match and the easiest to verify, so they go first.
Domain knowledge. The industry, process or subject expertise you have built - the regulations you know, the systems you have run, the customer type you understand.
Human skills, but only the specific ones. Not 'communication' - 'executive briefings'. Not 'leadership' - 'managing a team through a reorganisation'. A specific human skill is a claim someone can picture; a generic one is wallpaper.

Step 2: Mine the job description for the exact words

The single highest-return habit in resume writing is to build the skills section from the posting, not from memory. Open the job description and highlight every skill, tool and qualification it names. Then sort what you highlighted into three piles: skills you have and can prove, skills you have but have not written down, and skills you do not have. The first two piles become your list. The third pile is not a reason to lie - it is a reason to decide whether this role is worth your time.

Use the employer's exact phrasing. If the posting says 'stakeholder management', write 'stakeholder management', not 'working with clients'. The software is matching strings, and the human is matching the language of their own team. This is the same mirroring method that makes a tailored resume work, and the skills section is where it pays off fastest.

Step 3: Choose eight to fourteen skills, in order of relevance

A skills section is a shortlist, not an inventory. Eight to fourteen items is the working range: enough to cover the posting's main requirements, few enough that a reader can take them in at a glance. Order them by how much the job cares, not alphabetically and not by how much you like them. The first three or four are the ones you want the reader to remember, so they should be the ones the posting repeats.

If you are changing fields, put the transferable skills first and the technical ones second. If you are staying in the same lane, lead with the tools and the domain terms. Either way, cut anything you cannot back up in a bullet - a short list you can defend beats a long one you cannot.

Step 4: Put it where the reader is already looking

Career changer, or early in the field: put the skills section near the top, just under the summary, so the match is visible before the reader has to hunt for it.
Experienced and staying in your lane: the section can sit lower, after the experience, because your job titles already carry the signal.
Applying through a portal: keep the section as plain text in the body of the resume. A skills box built as a graphic or a two-column table is invisible to the parser and awkward for the human.
Applying to a small company or through a person: the same list works, but the proof bullets matter more, because a human is reading the whole thing.

Step 5: Prove each skill once

For every skill in the list, find one bullet in your experience that shows it in action. The bullet does not need to be long; it needs to be specific. 'Managed stakeholder management' is not proof. 'Ran weekly status calls with three vendor teams and cut the escalation backlog' is. If you cannot find a bullet for a skill, either write one or take the skill off the list.

Step 6: Format it so the software can read it

Plain text, one skill per item, separated by commas or line breaks. No columns, no text boxes, no tables, no icons.
No rating bars or star scales. A row of stars tells a reader nothing and a parser less.
No skill you would not want to be asked about in the interview. Everything on the list is fair game.
Spell out an acronym once, then use the short form: 'search engine optimisation (SEO)'. The posting may use either.
Keep the section to one block. If it needs headings, use two or three short ones, not a wall of sub-sections.

Before and after

Here is the same candidate, written two ways. The job is an operations role that asks for process improvement, vendor management and reporting in a specific tool.

Before	After	Why it changed
Team player, detail-oriented, hard-working, strong communicator	Process improvement · Vendor management · Stakeholder briefings · Reporting (Tableau) · SOP writing	The after list names the things the posting names, and every item is something the candidate can prove.
Microsoft Office, Excel, PowerPoint	Advanced Excel (pivot tables, lookups) · Tableau · Google Sheets automation	Specific beats broad. 'Advanced Excel' tells the reader which Excel.
Skills listed alphabetically	Skills ordered by what the posting repeats	The first items are the ones the reader remembers, so they should be the ones the job cares about.
Skills section only	Skills section plus one proof bullet per skill	The list names the skill; the bullet shows the result. Together they are an argument.

The skills-section worksheet

Build the list in one pass, in this order. The columns are the whole method.

Column	What goes in it	Why it matters
Skill	The skill in the posting's exact words.	The software matches strings, so the employer's phrasing is the one that counts.
Bucket	Tool, domain, or specific human skill.	Keeps the list honest and stops adjectives from creeping in.
Proof bullet	The one experience bullet that shows it in action.	A skill with no bullet reads as padding; the bullet is the evidence.
Placement	Top third, or after the experience.	Career changers lead with the list; experienced candidates can let the titles carry it.
Keep or cut	Whether it survives the cut to fourteen items.	A shortlist you can defend beats an inventory you cannot.

What good looks like

Every item is a skill, not an adjective.
The wording mirrors the job description, not your own vocabulary.
The list is eight to fourteen items, ordered by relevance.
Each item has one proof bullet in the experience section.
The section is plain text - no columns, tables, icons or rating bars.
You can talk about every item on the list for a minute.

Where people get stuck

Stuck because the posting lists skills you do not have. Sort them into have-and-can-prove, have-but-not-written, and do-not-have. The first two piles are your list; the third is information about the role, not a reason to invent anything. If most of the posting lands in the third pile, the honest move is to aim at a different posting.

Stuck because your skills feel generic. Generic is a naming problem, not a skills problem. Communication becomes executive briefings; leadership becomes managing a team through a reorganisation. Attach the context you actually worked in and the same skill stops sounding like everyone else's.

Stuck because the list keeps growing. Cut to fourteen and order by what the posting repeats. The first three or four items are the ones a reader remembers, so they should be the ones the job cares about most - everything after that is supporting detail.

Common mistakes

Listing adjectives instead of skills. 'Hard-working' is not a skill; it is a hope.
Copying a generic list from a template. Every template's list is the same, which is exactly why it does not help you.
Using your words instead of the posting's. The match is literal, so mirror the language.
Listing a skill you cannot discuss. The list is a promise the interview will collect on.
Hiding the section behind a graphic or a table. If the parser cannot read it, it does not exist.
Letting the list grow to twenty items. A long list reads as a lack of focus, not an abundance of ability.
Never updating it. The skills section is the fastest part of the resume to tailor, so tailor it every time.

A twenty-minute pass

Ten minutes: highlight every skill in the posting and sort it into have-and-can-prove, have-but-not-written, and do-not-have. Five minutes: write the list in the posting's words, ordered by relevance, and cut it to fourteen items. Five minutes: check that each item has a proof bullet, and that the whole thing is plain text. That is the entire job, and it is the highest-return twenty minutes in the application.

Where this fits

The list you build here sits on top of the Resume Value Proposition Worksheet, which is where you work out what you are actually selling. The mirroring method is the same one in How to Tailor Your Resume to a Job Description, the paragraph that sits above the list is covered in How to Write a Resume Summary, and the skills you are not sure how to name are sorted in How to Identify Your Transferable Skills. The Resume & Applications Roadmap sequences the whole set.

Start this week

Open the posting you most want and highlight its skills. Rebuild your list in its language, cut it to fourteen, and give every item a proof bullet. Then send it - and notice how much easier the interview gets when every line on the page is something you can talk about.

Quick answers

Short answers to the questions this piece gets asked most.

What skills should I put on my resume?
The ones the posting names. Highlight every skill, tool and qualification in the job description, keep the ones you have and can prove, and write them in the employer's exact words. Eight to fourteen items is the working range - a shortlist, not an inventory.

Where should the skills section go on a resume?
Career changers and early-career candidates put it near the top, just under the summary, so the match is visible immediately. Experienced candidates staying in the same lane can put it after the experience, because the job titles already carry the signal. Either way, keep it plain text.

Should I list soft skills on my resume?
Only the specific ones. Communication is wallpaper; executive briefings or managing a team through a reorganisation is a claim a reader can picture. And every skill on the list needs one proof bullet in the experience section, or it reads as padding.

How many skills should a resume skills section have?
Eight to fourteen, ordered by how much the job cares rather than alphabetically. Enough to cover the posting's main requirements, few enough to take in at a glance. Cut anything you cannot back up in a bullet.

Read next:The Experience Paradox Is a Lie. Here's How to Break In — How to break in without years of experience, and what entry level really means.You Sent 50 Applications and Got Silence. Here's Why — What actually happens to your application after you hit submit.You've Sent 300 Applications. Why Haven't You Heard Back? — Why volume applications fail, and the targeting shift that fixes it.

LaunchPath Careers tool: want to build this with structure instead of guesswork? LaunchPath Careers has a Resume Value Proposition Worksheet and a Resume & Applications Roadmap. Start at LaunchPathCareers.com.

LaunchPath Careers by UFO Chaser® helps job seekers build a strategy-first job search. Learn more at LaunchPathCareers.com.

Search This Blog

Cosmo's Career Strategy Blog