Resume Guide articles · Skills

Resume skills section: when you need one and when to skip it

A simple way to decide whether your resume needs a skills section, what to put in it, how to format and place it, and examples you can copy.

Updated October 2026. About 8 minutes to read.

Key takeaways

  • Include a skills section whenever the job posting lists hard requirements such as tools, certifications or languages.
  • Fold your skills into the summary line on a dense one-page resume, or skip the section when every skill is already proven in a bullet.
  • List six to ten hard skills using the exact names from the posting, because some applicant tracking systems match exact terms.
  • Format the section as a single-column, plain-text list; columns, tables and skill bars can scramble what software reads.
  • Show soft skills in your experience bullets instead of listing words like "team player" in the skills section.

Most job seekers should have a resume skills section, because many applicant tracking systems (ATS, the software employers use to store and search applications) look for the exact skills a posting names, and recruiters use the section to check hard requirements quickly. It is not always required, though. If your experience bullets already name every skill the job asks for, you can fold the list into your summary or skip it. Below is a simple way to decide, what to put in the section, how to format it, and copy-ready examples.

Is a skills section necessary on a resume?

Usually yes, but not always. Decide from the job posting and how full your page already is.

Your situationWhat to do
The posting lists hard requirements (tools, certifications, languages)Include a dedicated skills section
Your resume is one page and already denseFold your top skills into your summary line
Every skill is already proven in a bullet ("Cut deploy time from two days to two hours with Docker")You can skip the section

Include it when the posting lists hard requirements

When a posting names specific tools, certifications or languages, a plain, clearly labeled list is the easiest place for both software and people to find them. Use the posting's own names for the skills you really have.

Fold it into your summary when space is tight

On a dense one-page resume, a summary line such as "Data analyst: SQL, Python, Tableau" keeps the key terms without a separate block.

Skip it when every skill is already proven

If each skill appears next to a result in your experience section, a separate list mostly repeats it. What matters is that each term appears somewhere in plain, readable text. Our guide to the purpose of a resume covers what every section is for.

What should you put in a resume skills section?

Six to ten skills, named the way the job posting names them.

Pull your skills from the job posting

Treat the section as a matching exercise, not a brainstorm. Open the posting, note the exact terms it uses for required skills, and keep the ones you can back up with real work. Six to ten is usually enough. A wall of twenty makes the skills that matter harder to spot.

Name the tool, not the category

"Data analysis" tells a reader very little. "SQL, Excel pivot tables, Tableau" gives software exact terms to find and shows a person what you actually use. If the posting says "Figma", write Figma, not "design software".

Leave out "hardworking" and other filler

Traits like "hardworking", "team player" and "detail-oriented" read as padding. If a soft skill matters, show it in a bullet instead.

Weak: Strong communicator

Strong: Ran weekly standups for a five-person team

The free Resume Guide checker flags common buzzwords like these. It cannot tell whether a skill is honest, so that check stays yours.

Hard skills vs soft skills: which belong in the skills section?

Hard skills go in the list. Soft skills are proven in your bullets.

Hard skills are the ones you can name and test: Excel, SQL, Figma, a forklift certification. They belong in the skills section, spelled the way the posting spells them. If the posting says "Salesforce", write "Salesforce", not "CRM experience".

Soft skills are different. A bare word like "teamwork" proves nothing to the person reading. Show it in an experience bullet instead: "Cut onboarding time by mentoring three new hires" shows communication and leadership with evidence attached.

One exception: if the posting names a soft skill as a phrase, such as "cross-functional collaboration" or "client-facing", use that exact phrase somewhere, ideally inside a bullet. Our guide to hard skills vs soft skills on your resume goes deeper.

How should you format a skills section on a resume?

One column, plain text, short labels.

Single column, with commas or simple bullets

Either group skills under short labels ("Technical: Python, SQL, Git") or give each skill its own bullet. Both read cleanly. Skills set side by side in columns may not.

What breaks it

Four things cause most trouble: multi-column layouts, tables, skill bars or star ratings, and text placed inside images or text boxes. Software reading a two-column page can mix your skills in with your job titles, and a skill bar gives it a graphic instead of a word.

To see how your own file holds up, drop the PDF or Word file into the free resume checker. It reads the file in your browser, so nothing is uploaded, and it points out columns, text boxes, tables and skill bars.

A format you can copy

SKILLS

