Resume Skills Section: What to List and How to Format It

Header photo by bradford zak on Unsplash. A stock photo, not a screenshot of AceDraft or of any ATS.

A resume skills section is the short block on your resume that names what you can do: the tools, methods, qualifications and languages you'd use in the job. This post shows how to build one for the job you're applying to, and it starts with two things I won't give you.

The first is a list of the top skills employers want. I have no data on what employers want. AceDraft is pre-launch, so there are no users, no hiring outcomes and nothing I could rank. Any list I wrote would be a guess dressed up as research.

The second is an admission about my own product. AceDraft's Skills section makes you fill in a Proficiency Level for every entry, and a level is the one thing on a resume you can type without proving. I built that field, it's required, and I think it's the weakest part of the form. I'll say what I'd do with it further down.

What's left is a method. Take the skills from the posting in front of you, keep only the ones you have, group them, and make each one turn up again in your experience. Every sample skills section below is one I wrote for this post. They're generic. No real candidate used them, and no recruiter has reviewed them.

I also haven't sent a resume through any employer's applicant tracking system (ATS), so nothing here says how one handles a skills section. If you'd like to test what I say about ATS software on a known file: check in presale page for our demo resume and you can verify our claims in the opensource tool we have mentioned there.

Key takeaways

• Pick skills from one job posting. Indeed (updated 15 June 2026) says choosing is easier when you focus on the role's core responsibilities, and Coursera (updated 15 April 2025) suggests listing the required skills you really have first.
• Group related skills under a plain label, like "Programming: Python, Java".
• Back every listed skill with an entry lower down. MIT's career office says skills in your experience descriptions are reinforced by the context around them.
• Limitation: none of my sources gives a number of skills to list, AceDraft's scan has no separate result for the Skills section, and I haven't tested how accurate its skills bars are.

What is a resume skills section for?

A resume skills section's job is to put the tools and methods you can use in one short block, apart from the story of your jobs. The Indeed Career Guide (updated 15 June 2026) says the section helps employers quickly understand what you bring to a role.

I think of it as the index at the back of a book. An index is only useful when the pages it points to exist. "SQL" in your list should point at a project or a job where you wrote SQL.

That picture also tells you what doesn't belong. An index lists topics. It doesn't describe the author's personality, so I keep words like "hard-working" out of the list. That's my own rule, and I'll come back to where soft skills go instead.

The section has one more use, and it's practical. A job posting names tools and methods in its own words. Your skills section is the one place on the page where you can line up your words with the posting's words without bending a sentence to fit them.

How do I choose the skills to put on a resume?

Start from the job posting you're applying to, then keep only the skills you really have and can point to somewhere else on the page. The Indeed Career Guide (updated 15 June 2026) says choosing skills is easier when you focus on the core responsibilities of the role. Coursera's skills-section guide (updated 15 April 2025) suggests reviewing the job description and listing the required skills you really have first.

I'd add one test of my own before anything goes on the list. Where on this resume did I use it? If there's no answer, the skill needs an entry of its own, or it comes off.

Of the phrasings I checked, this one has the most searches. OpenSEO put "skills to put on a resume" at about 33,100 US searches a month on 29 September 2026, roughly six times the 5,400 it showed for "resume skills section" on 27 September. When I pulled Google's US results for the bigger phrase the same day, six of the ten slots were skills lists, going by URLs that include phrases like "25 excellent skills" and "top 10 skills employers look for".

I'm not adding a seventh. Here's the method I'd use instead, with one posting open next to your resume.

1. Copy the posting's responsibilities and requirements into a note.
2. Underline every tool, method, qualification and language it names.
3. Star the ones tied to the main work. This is where Indeed's "core responsibilities" advice comes in. In my book, a skill named in the first few duties counts for more than one in a "nice to have" line at the bottom.
4. Cross off anything you haven't done. Be strict.
5. For each skill left, write down the entry that proves it: a job, a project, a course or a certificate.
6. Only then add skills the posting doesn't name, and only if they're close to the work.

The list you end up with is short, and it changes with every posting. A skills section copied unchanged from one application to the next was chosen for none of them.

How many skills should a resume list?

No page I used for this post gives a number of skills a resume should list, so I won't invent one. Indeed, Coursera and MIT's career office all cover which skills to choose and how to show them. None of them sets a count.

My own rule has no number in it either. A skill stays if the posting asks for it, or for something close, and if it appears again in an entry below. Those two conditions cap the list for you, and the cap moves with the job.

Here's how I'd tell the list has grown too long. No source I used lists any signs, so these are mine:

