A resume skills section lists the specific skills you can use on day one, named the way the employer names them. Group related skills into two or three short categories, put the tools and methods from the job posting first, and keep the list focused on what you can prove. Roughly eight to fifteen skills is usually enough; a short, targeted list beats a long inventory.
Key takeaways
- Take skill names from the posting, and include the exact tool and certification names.
- Group the section into two or three categories so it can be scanned in seconds.
- List only skills you could discuss in an interview; cut the rest.
- Prove the most important soft skills with a bullet in experience or projects.
- Skip rating bars, percentages, and vague labels.
What should a resume skills section include?
A skills section holds two kinds of content. Hard skills are the specific, measurable abilities the role requires: software, equipment, methods, coding languages, certifications, and technical procedures. Soft skills are the interpersonal and thinking habits that shape how you work, such as communication, time management, or problem-solving.
| Skill type | What it looks like | Best place on the page |
|---|---|---|
| Tools and platforms | Excel, Salesforce, Tableau, Figma, Python | Skills section, named exactly |
| Technical methods | Financial modeling, A/B testing, CNC setup | Skills section plus a proving bullet |
| Certifications and licenses | PMP, CPA, CDL, Security+ | Its own line under skills or certifications |
| Languages | Spanish, Mandarin, ASL | Skills section with a clear level |
| Interpersonal skills | Communication, teamwork, leadership | Named once, then evidenced in bullets |
Use the names the employer uses. If the posting says "Microsoft Excel" rather than "spreadsheets," write "Microsoft Excel." If it lists a certification, use its exact title. Consistent names make the resume easier to search and easier to match against the posting.
How many skills should you list?
Most effective skills sections land around eight to fifteen entries, separated into two or three groups. The number matters less than the ratio of relevant to irrelevant skills. Five tools you can demonstrate are worth more than twenty you have touched once.
The interview test
For every skill on the page, imagine the interviewer saying, "Tell me about a time you used that." If you would struggle to answer, move it to a learning list and take it off the resume.
If you have a lot of relevant skills, choose the ones the posting emphasizes and leave the rest in your master document. If you have very few, expand the section by adding methods you used inside projects, courses, or volunteer work, not by adding traits you cannot support.
How do you choose skills from the job posting?
Copy the posting and mark every noun that names a tool, method, certification, or capability. Put the required items first, then the preferred items. Cross off anything you cannot support with an example. What remains is your shortlist.
| Posting phrase | Skill to list | Evidence to add elsewhere |
|---|---|---|
| "Proficiency in Excel and SQL" | Microsoft Excel, SQL | A report or analysis you built |
| "Experience with project management tools" | Asana, Jira, or the tool you actually used | A project you planned and delivered |
| "Strong written communication" | Technical writing, documentation | A guide, report, or policy you authored |
| "Certified in CPR" | CPR certification | The certifying body and date |
Match the posting's wording, but do not rename a skill you do not have. If the posting asks for Tableau and you have used Power BI, list Power BI and mention in the bullet that you build dashboards and can learn the other tool quickly. Honest adjacency is stronger than a false match. NACE's 2026 Job Outlook Spring Update reports that employers look for evidence of teamwork, problem-solving, and communication on entry-level resumes, not just a skills list. When you write the proving bullet, the resume action verbs list has stronger options, and the guide to tailoring a resume to a job covers the full edit.
Should you list soft skills?
Yes, when they are relevant to the role and when at least one bullet proves them. The title alone, such as "communication," tells a reader very little. The same term backed by evidence becomes credible.
Weak (hypothetical): Skills: teamwork, communication, leadership, problem-solving.
Stronger (hypothetical): Skills: Team leadership, client communication, process improvement. In the experience section: "Led a 4-person student team to deliver a semester project two weeks early" and "Wrote weekly status updates for a 20-person program team."
Some roles weigh soft skills heavily, especially customer-facing, early-career, and management positions. For those roles, name the two or three that matter most and make sure the rest of the page shows them in action. NACE's career readiness framework names eight competencies employers look for in new graduates, including communication, critical thinking, teamwork, and professionalism. O*NET OnLine's soft skills list (U.S. Department of Labor; updated October 2026) groups related skills such as coordination, persuasion, and critical thinking, which helps when you need the right term for the section.
How should you format and organize the section?
Group skills by type, not by proficiency. Two or three labels are enough: "Tools," "Methods," and "Languages" work for many roles. Put each group on its own line with a bold label, then list the skills separated by commas. Keep the casing consistent with how the employer writes the tool name. CareerOneStop's Resume Writing Guide gives formatting its own chapter, separate from work experience and education.
| Format | Example | Why it works |
|---|---|---|
| Grouped list | Tools: Excel, SQL, Tableau. Methods: A/B testing, survey design. Languages: Spanish (professional). | Scannable and organized by type |
| Flat list | Excel, SQL, Tableau, A/B testing, survey design, Spanish | Fine for short lists of five or six |
| Bulleted list | One skill per bullet | Wastes space; use only for long technical lists |
| Rating bars | Five dots for Excel, three for SQL | Avoid; subjective and often unreadable |
Where should the skills section go on a resume?
Place it wherever it helps the reader most. For candidates with a long work history, skills usually follow experience. For career changers, recent graduates, and anyone applying for a role where the tools matter more than the timeline, move the section above experience or directly under the summary.
Order the groups by relevance to the posting, not alphabetically. The first group should be the one the employer cares most about. If you are applying to two different kinds of roles, keep two different versions of the section rather than one compromise list. If you are writing your first resume, the guide to a resume with no work experience shows how to order education and projects around the skills section.
How do you show skill levels without rating bars?
Use plain language that means something. "Advanced Excel (pivot tables, XLOOKUP, macros)" says more than four out of five dots. "Spanish (professional working proficiency)" is clearer than "fluent" if you are not fully fluent. For most tools, skip the level entirely and show the skill in a bullet instead.
| Instead of | Write |
|---|---|
| Excel ★★★★☆ | Excel (pivot tables, XLOOKUP, macros) |
| SQL — 80% | SQL (joins, aggregations, window functions) |
| Fluent | Spanish (professional working proficiency) |
| Expert | Name the specific work you have done with the skill |
Do not inflate a level
If you label yourself advanced in a tool, expect a technical question about it. An accurate "working knowledge" is safer than an overstated "expert," and interviewers can tell the difference within a few minutes.
What skills should you leave off?
Cut anything that does not help the reader decide you can do the job. That includes skills you cannot demonstrate, tools you learned once years ago, and traits that every candidate could claim.
- Skills you cannot discuss in an interview.
- Outdated software you would not be expected to use.
- Generic traits with no evidence, such as "hardworking" or "detail-oriented."
- Skills that are irrelevant to the target role and only pad the list.
- Languages you cannot use in a work conversation without overstating your level.
- Keywords copied from the posting that do not describe your actual experience.
Formatting has to survive the application system as well as the reader. If you are not sure your section will parse, check the layout rules in the ATS-friendly resume guide, then use the full resume writing guide to connect the skills section to the rest of the page.
What should you check in your resume skills section?
Run this list before you finalize the page.
- Every required skill from the posting appears, using the employer's exact name.
- The list is grouped into two or three labeled categories.
- Each skill is one you could discuss in an interview.
- The most relevant group comes first.
- The top two or three skills are also proven in experience or project bullets.
- No rating bars, stars, percentages, or vague level labels appear.
- Spelling and capitalization match the official tool or certification name.
How we researched this guide
We build resume guides from public and official sources. This page draws on O*NET OnLine's soft skills list (U.S. Department of Labor; updated October 2026), NACE's Career Readiness Competencies and its 2026 report on the skills employers seek on student resumes, and CareerOneStop's Resume Writing Guide (U.S. Department of Labor; the guide does not display a publication date).
We review this page when the underlying guidance changes and show the last-updated date at the top. If you spot an error or a source that has moved, email us — our editorial policy explains how corrections work. Examples on this page are hypothetical illustrations, not real candidates or market data.
Frequently asked questions
What skills should I put on my resume?
Start with the skills the job posting names, then add the tools, methods, and knowledge you can actually demonstrate. Mix technical or job-specific skills, such as software and certifications, with a few interpersonal skills you can support with an example. Include a skill only if you could discuss it in an interview without guessing.
How many skills should a resume list?
Aim for roughly eight to fifteen skills, grouped into two or three short categories. The exact number matters less than relevance. A focused list that matches the posting is stronger than a long list of every tool you have touched, and recruiters can scan a short grouped list far faster than a dense block of keywords.
Should soft skills go in the skills section?
Yes, but prove them. A list that says 'teamwork, communication, leadership' tells the reader little. Pair each soft skill with evidence in a bullet, such as leading a four-person project or training new hires. The skills section can name the term the posting uses, and the experience or projects section can show where you used it.
Should I rate my skills on a scale?
No. Bars, stars, and percentage ratings are subjective, hard to compare, and often unreadable to screening software. Use clear words such as 'proficient,' 'advanced,' or 'working knowledge' only when they are meaningful in your field, and prefer demonstrating the skill in a bullet over labeling a level. If the posting asks for a specific proficiency, state it plainly.
Should I include a skills section if I have little experience?
Yes. A short skills section helps a reader see what you can do, especially when your work history is thin. Keep it to two or three groups and roughly eight to twelve entries, and support the most important ones with projects, coursework, or volunteering. The skills section does not replace evidence; it names the skills, and your bullets prove them.
Can I list skills I am still learning?
Only if you can describe the level honestly. A course, a small project, or a certification in progress can justify a "working knowledge" label, especially when the posting asks for that skill. Do not list something you have never used, because interviewers ask follow-up questions. If you are actively studying, say so rather than implying proficiency.
Sources and further reading
We link to primary and official sources so you can verify the details yourself.
How this guide was written. This page is part of Role Handbook, an independent career publication. We research each guide against primary and official sources, use worked examples and scripts instead of vague advice, and update pages when the underlying rules or practices change. Every page lists its sources. See our editorial policy for details and corrections.