Technical: Python, SQL, Excel (pivot tables, VLOOKUP), Git

Tools: Salesforce, HubSpot, Jira, Figma

Languages: English (native), Spanish (professional)

Plain labels, no graphics, one column. Then adjust the list to each posting before you apply, as covered in how to tailor your resume to a job description.

Where does the skills section go on a resume?

Usually below your experience. Near the top when your titles do not show your target skills yet.

For most resumes, put skills below work experience and education. People read top down, so your strongest proof, your recent roles, should come first, with skills as a quick summary underneath.

Move it near the top, right under your summary, in two cases: you are changing careers and your past job titles do not show the skills the new role needs, or the posting screens hard on specific tools. Wherever it goes, keep it in plain text in the main body of the page, not in a header, sidebar or text box.

What does a good resume skills section look like?

Short, one column, and matched to the posting. Swap in your own skills.

The examples below are made up, written only to show the format.

Retail associate

Point-of-sale systems (Square, Lightspeed)

Inventory management and merchandising

Handling customer complaints

Cash handling and end-of-day reconciliation

Administrative assistant

Microsoft Office (Excel, Outlook, Word)

Scheduling and calendar management

Data entry (60+ words per minute)

Travel booking and expense reporting

Entry-level developer

Languages: Python, JavaScript, SQL

Frameworks: React, Django

Tools: Git, Docker, Postman

Testing: Jest, pytest

Career changer

This is where the skills section matters most. Take the skill names from the posting, then match each one to something you really did in your old role, even if your title was different. A teacher moving into customer success might write "client onboarding" and "CRM documentation" rather than "lesson planning", as long as that is honestly what the work involved.

Keep it to six to eight lines, use the posting's own phrasing, and leave out anything you could not discuss in an interview.

How do you tailor your skills section to a job description?

A five-minute pass for each application: highlight the skills the posting names, then mirror them.

Use the posting's exact wording

If the posting says "SQL" and your resume says "database queries", change it. Some systems match exact terms, so "PostgreSQL" and "Postgres" may not count as the same thing. Copy the posting's spelling for anything you really have.

Cut what the job does not need

A retail posting does not need your Kubernetes entry. Extra lines make the relevant ones harder to find. Keep six to ten entries that fit this job.

Check the match for free

Paste the job ad into the Resume Guide checker along with your resume. It shows the skills the ad asks for and which ones your resume does not mention yet, with no account and no subscription. If you want a resume rewritten for a specific posting, that is part of the paid packs, which start at $4.99 once. See pricing.

Do you need a skills section if you are applying through an ATS?

It helps. A clean list gives the software exact terms, and your bullets give a person the proof.

If a posting says "SQL" and your bullet only says "wrote database queries", a system looking for the exact term may not count it. List the term as the posting spells it in your skills section, then use it naturally in a bullet so it reads as real experience, not keyword stuffing.

Do both: a short skills list plus proof in your bullets. A skills-only resume reads thin to a person, and bullets alone can hide a term. Keep the list to the skills the posting actually asks for.

Questions people ask

Short answers to the ones that come up most.

  • Can I put a skills section on a resume with no work experience? Yes, and you should. With no job history, your skills section does more of the work. Take six to ten terms from the job posting that you have used in coursework, personal projects or volunteering. A student who built a Django app can list Django; just be ready to talk about each entry in an interview.
  • How many skills should I list on my resume? Six to ten, taken from the job posting. A longer list makes the skills that matter harder to spot for both software and the person reading. Cut anything the posting does not ask for.
  • Do recruiters actually read the skills section? Yes, but quickly. A clearly labeled, one-column list lets them see at a glance whether you meet the hard requirements, and it gives an ATS a clean list of terms. That is why placement matters, especially if you are changing careers.
  • Is it okay to list soft skills like communication on a resume? Avoid listing them as bare words. "Hardworking" or "team player" read as padding. If the posting stresses communication, prove it in a bullet such as "Ran weekly standups for a five-person team", and keep the skills list for named hard skills.
  • Should I rate my skills with bars or stars? No. Software may read a rating graphic as noise or miss the skill name entirely, and a rating invites awkward questions about why your Excel is a 4 and not a 5. A plain list of skill names works better. Show depth in a bullet with a concrete result instead.

More articles

From the same library. For shorter reads, see the resume guides.

Employers and their screening software differ. Treat this article as the default that works for most applications, and follow a specific posting's instructions whenever the two disagree.