• You've listed a skill you'd struggle to talk about for two minutes.
• The same tool appears twice under two labels, like "Excel" in Tools and "spreadsheets" in Office skills.
• A group has one item in it, and the label is longer than the item.
• The skills list is longer than the experience entries that are meant to back it up.

If you want a number anyway, count your proof. The number of skills you can back up is the length of the list. I realise that's a dodge, but it's an honest one.

How should I list and group skills on a resume?

List skills on a resume either as a plain bulleted list or grouped under short labels by function, such as "Programming: Python, Java"; Coursera's skills-section guide (updated 15 April 2025) shows both layouts. I'd group them once the list covers more than one kind of skill, because a label saves repeating the same context on every line.

The three sample skills sections below are ones I wrote for this post. They're generic on purpose. Swap in your own skills, and delete any line you can't back up.

An accounts assistant's list, kept plain

Skills

Tally Prime, including GST invoicing

Bank reconciliation and month-end ledger checks

Microsoft Excel: VLOOKUP, pivot tables, conditional formatting

English, Hindi and Tamil, spoken and written

A plain list works here because the skills belong to one kind of work. Each line still names something specific. "Excel" alone could mean anything from typing in a cell to building a forecast, so the line says which parts.

Grouped by kind: a junior web developer

Programming: JavaScript, TypeScript, Python

Web: HTML, CSS, React, Node.js

Data: SQL, PostgreSQL

Tools: Git, Docker, VS Code

There's no group called "Languages" here, and that's deliberate. On a developer's resume the label is ambiguous: JavaScript, or Tamil? I went with "Programming" and left spoken languages for their own section.

This is also how I'd handle technical skills on a resume in general. Name the tool the way the posting names it, and add a version or a sub-skill only where the posting does. If the posting says "React", "React" is enough.

How a marketing coordinator's skills fit AceDraft's three fields

Skill Category: Email marketing. Proficiency Level: Intermediate. Keywords: Mailchimp, list segmentation, subject-line A/B tests.

Skill Category: Analytics. Proficiency Level: Beginner. Keywords: Google Analytics 4, Looker Studio.

Skill Category: Content. Proficiency Level: Advanced. Keywords: copywriting, WordPress, Canva.

This is Coursera's grouped layout with one extra field, because that's how I built AceDraft's form. I left a "Beginner" in on purpose. A level you'd defend beats a level that looks good, and I'll explain my doubts about the field itself when I get to the editor.

One habit I'd apply to all three samples: use the posting's spelling for each tool. If it says "Microsoft Excel" and you wrote "MS Excel", change yours. It costs nothing, and the two names then match letter for letter.

Where should the skills section go on the page?

The skills section can go near the top of the page, under your summary, or lower down after your experience, and none of the guides I used for this post fixes one spot for it. My view is to put it high when your skills are the strongest thing you have, and lower when your experience entries already name the same tools.

How I'd decide, case by case:

• First job, or no work history yet: high. I've written a separate post on a resume without work experience, where projects and education do most of the proving.
• Career change. Also high, led by the transferable skills the new posting asks for.
• Several years in the same field: lower. Your job entries already carry the tool names, so a list above them repeats them before they've been shown in use.
• A technical role where the posting opens with a list of required tools. I'd put it high, since your list answers that one directly.

The format question sits right next to this one, and here my sources disagree with each other. Coursera's skills-section guide (updated 15 April 2025) says a chronological resume may be a better choice than a functional one, and gives as its reason that many companies use an ATS to parse resumes. Coursera's guide for people with no experience (updated 28 June 2026) recommends a functional format, because it promotes your skills rather than listing experience. Same site, two directions.

I won't settle that with a claim about how an ATS reads either format, because I haven't tested one. My own preference is a hybrid: a skills section near the top, with every skill in it turning up again in a dated entry below. That's my view, and I have nothing to measure it against.

In AceDraft's guest editor, Skills is the fourth section in the list, after Basics, Professional Summary and Social Profiles, and before Languages, Education and My Experience.

Do I need a separate skills section at all?

You don't strictly need a separate skills section, but I'd keep a short one and make sure every skill in it also appears in your experience entries. MIT's career office (CAPD, no date shown on the page, read 29 September 2026) advises saying how you performed tasks, such as which programming language or which lab technique you used. It adds that although you might list these skills in a Skills section, including them in your experience descriptions reinforces them by putting them in context.

This question is on page one of the search results, too. In the US results for "resume skills section" that I pulled through OpenSEO on 29 September 2026, slot two was a Reddit thread asking about the consensus on the skills section, and slot five was a LinkedIn post whose URL asks "do I need a skills section on my resume". A university careers page asking whether a resume should have a separate skills section sat in slot nine.

