Resume Skills Section Examples for 2026: What to Write and Where

Q: How many skills should I put on my resume?

Aim for 8-12 skills that directly mirror the language of the specific job posting. The average job posting explicitly names 11-15 required skills, and ATS-optimized resumes that list 8-12 direct keyword matches score highest in automated screening. More than 15 skills dilutes your signal. Fewer than 6 leaves keyword match potential untapped. Quality and specificity matter more than quantity.

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

Hard skills are specific, measurable abilities: Python, Bloomberg Terminal, Six Sigma Green Belt, Salesforce. ATS systems weight these heavily because they are precisely matchable against job posting language. Soft skills are interpersonal abilities like communication and leadership. They have limited ATS value because they appear on 70%+ of resumes and are too vague to differentiate. Prove soft skills through your experience bullets, not your skills list.

Q: Should I rate my skills on my resume (beginner/intermediate/expert)?

Use proficiency descriptors only when the level distinction matters for the role. 'SQL (advanced)' versus 'SQL (intermediate)' is meaningful to a hiring manager evaluating analytical depth. 'Python (intermediate)' sets accurate expectations if the role requires advanced Python. Skip proficiency labels for binary skills and avoid visual star ratings or percentage bars, which are meaningless to ATS and recruiters.

Q: Where should the skills section go on a resume?

For strong work histories (5+ years): after the experience section. For career changers or recent graduates: before the experience section to frame your skills before revealing limited history. For technical roles (engineering, data, finance): immediately after the summary, since recruiters scan for specific tools first. For senior leadership: after experience, or omit a dedicated skills section entirely and weave skills into experience bullets.

Q: What skills are ATS systems actually looking for?

ATS systems match your resume text against the specific language in the job posting. They look for exact or near-exact matches: tool names (Tableau, Jira, Salesforce), methodology terms (Agile, Six Sigma, GAAP), certification names (PMP, CPA, AWS-SAA), and role-specific technical terms. Vague phrases like 'strong analytical skills' score poorly. Using the same terminology as the job description is the most reliable way to improve your ATS match score.

Q: Should I have separate sections for technical skills and soft skills?

Separate them only if both sections are substantive. A common approach is a single 'Skills' section with category headers (Technical, Methodologies, Tools, Languages) rather than a hard split between hard and soft. Soft skills listed without evidence are weak, so consider removing them from the dedicated section and instead demonstrating them through quantified bullets in your experience section.

"Communication skills" appears on 76% of all resumes, making it nearly useless as an ATS differentiator (general resume data, 2025). Your skills section is prime ATS real estate: the average job posting explicitly names 11-15 required skills, and resumes that list 8-12 direct keyword matches score highest in automated screening. But most candidates either list too many generic skills or too few specific ones. This guide shows you exactly what filled-in skills sections look like across five industries, with formatting rules that maximize ATS match scores.

Why the Skills Section Matters for ATS

ATS platforms like Workday, Greenhouse, and Taleo parse your resume looking for keyword matches against the job description. The skills section is one of the highest-density keyword areas on your resume because it contains role-specific terms without the surrounding prose that can dilute match signals.

The critical distinction: ATS systems weight hard skills more heavily than soft skills because hard skills are precisely matchable. "Python" matches "Python." "Tableau" matches "Tableau." "Strong communicator" is too vague to score reliably against specific job posting language.

Hard Skills vs. Soft Skills: ATS Behavior

Hard Skills (ATS-parseable)

Specific tools: Salesforce, Jira, Tableau, Python
Methodologies: Agile, Scrum, Six Sigma, GAAP
Certifications: PMP, CPA, CCRN, AWS-SAA
Technical abilities: SQL, financial modeling, DCF analysis

Soft Skills (limited ATS value)

"Strong communicator" (appears on 76% of resumes)
"Team player," "detail-oriented," "results-driven"
"Leadership skills" (without context)
"Problem-solving ability"

The implication: soft skills belong in your experience bullets, where they are supported by evidence. "Presented quarterly findings to C-suite, resulting in $2M budget approval" proves communication more credibly than listing "strong communicator" in a skills section. Use your skills section for hard skills; let your bullets demonstrate the soft ones.

The 60/40 rule: Aim for roughly 60% hard skills and 40% soft skills in your dedicated skills section. For most roles, your hard skills are the primary filter criteria; soft skills add context but don't drive screening decisions (general resume best practice data, 2025).

How Many Skills to List and How to Format Them

The optimal range is 8-12 skills that directly mirror the language of the specific job posting. Listing 20+ skills dilutes your signal and can read as padding. Listing 4-5 skills leaves keyword match potential untapped.

Grouping beats flat lists. A comma-separated list of 15 skills is harder to scan than a categorized two-column layout. Grouping also signals to both ATS and human reviewers that your skills cluster into coherent domains.

Flat List vs. Categorized Format

Flat list (harder to scan, no context):

Excel, Python, SQL, Tableau, communication, team leadership, financial modeling, PowerPoint, data analysis, budgeting, problem-solving, Salesforce

Categorized format (ATS-friendly, readable):

Financial Modeling: DCF, LBO models, comparable company analysis, variance analysis

Technology: Excel (advanced, VBA), Python (pandas), SQL (intermediate), Tableau, Power BI

Business: Annual budgeting, FP&A, stakeholder presentations, cross-functional project management

Skill Proficiency Levels: When to Include Them

Add proficiency context only when the difference matters for the role. "SQL (intermediate)" is useful if the job requires advanced SQL and you want to set accurate expectations. "Excel (advanced, VBA)" differentiates you from candidates who can only do basic spreadsheet work. Skip proficiency labels for binary skills where you either have them or you don't ("Python" vs. "Python (familiar)").

