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

The skills section of a resume should list 8 to 15 hard skills, grouped into two to four labeled categories. Put the job's key tools first, in the employer's exact wording. Skip ratings and skill bars. Make sure every skill you list shows up again in a bullet, project, or credential. Place the section after your work experience unless you're a new graduate, a career changer, or applying for a tool-heavy role.

That is the short version. Most people get it wrong because the section looks easy: they paste in twenty generic words, add a few star ratings, and move on.

This guide shows you how to choose the right skills, how many to list, and how to group and order them. It also covers where to put the section and how to show skill level without graphics. You'll get a five-step method for mapping a job post to your skills, a copyable template, and 12 examples by role.

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. They want to confirm, in a glance, that you have the tools the job needs.
• 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 2025 report found that companies running the most skills-based searches were 12% more likely to make a quality hire.

Pin, a recruiting platform, studied more than 100,000 recruiter searches on its own platform, from June 2025 to June 2026. Skills appeared in almost every search, right behind job titles and locations. Because the data comes from one vendor's users, treat it as a strong signal rather than a market-wide measure.

One detail in that study matters for how you write the section. In 89.1% of searches that named skills, every skill was optional. So 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. NACE regularly asks employers what they look for on new graduates' resumes. The answers are about evidence of skills like problem-solving and teamwork, not the words themselves.

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 abilities 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, 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 how you think and work with people. The World Economic Forum's Future of Jobs Report 2025 asked employers which skills are core for their workforce. Analytical thinking came first, named by nearly 70% of employers, as summarized by FM Magazine. Next came resilience, flexibility, and agility (67%), then leadership and social influence (61%).

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." The 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 get lost, and you invite questions you can't 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 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 not, cut it or move it to a "Familiar with" line.

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

Extra skills also dilute the ones that matter. If a recruiter sees thirty items, they can't tell which five are your strongest. And twelve programming languages from 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. Once you have a master inventory, it takes about 20 minutes per application.

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 are required, which are 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 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 job in O*NET OnLine, the U.S. Department of Labor's occupation database. It lists skills, knowledge areas, and common software for each role.

The free resume skills generator shows example skill lists by role, which can jog your memory. 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 are required and which repeat. Skills in the title or first paragraph usually matter most.

The free job description keyword finder does a first pass for you in the browser. Here is a sample marketing operations posting, written for this guide, and what the finder pulled from it.

The finder caught the tools that repeat and the ones it knows by name. It missed phrases that appear only once, such as "lead scoring," "list segmentation," and "email automation." It also picked up "operations specialist" from the job title, which isn't a skill. Use the finder for the first pass, then read the posting yourself for the rest.

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 them. Prominence measures how strongly the post stresses it: 3 means required and named more than once. Proof measures how well your resume backs it up: 3 means a quantified bullet or a certification.

The chart scores a hypothetical candidate against the sample posting. HubSpot gets prominence 3 because the finder counted it five times. Figma gets 0 because the post never mentions it, however good you are. 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 candidate.

How to format the skills section: five layouts compared#

Formatting decides how quickly someone finds 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 group. Readers find what they need in one glance. You can also reorder categories for each job without rewriting anything.

Here is a blank template you can copy. Swap each placeholder for your own category names, skills, and context.

Category labels that work by field#

Category names should be the words a hiring manager in your field uses for 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 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 across rows and scramble the order. If you use one, test the text 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. When they're drawn as shapes, they don't parse as text, so the ATS sees only the skill names. They are also meaningless, since "80% Python" has no reference point. And they invite doubt when a reader wonders about the missing 20%.

Here is the same candidate's skills section in two styles. One lists five tools with symbol ratings, like "HubSpot ●●●●○." The other uses three plain categorized lines with context. Both went into the free checkers inside the same sample resume, and the keyword check used the sample posting above.

A list of names and ratings leaves no room for context, so the bars version never mentions "A/B testing" or "UTM governance." Even the plain version missed "marketing operations" and "campaign reporting." Those belong in your headline, summary, and bullets, which is why the skills section can't do all the work. The free resume keyword scanner shows which terms are still missing from your draft.

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 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. Save it for the skills at the top of your list.

Language skills follow their own scale#

Spoken languages are the one area where standard levels exist and help. Use a recognized framework, such as CEFR levels (B2, C1) or the ILR scale. Or use plain words like Native, Fluent, Professional working, or Conversational. The 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. For experienced candidates, the default is below work experience, because experience is what proves the skills. 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. A single column is the safest choice for online applications. The guide to an ATS-friendly resume explains the rules that matter.

Section names that parse reliably#

Call the section Skills, Technical Skills, Core Competencies, or Skills and Certifications. Parsers map these standard labels correctly. Avoid creative names like "My Toolbox" or "Superpowers," which some systems won't recognize.

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 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," don't write "web analytics." Search tools match strings, and recruiters skim for the words they wrote. The 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 bullets, in context. Recruiters reading your experience should see the same tools at work.

Here is what that looks like in practice.

The "after" version drops traits that can't 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. The technical skills generator shows example stacks by role.

Mechanical or civil engineer#

Non-software engineers should lead with design tools and analysis methods, then licensure status. Put PE or EIT status in the skills section and again in certifications if the post asks for it.

A civil engineer would swap in Civil 3D, structural or hydraulic analysis tools, and the codes the post names. The mechanical engineer resume guide shows a full sample.

Registered nurse#

Classroom teacher#

A teacher who is staying in teaching lists instruction and classroom tools, not corporate training terms. That is the key difference from the career-changer example further down.

The teacher resume guide shows how these skills pair with classroom results in the experience section.

Restaurant and retail#

Hourly jobs have skills sections too, and managers scan them for the systems you already know. Name the point-of-sale system, the food or alcohol certifications, and the volume you can handle.

For full samples, see the server resume and retail sales associate resume guides.

Marketing coordinator#

Project manager#

Recent graduate#

New graduates should keep skills tied to projects and coursework they can describe. The 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 trained in or practiced. See the 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#

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. The career change resume guide covers the full structure.

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 the 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. Lead with 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, and name makes and models when the post does. 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, and spend a few hours on the newest release if not. List what you know now, not what you knew then. The 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 and show what you did with them. "ChatGPT and Claude for drafting customer FAQs; cut 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. The 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 can't defend. If you would struggle to answer a question about it, cut it.
• Including outdated technology. Old versions and retired tools suggest your knowledge hasn't 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 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 to your master inventory. Add a one-line note on what you did with each, because that note becomes the proof bullet later.

Skills section checklist and next steps#

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 text parses correctly in an ATS check

When every box is checked, paste your resume and the posting into the free resume to job description match tool. It shows what is still missing. Then strengthen the bullets that prove your skills, using the guide to resume bullet points.