So here's my answer, as a view. The skills section is the one place where the tool names sit together. The experience section is where they're shown in use. Coursera's skills guide (updated 15 April 2025) also says skills can go in other places, such as the summary or objective and the experience section. I'd rather a skill turned up in two places than in one.

If you're writing the top of the page as well, I've put together resume summary examples and resume objective examples in separate posts. In my view, a skill you name up there should also be in the skills section. The other way round is optional.

Author's take. The one case where I'd drop the section is a long, senior resume in a field without named tools, where every skill is already plain from the job entries. I haven't seen data either way on that case, so it's only my judgement.

For everyone else, a short list costs a few lines, and I'd keep it.

What is the difference between hard skills and soft skills on a resume?

The short version: hard skills are tied to the tasks of the job, like a programming language or a type of accounting, and soft skills are personal ways of working, like patience or communication. The Indeed Career Guide (updated 15 June 2026) says hard skills often align closely with job tasks, while soft skills may be more personal.

My view on where each goes: hard skills in the list, soft skills shown inside an entry. "Communication" in a skills list is a claim. "Wrote the weekly update sent to [N] store managers" is the same skill with the evidence attached.

The table sorts common skill types by where I'd prove each one. The examples are generic and mine, and the last column is where each type runs out.

If you can't point to the entry where a soft skill happened, I'd leave the word out.

How do I match my skills to the job description?

Use the posting's own names for skills you already have, and put the ones tied to its main duties first in each group. Anything the posting has no use for can come off. Matching never means adding a skill you don't have.

A worked example, with a posting I made up for this post. Say the requirements read "Advanced Excel, experience with Power BI, stakeholder reporting". Your list says "Spreadsheets, dashboards, reporting". The skills overlap, but the names don't.

So "Spreadsheets" becomes "Microsoft Excel: pivot tables, XLOOKUP". "Dashboards" becomes "Power BI", if that's the tool you used. "Reporting" gets an entry below, naming who you sent the reports to.

If your dashboards were in Tableau, keep Tableau. Swapping the name would be a lie with good spelling.

I've written up the whole-resume version of this, with the steps I use, in how to tailor a resume without rewriting it. The skills section is the easiest part of that job, because it's already a list.

How do I fill in AceDraft's Skills section?

Each group of skills gets its own entry, with three required fields: a Skill Category, a Proficiency Level and a comma-separated list of Keywords. It's in the free guest editor, which needs no sign-up, as the fourth section after Basics, Professional Summary and Social Profiles.

Here's what's on the form, as I built it:

• Skill Category, shown as "Skill Category (e.g. Programming)". This is your group label.
• Proficiency Level, whose placeholder reads "Expert / Master".
• Keywords, comma-separated, with "HTML, CSS, JavaScript" as the example. An AI Rewrite link sits on this box.
• An add button for another entry, and a trash icon to delete one.

Now the field I'm least happy with. Proficiency Level is required, so every entry needs one, and a level is self-reported. Nothing on the page confirms "Expert" unless an entry below does. The placeholder makes it worse by showing the top of the scale before you've typed anything. I wrote that placeholder.

For now the field stays required, so here's how I'd fill it. Type the level you'd defend if someone asked you to show it, and stick to plain words: Beginner, Intermediate, Advanced. If a group mixes levels, like Excel you use daily and Power BI you've tried twice, split it into two entries instead of averaging them into one word.

The AI Rewrite link on the Keywords box depends on whether you're signed in. In the signed-out guest editor, clicking it opens a pop-up about getting AI rewrites, and your text stays as it is. Signed in with Google, it runs only when a job description is pasted into the editor, and asks you for one if there isn't. I haven't judged what it suggests for a skills list, so I can't tell you whether its suggestions are any good.

When the resume's done, press Save. The progress screen offers a free ATS-ready plain-text PDF of your resume as written, with no sign-up, no payment and no watermark. On the web it opens your browser's print dialog, where you pick Save as PDF.

There's also a paid polished export. It adds a recruiter and ATS rewrite, a keyword-gap analysis and a polished PDF, needs Google sign-in, and is one payment per export with no subscription. Neither export gives you a DOCX.

Does AceDraft check my skills section?

AceDraft doesn't check your skills section on its own. Its free ATS scan has Hard Skills and Soft Skills bars that compare your resume with terms found in the job description you paste, and I haven't tested how accurate those bars are.

