Resume Skills Section: What to Include and How to Format It [2026 Guide]

Your skills section is one of the highest-leverage parts of your entire resume. It's compact, scannable, and directly feeds the algorithms that decide whether a human ever sees your application.

According to Jobscan's recruiter survey data, 76.4% of recruiters use skills-based filters in their Applicant Tracking Systems. That means if the right keywords aren't sitting in your skills section, your resume is being filtered out before anyone reads your carefully crafted experience bullets.

Having reviewed hundreds of CVs as part of hiring teams, I can tell you that the skills section is where most applicants leave the easiest points on the table. It takes five minutes to get right, and most people never bother.

Why Your Skills Section Matters More Than You Think

Let's start with the numbers.

Three things are happening simultaneously when a recruiter opens your resume:

1. ATS keyword matching parses your skills section for exact-match terms from the job description. This is automated and happens before a recruiter ever sees your name.
2. The 7-second scan is when a human recruiter glances at your resume. Skills sections are among the first things their eyes land on because they're visually distinct and easy to scan.
3. Shortlisting decisions often come down to whether the recruiter can quickly confirm you have the technical capabilities they need.

Your skills section serves all three of these gatekeepers. If it's weak, vague, or poorly formatted, you're fighting an uphill battle on every front.

I covered the ATS side in depth in our ATS-friendly resume guide, but the short version is: your skills section is where keyword matching starts. Get this wrong and your resume is invisible.

Hard Skills vs Soft Skills (and Why It Matters)

This is the single most misunderstood distinction in resume writing. Here's the breakdown:

Hard skills: list them explicitly

Hard skills are the currency of ATS filtering. When a recruiter sets up a filter for "Python" or "Salesforce" or "GAAP compliance," they're looking for those exact terms on your resume. Your skills section is where those terms need to live.

Be specific. "Data analysis" is okay. "SQL, Python (Pandas, NumPy), Tableau, Power BI" is significantly better. The more precise you are, the more filters you pass and the more credible you appear to human readers.

Soft skills: demonstrate, don't list

Here's a truth that most resume advice gets wrong: listing soft skills in your skills section is almost always a waste of space.

Every single applicant lists "communication" and "teamwork." It's meaningless. Recruiters don't filter for soft skills in ATS, and seeing "problem-solving" next to "JavaScript" actually dilutes the impact of your technical skills.

Instead, demonstrate soft skills through your experience bullets. Compare these approaches:

Weak (skills section): Communication, Leadership, Problem-Solving

Strong (experience bullet): Led cross-functional team of 12 across 3 time zones to deliver product launch 2 weeks ahead of schedule, presenting weekly progress updates to C-suite stakeholders.

The second approach proves communication, leadership, and problem-solving all at once, with evidence. That's infinitely more persuasive than a word in a list. For more on writing strong achievement bullets, see our guide on action verbs for your resume.

The mistake everyone makes

I see this on roughly 8 out of 10 CVs I review: skills sections stuffed with "Communication, Teamwork, Time Management, Problem-Solving, Adaptability."

These words carry zero weight in ATS filtering and take up space that could be used for the hard skills that actually get you past the bots. Every soft skill in your skills section is a missed opportunity to include a technical keyword that could trigger a match.

How Many Skills Should You List?

The optimal number depends on your role and industry, but here are solid benchmarks based on what I've seen work:

The key principle: every skill on your list should be something you could discuss confidently in an interview for at least two minutes. If you can't explain how you've used it, it shouldn't be there.

Padding your skills section with keywords you barely know is a trap. It might get you past ATS, but it will catch up with you in the interview. I've written about this and other pitfalls in our common resume mistakes guide.

How to Format Your Skills Section

Formatting matters more than most people realise. A well-structured skills section is easier for both ATS and humans to parse. Here are the three main approaches:

1. Simple list format (best for most roles)

This is the cleanest option for non-technical roles. A single line or small block of comma-separated skills.

Skills: Project Management, Stakeholder Engagement, Budgeting and Forecasting, Agile Methodology, Jira, Confluence, Risk Assessment, Vendor Management

When to use: business roles, marketing, operations, project management, and any role where you have fewer than 12 skills to list.

2. Categorised format (best for technical roles)

