How to Write the Skills Section of a Resume (With Examples)

The skills section of a resume looks like the easiest part to write: a short list, no bullets, no metrics. That is exactly why most people get it wrong. They paste in twenty generic words, add a few star ratings, and move on, and the section ends up doing nothing for them.

Done well, the skills section is the part of your resume that recruiters' search tools match against, the part a hiring manager scans to confirm you can use their stack, and the index that points to proof elsewhere on the page. This guide shows you how to choose the right skills, how many to list, how to group and order them, where to put the section, and how to show proficiency without graphics.

You will also get a five-step method for mapping a job post to your skills, eight examples by role and career stage, and a checklist you can run before every application.

What the skills section of a resume actually does#

A skills section has three readers, and each one uses it differently. If you write for all three, the section earns its space.

• Search tools. Recruiters query their applicant tracking system (ATS) and sourcing platforms for titles, locations, and skills. Your skills section gives those queries exact terms to match.
• The skimming recruiter. A recruiter's first pass is short. The 2018 Ladders eye-tracking study, as reported by HR Dive, measured an average initial screen of 7.4 seconds and found that clear section headings helped resumes hold attention.
• The hiring manager. The person who will manage you reads more slowly and asks a narrower question: can this candidate use our tools and methods on day one?

How recruiters search for skills#

Skills have become one of the main ways recruiters filter candidates. LinkedIn's Future of Recruiting 2023 report found that the share of recruiter searches on its platform that include a skills filter grew 25% since 2019, and that recruiters were 50% more likely to search by skills than by years of experience.

A 2026 analysis of more than 100,000 recruiter searches on the sourcing platform Pin shows the same pattern. Skills appeared in almost every search, right behind job titles and locations.

One detail in that study matters for how you write the section. In 89.1% of searches that named skills, every skill was optional. In other words, skills mostly rank candidates rather than exclude them. The more of the requested skills you show, in the employer's wording, the higher you tend to surface.

Why a list alone does not prove anything#

Search gets you seen. Evidence gets you shortlisted. When the National Association of Colleges and Employers asked employers what they look for on new graduates' resumes, nearly 90% said evidence of problem-solving and nearly 80% said teamwork. The operative word is evidence.

That is the core principle of this guide: the skills section is an index, not a claim. Each item should point to a bullet, project, or credential that backs it up.