The scan needs a resume PDF up to 10 MB and a pasted job description, and a target job title is optional. Results take about 30 seconds and aren't gated behind an email. Signed out, you get 15 scans a day; signed in, they're unlimited. You can run it from AceDraft's free ATS scan page.

Its Score Breakdown has three scored bars: Hard Skills, Job Title Alignment and Soft Skills. Each one compares the resume with terms in the posting. None of them is a separate result for your Skills section.

Where the bars stop:

• A bar shows "not scored" instead of 0% when it couldn't be measured. Job Title Alignment does this when no job title is given, and Soft Skills does it when the job description matched zero soft-skill terms.
• Formatting and Content Quality say "coming soon". They aren't scored today.
• I haven't tested how accurate the Hard Skills and Soft Skills bars are. An earlier post of mine recorded runs where they returned nothing.
• The whole scan is AceDraft's own scoring against one pasted job description. It isn't any employer's ATS and has no access to one. Its score hasn't been checked against Workday, Greenhouse or any other named system.

So a "not scored" Soft Skills bar isn't a 0%. It shows when the job description matched zero soft-skill terms, which tells you about the posting.

For more on each bar, I've set out what each row of the score breakdown measures, and there's a separate walkthrough of the resume detail page: score and keywords.

Which skills should I leave off?

Leave off any skill you couldn't show in use, starting with tools you've only read about and adjectives posing as skills. The rest of this list is mine, since none of my sources sets these rules.

• A tool you used once, in a tutorial.
• Adjectives on their own: "team player", "detail-oriented", "fast learner", "results-driven". Show the behaviour in an entry, or drop the word.
• Skills from a different career that the posting doesn't touch. Keep them for an application where they matter.
• Percentages and star ratings. "Python 80%" has no unit I can think of. Yes, I see the irony, given the Proficiency Level field I built. A word you'd defend is the least-bad version of the same idea.
• Skills you crossed off in the matching step and then added back because the posting asked for them.
• Duplicates hiding under two labels.

One last test before you send it. Read each skill aloud and name the entry where it happened. If you have to pause and think, that line goes.

What haven't I tested?

I haven't tested any skills section in this post with recruiters, hiring managers or real applications, so nothing here tells you which skills section gets a call. Here's the full list, so you can weigh the advice above for what it is.

• No recruiter review. I'm the only person who has read these samples.
• No outcome data. AceDraft is pre-launch: no users, no usage data, no reviews and no success rates.
• I haven't submitted a resume through Workday, Greenhouse, Lever, Taleo, iCIMS or any other employer's ATS, so I can't say how any of them treats a skills section, a grouped list or a proficiency level.
• The scan's Hard Skills and Soft Skills bars: accuracy untested, with empty runs recorded in an earlier post.
• I haven't judged AI Rewrite's suggestions for the Keywords box.
• I haven't compared a skills-first hybrid with a plain chronological resume in real applications, so my preference for the hybrid is untested.
• This post doesn't describe how the three Skills fields are laid out in the exported PDF.
• I used four pages for this post, from Indeed, Coursera (two) and MIT CAPD, read on 29 September 2026. Other guides may disagree, and those pages can change.

For the ATS side, there's a file you can check yourself: check in presale page for our demo resume and you can verify our claims in the opensource tool we have mentioned there.

That tool is ATS Screener. It's open source and simulates Workday, Oracle Taleo, iCIMS, Greenhouse, Lever and SAP SuccessFactors. It isn't affiliated with any of them. A simulator is still somebody's model of those systems, the same caveat I put on my own scan. I haven't recorded any scores from it, and I won't quote one.

Use this method if you have a specific posting and can name, for each skill, the entry where you used it. Start from the sample nearest your field, rebuild it from the posting, and fill in AceDraft's three fields with a level you'd defend.

Skip it if you want a ready-made list of in-demand skills to copy. I don't have the data to write one, and a method built on your own posting won't hand you one either.

Sources

• Indeed Editorial Team, Best Resume Skills, Indeed Career Guide. Updated 15 June 2026; read 29 September 2026.
• Coursera Staff, How to Write a Resume Skills Section. Updated 15 April 2025; read 29 September 2026.
• Coursera Staff, How to Write a Resume with No Experience: 5 Helpful Steps. Updated 28 June 2026; read 29 September 2026.
• MIT Career Advising & Professional Development, Resumes. No date shown on the page; read 29 September 2026.
• OpenSEO keyword data for "resume skills section" (checked 27 September 2026) and "skills to put on a resume" (checked 29 September 2026), and US SERP data for both, checked 29 September 2026.
• AceDraft, AceDraft presale page. Read 29 September 2026.