When you have 12 or more skills, grouping them into categories makes the section scannable and organised.

Languages: Python, JavaScript, TypeScript, SQL, Go

Frameworks: React, Next.js, Django, FastAPI

Cloud and DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, Terraform, CI/CD

Databases: PostgreSQL, MongoDB, Redis, DynamoDB

Methodologies: Agile, Scrum, TDD, Microservices Architecture

When to use: software engineering, data science, DevOps, and any role with a broad technical toolkit.

3. Proficiency levels (use with caution)

Some candidates add proficiency indicators (Expert, Advanced, Intermediate) or visual bars next to each skill. My advice: avoid this in most cases.

Here's why:

• ATS cannot parse visual skill bars or star ratings
• Labelling yourself "Intermediate" at something invites scrutiny
• It adds visual clutter without adding information
• Recruiters care about whether you have the skill, not your self-assessed rating

The one exception is language proficiency (as in spoken languages), where levels like "Native," "Fluent," and "Conversational" are genuinely useful and expected.

Before and after: a real formatting improvement

Before:

Skills: Microsoft Excel, Communication, Python, Leadership, Data Analysis, Teamwork, SQL, Problem Solving, Tableau, Adaptability, R, Time Management

After:

Technical Skills: Python, R, SQL, Tableau, Power BI, Advanced Excel (VLOOKUP, Pivot Tables, Macros)

Data and Analysis: Statistical Modelling, A/B Testing, Regression Analysis, Data Visualisation, ETL Pipelines

Tools: Jupyter, Git, Snowflake, dbt, Airflow

The "before" version mixes hard and soft skills randomly, includes generic terms, and is hard to scan. The "after" version is categorised, specific, and packed with ATS-friendly keywords. Same person, vastly different impression.

Skills to Include by Industry

One of the most common questions I get is "what skills should I actually put?" The answer depends entirely on your target industry. Here are the most in-demand skills for six major sectors in 2026, based on job posting analysis.

Technology

Marketing

Finance

Healthcare

Design

Project Management

These aren't exhaustive. They're starting points. The best approach is to cross-reference these with the specific job descriptions you're targeting, which brings us to one of the most important skills in job searching itself.

Skills to Leave Off Your Resume in 2026

Some skills actively hurt your resume. They signal that you're padding, out of touch, or not clear on what the role requires. Here's what to remove:

Microsoft Office / Google Workspace. In 2026, listing Word, Excel, PowerPoint, or Google Docs as skills is like listing "can use a telephone." These are assumed baseline competencies. The exception: if you have genuinely advanced capabilities (Excel macros, complex pivot tables, Apps Script automation), list those specific capabilities instead.

"Basic computer skills." This phrase should never appear on any resume, for any role, at any level. It signals a fundamental misunderstanding of what employers are looking for.

Email. No.