What belongs in the skills section (and what doesn't)#

Not every skill deserves a slot. The section works best when it holds concrete, checkable capabilities and leaves character traits to your bullet points.

Hard skills: the core of the section#

Hard skills are teachable and testable. They include software, programming languages, equipment, methods, regulations, and spoken languages. For a deeper breakdown of the two categories, see hard skills vs. soft skills.

Good hard skills are specific. "Data analysis" is vague. "SQL (window functions, CTEs)" or "Excel Power Query" tells a reader exactly what you can do. The same applies to methods: "Agile" is broad, while "Scrum (sprint planning, backlog refinement)" is precise.

Soft skills: show them, don't list them#

Employers care a great deal about interpersonal and thinking skills. The World Economic Forum's Future of Jobs Report 2025, as summarized by FM Magazine, found that analytical thinking topped the list of core skills, followed by resilience and flexibility, and leadership.

Here is the catch: everyone claims these skills, so typing "analytical thinking" in a list adds almost nothing. Prove it in a bullet instead: "Built a churn model in Python that flagged 70% of cancellations a month early." Our guide to soft skills for your resume has more ways to show them.

What to include and what to leave out#

Use this table to sort borderline items quickly.

How many skills to list on a resume#

There is no magic number, but there is a sensible range. Too few skills and you miss searches. Too many and the important ones disappear in the noise, and you invite questions you cannot answer.

For most people, 8 to 15 skills is the right range. Technical candidates and senior specialists can go higher if the list is grouped into categories. The table below gives starting points.

The five-minute test#

Before a skill makes the list, ask: could I talk about this for five minutes in an interview, with a real example? If the answer is no, cut it or move it to a "Familiar with" line.

Interviewers often pick an item from your skills list and ask you to walk through how you used it. A list full of words you cannot back up turns that question into a trap.

Why more is not better#

Adding marginal skills dilutes the ones that matter. If a recruiter sees thirty items, they cannot tell which five you are strongest in. A shorter, ordered list makes the hierarchy obvious.

There is also a credibility cost. A resume that lists twelve programming languages for someone two years out of school reads as padding, even if each was used once.

How to choose the right skills: a five-step method#

Picking skills by gut feel produces generic lists. This method ties every item to the job post and to proof on your resume. It takes about 20 minutes per application once you have a master inventory.

1. Build a master skills inventory. List every tool, method, language, and credential you have used in work, school, volunteering, or projects. Keep it in your master resume so you only do this once.
2. Extract the job post's skills. Highlight every tool, method, and qualification in the posting. Note which appear in the requirements versus the nice-to-haves, and which repeat.
3. Score each overlap. For each skill in both lists, score how prominent it is in the post and how strong your proof is.
4. Select and order. Keep the highest scorers, order them by job relevance, and group them into two to four categories.
5. Cross-check the proof. For every skill you keep, confirm that a bullet, project, or credential elsewhere on the resume backs it up. Add one if it's missing.

Step 1: build the inventory with outside help#

Most people forget half of what they can do. Two places help you remember. First, scan old job descriptions and performance reviews for tools you used. Second, look up your occupation in O*NET OnLine, the U.S. Department of Labor's occupational database, which lists skills, knowledge areas, and the software commonly used in each role.

If you want a faster start, a resume skills generator can suggest a role-specific list for you to edit down. Only keep what you can genuinely do.

Step 2: extract the job post's skills#

Read the posting twice. On the first pass, highlight every concrete skill. On the second, mark which ones appear in the requirements, which repeat, and which are in the title or first paragraph, since those usually matter most.

A job description keyword finder can pull these out for you, and our step-by-step guide on how to find keywords in a job description covers the manual method.

Step 3: score each overlapping skill#

Give each skill two scores from 0 to 3, then multiply. Prominence measures how strongly the job post emphasizes it (3 means a required skill named more than once). Proof measures how well your resume backs it up (3 means a quantified bullet or a certification).

The chart below shows what this looks like for a hypothetical marketing operations job. Anything scoring 6 or more goes in. Anything at 2 or below stays out.

Steps 4 and 5: order, group, and prove#

Put the highest scorers first within each category, and put the most relevant category first. Then read your experience section with the skills list beside it. Any skill with no supporting bullet is a gap to fix before you send the resume.

Here is the finished result for the hypothetical marketing operations candidate.

How to format the skills section: five layouts compared#

Formatting decides how quickly someone can find what they need. Pick the layout that fits the number of skills and the type of role. All five below parse cleanly in most ATS software when you use plain text.

Single line#

The simplest option. Separate items with commas or vertical bars and keep it to one or two lines. It works well for early-career resumes and for roles where you only need to show a handful of tools.

Categorized lines#

This is the best default for most people. Each line starts with a bold label, like "Design tools" or "Clinical," followed by the skills in that category. Readers find what they need in one glance, and you can reorder categories for each job without rewriting anything.

Category labels that work by field#

Category names should be the words a hiring manager in your field would use to describe their own team's toolkit. Generic labels like "Other skills" waste the line. These starting points work for common fields.

Two or three categories are enough for most resumes. If you find yourself creating a fifth, some of those items probably belong in a certifications or languages section instead.

Skills with context#

Add a short qualifier after key items: years of use, versions, scale, or the specific feature you know. "PostgreSQL (5 years; query tuning, partitioning)" says far more than "PostgreSQL." Use this sparingly, for the three to six skills that matter most.

Core competencies grid#

Executive and mid-career resumes often use a three-column grid of competencies under the summary. It looks clean, but some parsers read tables left to right across rows and scramble the order. If you use one, test the file in an ATS resume checker first, or build the same effect with plain lines separated by bars.

What to avoid: bars, stars, and icons#

Skill bars, star ratings, percentage dials, and logo icons are popular in templates, and they cause three problems. They do not parse as text, so the ATS may see nothing. They are meaningless, since "80% Python" has no reference point. They also invite skepticism when a reader wonders what the missing 20% is.

The Ladders study cited earlier found that cluttered layouts and multiple columns performed poorly in the initial screen, while simple layouts with clear headings performed well. Plain text wins on both counts.

How to show skill proficiency levels honestly#

Sometimes you want the reader to know which skills are deep and which are working knowledge. Do it with words and context, not graphics. Pick one scheme and apply it consistently.

Two practical rules keep labels credible. First, use Expert rarely; one or two items at most. Second, if most of your list is "Familiar," drop the labels altogether and just order skills by strength.

Better than labels: verifiable context#

Context a recruiter can check beats any self-rating. Compare these three versions of the same skill:

• "Excel: Advanced" tells the reader your opinion.
• "Excel (6 years)" tells them how long you have used it.
• "Excel (Power Query, XLOOKUP, 50K-row financial models)" tells them exactly what you can do.

The third version is longer, but it answers the hiring manager's question before they ask it. Reserve it for the skills at the top of your list.

Language skills follow their own scale#

Spoken languages are the one area where standardized levels exist and help. Use a recognized framework, such as CEFR levels (B2, C1) or the ILR scale, or plain descriptors like Native, Fluent, Professional working, or Conversational. Our guide to language skills on a resume covers which scale to use where.

Where to put the skills section on your resume#

Placement depends on what the reader needs to see first. The default for experienced candidates is below work experience, because experience is what proves the skills. But several situations call for moving it up.

Two-column layouts and parsing#

Sidebars look tidy, and many modern parsers handle them. Some older systems read across both columns line by line, though, mixing your skills into your job titles. If you love a two-column design, run it through a parser before applying. The safest choice for online applications is a single column. Our guide to an ATS-friendly resume explains the formatting rules that matter.

Section names that parse reliably#

Call the section Skills, Technical Skills, Core Competencies, or Skills and Certifications. These are standard labels that parsers map correctly. Avoid creative names like "My Toolbox" or "Superpowers," which some systems will not recognize as a skills section.

How to match your skills to the job post without keyword stuffing#

Matching the job post raises your chances in search and with the human reader. Stuffing it, by pasting in every phrase from the posting whether or not you have it, backfires as soon as someone reads the page.

Mirror the employer's exact terms#

If the posting says "customer relationship management," write that alongside "CRM." If it says "Google Analytics 4," do not write "web analytics." Search tools match strings, and recruiters skim for the words they wrote. Our guide to resume keywords covers this in detail.

• Include both forms of acronyms once: "Search engine optimization (SEO)."
• Match tool names and versions when they matter: "Revit 2024," "Python 3."
• Keep the employer's spelling, such as "JavaScript" not "Javascript," or "Microsoft Dynamics 365" not "Dynamics."
• Avoid synonyms for required skills. Save your own phrasing for the bullets.

Spread skills across the whole resume#

A skill that appears only in the skills list looks unproven. Repeat your top three to five skills in your summary and in your bullets, in context. Recruiters reading your experience should see the same tools at work. The resume keyword scanner can show you which job post terms are missing from your draft.

Here is what that looks like in practice.

The "after" version drops traits that cannot be checked, names features and methods, and uses the phrases a support manager would search for.

Skills section examples by role and career stage#

These examples show different layouts and lengths. Treat them as models for structure, not text to copy. Your list should come from your own inventory and the specific job post.

Software engineer#

Engineers should group by layer and put the post's main language first. For more on grouping technical stacks, see technical skills for a resume and the technical skills generator.

Registered nurse#

Marketing coordinator#

Project manager#

Recent graduate#

New graduates should keep skills tied to projects and coursework they can describe. If that is your situation, our guide to an entry-level resume shows how skills, projects, and education work together.

Career changer#

Career changers should lead with the new field's vocabulary and fill it with skills they have actually trained in or practiced. See our guide to transferable skills for help translating past experience.

Special cases: when the standard advice changes#

Most people can follow the defaults above. A few situations call for a different approach.

You are changing careers#

Move the skills section to the top and pair it with a short summary that names your target role. Split it into "Transferable" and "Technical" categories if that helps the reader connect your past and future work. Our career change resume guide covers the full structure.

Resist the urge to switch to a skills-only format. A functional resume that hides dates tends to raise more questions than it answers. A hybrid layout, with skills on top and a normal work history below, is safer.

You are applying for federal jobs#

Federal resumes follow different rules and reward detail. Skills need to show up inside each job entry with context, because reviewers check your experience against specialized experience requirements. See our federal resume guide.

You are senior or an executive#

Executive resumes lean on competencies, not tool lists. Keep tools to a single line, if any, and lead with functional strengths like P&L management, M&A integration, or turnaround leadership. The executive resume guide shows how to frame scope.

You work in the skilled trades or operations#

Trade and operations resumes are read by supervisors who want to know which equipment you can run safely and which licenses you hold. Lead with equipment and techniques, name makes and models when the post does, and list safety credentials like OSHA training or forklift certification near the top. A line such as "CNC: Haas VF-2 setup and operation, G-code editing, first-article inspection" tells a shop supervisor more than a paragraph of general claims.

You have gaps or older skills#

If you are returning after a break, refresh before you list. Check whether the tools you used are still current versions, and spend a few hours on the newest release if they are not. List what you know now, not what you knew then. Our return-to-work resume guide covers how to frame the gap itself.

You work with AI tools#

If you use AI tools in your work, name them specifically and show what you built with them: "ChatGPT and Claude for drafting customer FAQs; reduced first-draft time by half" is concrete. "AI" on its own is not. See AI skills for your resume for examples.

Common skills section mistakes and how to fix them#

Most weak skills sections fail in predictable ways. Check your draft against this list.

• Listing traits instead of skills. "Hardworking" and "team player" are not searchable or verifiable. Replace them with tools and methods, and show traits in bullets.
• Using the same list for every job. Reorder and swap items for each application. Ten minutes of tailoring beats a generic list every time. Our guide on how to tailor your resume shows a fast routine.
• Burying the key skill. If the job post leads with Salesforce, Salesforce should not be ninth on your list.
• Listing skills you cannot defend. If you would struggle to answer a question about it, cut it.
• Including outdated technology. Old versions and retired tools suggest your knowledge has not kept up.
• Graphics instead of text. Bars and icons may vanish in parsing and look vague to humans.
• No proof anywhere else. A skill that appears only in the list is a claim. Add a bullet that uses it.
• Duplicating sections. Listing the same certification in skills, summary, and certifications wastes space. Name it once in the skills list if it is a search term, then give the full details in its own section.

Keep the list current between searches#

The best time to update your skills is when you learn them, not the night before an application. Each quarter, add new tools, versions, and methods you have used to your master inventory, along with a one-line note on what you did with them. That note becomes the proof bullet later.

Skills section checklist before you apply#

Run through this checklist for every application. It takes about five minutes.

• Every required skill from the job post that I genuinely have appears in my resume, in the employer's wording
• The most important skill for this job appears in the first line of the section
• The list has roughly 8 to 15 items, grouped into two to four labeled categories
• No generic traits like "hardworking" or "detail-oriented" in the list
• No skill bars, star ratings, percentages, or logo icons
• Acronyms appear once with their full form
• Each listed skill is backed by a bullet, project, or credential elsewhere
• I could talk for five minutes about every item on the list
• The section heading is a standard label like Skills or Technical Skills
• The file parses correctly in an ATS check

Put your skills section to work#

Start with your master inventory, because everything else is faster once it exists. Then, for your next application, run the five-step method: extract the post's skills, score the overlap, select and group the top items, and confirm each one has proof elsewhere on the page.

After that, read your resume as the hiring manager would. Does the first line of your skills section match the first requirement in the job post? Does every skill appear again in a bullet with a result? If both answers are yes, your skills section is doing its job.

Finally, check the whole page with a resume checker and compare it against the posting with the resume to job description match tool. Then move on to strengthening the bullets that prove your skills, using our guide to resume bullet points.