Avoid self-rating scales like "Python: ★★★☆☆" or "Excel: 4/5." These are meaningless to ATS and recruiters. Use descriptors ("intermediate," "advanced," "expert") only when they add genuine signal.

Resume Skills Section Examples by Industry

Software Engineer / Data Engineer Skills Section

Technical Skills Section: Software Engineer

Languages: Python, Java, TypeScript, SQL, Go

Frameworks & Tools: React, Node.js, Spring Boot, FastAPI, Docker, Kubernetes

Cloud & Data: AWS (EC2, S3, Lambda, RDS), PostgreSQL, Redis, Kafka, Spark

Practices: CI/CD, Agile/Scrum, test-driven development, code review, system design

AI/ML Tools: LangChain, OpenAI API, Hugging Face, PyTorch (familiarity)

Marketing Manager Skills Section

Skills Section: Marketing Manager

Digital Marketing: SEO, paid search (Google Ads), paid social (Meta, LinkedIn), email marketing, content strategy

Analytics: Google Analytics 4, Semrush, HubSpot, Marketo, Salesforce CRM, A/B testing

Content: Copywriting, brand voice, editorial calendar management, campaign briefing

Skills: Demand generation, marketing operations, budget management, cross-functional collaboration

Project Manager Skills Section

Skills Section: Project Manager

Methodologies: Agile, Scrum, Waterfall, Kanban, PRINCE2

Tools: Jira, Asana, MS Project, Smartsheet, Confluence, Monday.com

Project Skills: Risk management, scope management, stakeholder reporting, resource planning, budget oversight

Credentials: Project Management Professional (PMP), Certified Scrum Master (CSM)

Healthcare / Clinical Skills Section

Skills Section: Registered Nurse (ICU)

Clinical Skills: Mechanical ventilation, hemodynamic monitoring, arterial line management, CRRT, vasopressor titration, rapid assessment

Technology: Epic EMR, Cerner, Meditech, Pyxis medication dispensing

Certifications: Registered Nurse (RN, active), Basic Life Support (BLS), Advanced Cardiac Life Support (ACLS), Critical Care Registered Nurse (CCRN)

Operations / Supply Chain Skills Section

Skills Section: Operations Manager

Operations: Process improvement, Lean/Six Sigma, KPI development, cost reduction, vendor management

Supply Chain: Inventory management, demand forecasting, warehouse management, logistics coordination, ERP systems (SAP, Oracle)

Analytics: Excel (advanced), Power BI, Tableau, SQL (intermediate)

Credentials: Lean Six Sigma Green Belt, APICS CSCP (certified supply chain professional)

Where to Place the Skills Section on Your Resume

Placement depends on your experience level and whether your skills or your work history is the stronger signal.

Scenario	Placement	Why
Strong work history, 5+ years	After work experience section	Let your career progression speak first; skills reinforce it
Career changer or recent grad	Before work experience section	Lead with skills that transfer; frame before revealing experience gaps
Technical role (engineering, data, finance)	After summary, before experience	Recruiters scan for specific tools immediately in technical hiring
Executive or senior leadership role	After work experience or omit dedicated section	Your career record is the credential; skills lists are for junior roles

One positioning rule applies universally: if you use a single-column resume layout, the skills section goes above the fold (within the first 2/3 of the first page). ATS parses the full document, but human reviewers skim the top.

Before/After Skills Section Makeovers

Makeover 1: Marketing Manager

Marketing Manager Skills: Before and After

Before:

Skills: Microsoft Office, communication, social media, creative thinking, teamwork, marketing, customer service, analytical skills, leadership, Google

After:

Digital Marketing: SEO (on-page, technical), Google Ads, Meta Ads Manager, LinkedIn Campaign Manager, email marketing (HubSpot)

Analytics: Google Analytics 4, Semrush, Looker, A/B testing, conversion rate optimization

Operations: Campaign management, editorial calendar, budget tracking, cross-functional project coordination

Makeover 2: Data Analyst

Data Analyst Skills: Before and After

Before:

Skills: Data analysis, Excel, Python, critical thinking, attention to detail, reporting, SQL, statistics, PowerPoint, problem solving

After:

Analysis & Modeling: SQL (advanced), Python (pandas, NumPy, scikit-learn), R (intermediate), statistical analysis, regression modeling, A/B testing

Visualization: Tableau, Power BI, Matplotlib, Seaborn, Excel (advanced, pivot tables, VBA)

Data Engineering: dbt, Snowflake, BigQuery, Airflow (familiarity), data pipeline maintenance

AI and Emerging Skills to Add in 2026

AI skills demand surged 866% year-over-year in job postings (LinkedIn Workforce Report, 2025). In 2026, basic AI fluency is increasingly a baseline expectation rather than a differentiator. Here is how to list AI skills without overstating your proficiency:

Role Type	AI Skills to List	Phrasing
Non-technical (marketing, ops, HR)	Prompt engineering, ChatGPT/Claude for content, AI workflow automation	"AI-assisted content creation (Claude, ChatGPT, Midjourney)"
Technical (engineering, data)	LLM APIs, RAG pipelines, vector databases, GitHub Copilot	"LLM integration (OpenAI API, LangChain, Pinecone)"
Product management	AI product development, prompt engineering, model evaluation	"AI product development, LLM evaluation frameworks"
Finance / Analysis	AI-assisted data analysis, Python for ML (basic), automation tools	"Python for data analysis and ML (scikit-learn, pandas)"

Only list AI skills you can demonstrate. Claiming "machine learning" or "deep learning" as a skill when your only exposure is a weekend tutorial will fail scrutiny in any technical interview. List what you have actually used in work or substantive projects.

Get your skills match score: Paste your resume and a target job description into Resume Optimizer Pro to see exactly which skills from the posting are missing from your resume and where to add them.