Social media (unless you're in marketing). "Social media" as a skill is meaningless unless you're applying for a role that involves managing social media professionally. And even then, list the specific platforms and tools: "Meta Business Suite, Hootsuite, Social Media Analytics" rather than just "social media."

Soft skills without evidence. As discussed above, "communication" and "teamwork" in your skills section add nothing. Move them to your experience bullets where you can prove them with results.

Outdated technologies. Unless the job posting specifically requests it, remove legacy technologies that signal you haven't kept current. This includes things like jQuery (in frontend roles), COBOL (unless applying to banks that still use it), Flash, or Dreamweaver. When in doubt, check whether the technology appears in recent job postings for your target roles.

Typing speed. Unless you're applying for a data entry or transcription role, nobody cares about your WPM.

A good rule of thumb: if a skill wouldn't impress someone who's been working in your target industry for five years, it probably doesn't belong on your resume.

AI Skills: The New Must-Have

I wrote a comprehensive guide on AI skills for your resume, but here's the short version: AI literacy is no longer optional for most knowledge workers.

PwC's Global AI Jobs Barometer found that AI skills now command a 56% wage premium, up from 25% just one year ago. And 75% of AI job listings are looking for domain experts who can use AI, not AI specialists.

The key mistake people make: listing "AI" or "familiar with AI tools" as a skill. That's far too vague. Instead, be specific:

Weak: AI, Machine Learning, ChatGPT

Strong: Prompt Engineering, GPT-4/Claude API Integration, AI-Assisted Data Analysis (Python + LangChain), RAG Pipeline Development

If you're not in a technical role, you can still list AI skills effectively:

Marketing: AI Content Optimisation, Predictive Audience Segmentation, AI-Powered A/B Testing

Finance: AI-Assisted Financial Modelling, Automated Report Generation, LLM-Based Document Analysis

Operations: AI Workflow Automation, Intelligent Process Mining, Predictive Maintenance

Name the specific tools you use. "Midjourney for visual asset creation" beats "AI image generation" every time. Specificity is what separates a credible AI skill from a buzzword.

How to Match Skills to Job Descriptions

This is where most applicants fail. They create one skills section and use it for every application. That's a strategy for getting filtered out, not for getting interviews.

Here's the process I recommend:

Step 1: Read the job posting like a recruiter

Go through the job description and highlight every skill, tool, technology, and qualification mentioned. Pay special attention to:

• The "Requirements" or "Qualifications" section (these are the ATS filter terms)
• Repeated terms (if they mention "Agile" three times, it's important)
• The order skills are listed in (first usually means most important)

Step 2: Mirror their exact terminology

If the job posting says "Salesforce," don't write "CRM software." If they say "stakeholder management," don't write "working with people." ATS systems match on exact terms, and human recruiters recognise their own language.

Job posting says: "Experience with CI/CD pipelines"

Your skills section says: CI/CD (Jenkins, GitHub Actions, CircleCI)

You've matched their keyword and added specificity. That's the formula.

Step 3: Include both acronyms and full terms

Some ATS systems match on exact strings. If the system searches for "SEO" and you've only written "Search Engine Optimisation," you might miss the match (and vice versa). The safest approach is to include both:

SEO/Search Engine Optimisation, PMP (Project Management Professional), AWS (Amazon Web Services)

This covers all possible search variations. It's a small detail that makes a measurable difference.

Step 4: Only list skills you can back up

This seems obvious, but the temptation to add a few extra keywords is real. Don't do it. Interviewers will ask about the skills on your resume. If you list "Kubernetes" and can't explain what a pod is, you've done more damage than if you'd left it off entirely.

A good test: could you complete a task using this skill within your first week on the job, with minimal guidance? If yes, list it. If no, leave it off or invest time learning it before your application.

If tailoring sounds like a lot of work, tools like JobSprout make it faster. You can toggle sections on and off, reorder content for different applications, and use the AI Writer to rephrase bullets to better match a specific job description. It turns a 30-minute tailoring session into a 5-minute one. JobSprout's one-click job tailoring goes further: paste a job description and your skills section is automatically reordered and optimised to match what the employer is looking for, with a diff preview showing exactly what changed.

Common Skills Section Mistakes

After reviewing hundreds of resumes, these are the patterns that consistently hurt applicants:

1. Listing skills you don't actually have

This is the most dangerous mistake. It might get you past ATS, but it creates a credibility gap that's almost impossible to recover from in an interview. Technical interviewers will probe your listed skills. Getting caught in a bluff doesn't just cost you the role. It costs you your reputation with that company.

2. Using vague descriptors

"Proficient in various tools" tells the reader nothing. "Various" is a red flag word on any resume. Be specific, always.

Bad: Proficient in various programming languages and development tools

Good: Python, JavaScript, TypeScript, Go. Tooling: VS Code, Docker, Git, Jira

3. Keyword stuffing

Some applicants try to game ATS by cramming every possible keyword into their skills section, including skills they've barely touched. Modern ATS systems are increasingly sophisticated at detecting this, and human recruiters will spot it immediately. A focused list of 10 genuine skills beats a padded list of 30 every time.

4. Forgetting to update for each application

Your skills section should change with every application. Not dramatically, but the emphasis and ordering should reflect the specific job description. A generic skills section is a sign that you're mass-applying rather than targeting. Recruiters notice.

If tailoring your resume for every application sounds exhausting, I get it. That's precisely the kind of repetitive optimisation work that JobSprout was built to handle. Upload once, tailor to each role in seconds.

5. Burying technical skills below soft skills

If you're in a technical field, your hard skills should come first. Recruiters scanning your resume in those critical 7.4 seconds are looking for technical capabilities. Making them hunt past "Communication, Teamwork, Adaptability" to find "Python, AWS, Kubernetes" is costing you interviews.

Put your strongest, most relevant hard skills at the top of the section. Always.

6. Using an inconsistent format

Pick one format and stick with it. Don't mix comma-separated skills with bulleted lists with categorised groups. Consistency signals attention to detail, something every employer values.

For a comprehensive look at formatting, check our how to write a resume guide, which covers every section including skills placement and ordering.

Putting It All Together: A Skills Section Checklist

Before you submit your next application, run through this checklist:

• Every skill listed is something you could discuss confidently for 2 minutes in an interview
• Hard skills are listed explicitly with specific tool names and versions where relevant
• Soft skills are demonstrated in your experience section, not listed in skills
• Skills are categorised if you have more than 10 to 12
• You've mirrored the exact terminology from the job description
• Both acronyms and full terms are included for key skills
• Outdated or assumed skills (Microsoft Office, email, basic computer skills) are removed
• AI-related skills are specific and tool-based, not generic
• The section is formatted consistently and easy to scan
• You've updated the section specifically for this application

If you can tick every box, your skills section is in strong shape. Combine it with a well-written resume summary and quantified experience bullets, and you'll be ahead of the vast majority of applicants.

Frequently Asked Questions

Should I put skills at the top or bottom of my resume?

For most roles, place your skills section near the top of your resume, just below your summary or professional statement. This ensures both ATS and human recruiters encounter your keywords early. The exception is if you have highly relevant and impressive work experience that speaks for itself, in which case experience can come first. But even then, a brief skills section in the top third of the page is generally more effective than burying it at the bottom.

How do I list skills I'm currently learning?

Don't list skills you're still in the early stages of learning. If you've completed a course, built a project, or used a tool in any meaningful way, it's fair to include. If you're mid-course with no practical application yet, leave it off and add it once you can speak to real usage. Listing "Currently learning Python" doesn't help you. Listing "Python (completed Google Professional Certificate, built 3 data analysis projects)" does.

Should I include a separate "Technical Skills" section and a "Core Competencies" section?

You can, but only if both sections are genuinely adding value. A "Technical Skills" section with specific tools and technologies plus a "Core Competencies" section with role-specific strategic capabilities (not soft skills) can work well for senior roles. For most applicants, a single well-organised skills section is cleaner and more effective. Two sections are justified when you have 15 or more skills that naturally fall into distinct categories.

What if I'm changing careers and don't have industry-specific skills?

Focus on transferable technical skills that apply across industries: data analysis, project management tools, CRM platforms, and communication tools. Supplement these with any industry-specific knowledge you've gained through courses, certifications, or personal projects. Be honest about your skill level, but don't undersell transferable capabilities. "Budget management and forecasting" is relevant in almost any industry, for example. Our resume writing guide has a dedicated section on career changers.

How often should I update my skills section?

Update it for every application (adjusting keywords to match the job description) and do a full overhaul every 3 to 6 months. Technology and industry expectations shift quickly. Skills that were cutting-edge 12 months ago may now be baseline expectations, and new tools emerge constantly. Set a recurring reminder to audit your skills section and remove anything outdated, adding new capabilities you've developed. Keeping a running "skills inventory" document makes this much easier.

Get Your Skills Section Right, Starting Now

Your skills section is small but powerful. It's the part of your resume that ATS systems scan first, that recruiters' eyes land on during their 7-second review, and that determines whether you make it to the shortlist or disappear into the rejection pile.

The good news: getting it right isn't complicated. Be specific, be honest, match the job description, and focus on hard skills that prove your capability. That alone puts you ahead of the majority of applicants who are still listing "Communication, Teamwork, Microsoft Office."

If you want to build a resume with a well-structured skills section from the start, JobSprout gives you professionally designed templates that are already formatted for ATS compatibility and easy skills scanning. Use the AI Writer to refine your content, and toggle sections on and off as you tailor for each application.

Your skills tell employers what you can do. Make sure the right ones are on the page.

Questions about your skills section? Email david@jobsprout.ai or connect on LinkedIn.