How to list skills on a resume in 2026 (with ATS-optimized examples by role)

Quick answer: A resume skills section in 2026 should contain 10-25 specific, role-relevant keywords organized into 3-4 categories (e.g., Technical, Tools, Analysis, Languages). Use exact phrasing from job descriptions for ATS keyword matching. Hard skills (tools, technologies, methodologies) belong here; soft skills (leadership, communication) belong in your bullets, not the skills section — because soft skills without evidence are noise. Place the skills section immediately below the summary, before work experience. The single most common mistake: listing generic soft skills ("hardworking, team player, detail-oriented") that ATS systems and recruiters both ignore.

A product designer with 6 years of experience can't get callbacks. Her resume skills section reads: "Skills: Excellent communication, creative thinker, team player, problem-solver, detail-oriented, fast learner, hardworking, passionate about design." She rewrites the section: "Design: Figma, Sketch, Framer, Principle, Adobe Creative Suite. Research: User interviews, usability testing, A/B testing, JTBD framework, Maze, Lookback. Collaboration: Cross-functional design reviews, design systems, Figma component libraries, design ops, design tokens." Same skill set, completely different signal. Callback rate goes from 1-in-25 applications to 1-in-6.

The difference isn't the underlying skills — it's whether they're concrete enough to register with both ATS keyword matching and human resume scanners. Soft skills without evidence are filler; hard skills with specific tool names and methodologies are signal. This guide covers what to put in your skills section, what to leave out, how to organize it, and role-specific keyword sets for the most common professional functions.

Key takeaways

• Hard skills belong in the skills section (tools, technologies, methodologies, languages, frameworks).
• Soft skills belong in your bullets — demonstrated through accomplishments with evidence, not listed as labels.
• Use exact phrasing from job descriptions. "Project management" and "PM" and "project management lifecycle" are not equivalent for ATS keyword matching.
• 10-25 skills is the right range. Fewer suggests thin background; more becomes keyword stuffing.
• Organize into 3-4 categories with clear labels (Technical, Tools, Languages, Methodologies, etc.).
• Tailor the skills section to each job application. The skills you list should reflect what the JD emphasizes.
• List skills you actually have. ATS-matched skills you can't discuss in interview produce instant negative impressions.

Part 1: the format

Placement

Skills section goes immediately below the summary statement, before work experience. This serves two functions:

1. ATS keyword density at the top — keywords closer to the top of the document carry more weight in some ATS scoring algorithms.
2. Recruiter first scan — most recruiters skim the top third of resumes for relevance. Skills near the top give them a fast read on fit.

Structure

Categorized skills with clear labels:

``` SKILLS

Technical: Python, SQL, JavaScript, React, AWS, Docker Analysis: Cohort analysis, A/B testing, regression modeling, SQL Tools: Jira, Linear, Figma, Notion, Mixpanel, Amplitude Languages: English (native), Spanish (conversational) ```

Categories should match what your target role values. A software engineer's skills section is heavy on Technical + Tools + Languages. A marketing manager's is heavy on Channels + Tools + Analysis + Strategy.

Length

10-25 skills total is the sweet spot. Less than 10 suggests a thin background. More than 25 starts to look like keyword stuffing — ATS systems are getting better at detecting and discounting obvious stuffing.

Specific vs. vague

Vague: "Programming languages" Specific: "Python, JavaScript, Go, Rust"

Vague: "Cloud platforms" Specific: "AWS (EC2, S3, Lambda, RDS), GCP, Azure"

Vague: "Project management tools" Specific: "Jira, Linear, Asana, Notion"

ATS keyword matching is literal — "Python" doesn't match "programming languages" even though both refer to the same thing. Specificity wins.

Part 2: hard skills vs. soft skills

Hard skills (belong in the skills section)

• Technical: programming languages, frameworks, platforms, tools
• Domain: industry-specific knowledge (HIPAA compliance, GAAP accounting, FAR contracting)
• Methodologies: Agile, Scrum, SAFe, Six Sigma, Lean Manufacturing
• Languages: spoken languages with proficiency level
• Certifications: AWS Solutions Architect, PMP, Series 7, CFA, Six Sigma Black Belt
• Software tools: specific products (Salesforce, Tableau, Adobe Creative Suite, Mathematica)

Soft skills (belong in your bullets, NOT the skills section)

• Leadership: demonstrated through "Led 4-person team" in a bullet, not listed as "Leadership"
• Communication: demonstrated through "Presented quarterly to executive team of 12" in a bullet
• Problem-solving: demonstrated through accomplishment bullets showing actual problems solved
• Teamwork / collaboration: demonstrated through cross-functional initiative bullets

Why listing soft skills fails:

1. No evidence: "Excellent communicator" without proof is unverifiable.
2. Universally claimed: every resume claims good communication and teamwork. The label adds zero discrimination.
3. ATS doesn't score them: keyword matching on "leadership" produces no signal because every candidate has it in their resume.
4. Wastes space: every word of skills section that says "team player" instead of "Python" is a word of missed ATS matching.

Exception: skills that are both technical and soft

Some skills sit between hard and soft and are appropriate for the skills section if they're tool-specific or methodology-specific:

• Project management as a domain skill is too vague; "Project management (Agile/Scrum, Jira, Linear)" is appropriate.
• Stakeholder management alone is soft; "Cross-functional stakeholder management for product launches across engineering, design, marketing, and sales" in a bullet is appropriate.
• Public speaking alone is soft; "Conference speaking (AWS re:Invent, KubeCon, RSA)" with specific events is appropriate.

Part 3: ATS keyword strategy

The skills section is the highest-density area for ATS keyword matching. Strategy:

Step 1: read the JD carefully

Identify every specific tool, technology, methodology, or domain knowledge mentioned. Note both required and "nice to have."

Step 2: identify the keywords you legitimately have

For each JD-listed skill, ask: do I have this skill in my actual capability set? If yes, list it. If no, leave it off (don't pad with skills you can't discuss).

Step 3: use exact JD phrasing

If the JD says "TypeScript," list "TypeScript" (not "TS"). If the JD says "Microsoft Excel," list "Microsoft Excel" (not "Excel"). The ATS matches literal strings.

Step 4: include adjacent terminology

For skills with multiple common terms, list both variants. "Customer Relationship Management (CRM)" matches both "CRM" searches and "customer relationship management" searches.

Step 5: don't pad

Listing skills you don't have produces:

• ATS match (good)
• Interview discussion you can't survive (very bad — interviewers ask about every skill listed)
• Long-term reputation damage

The cost of being caught padding is higher than the cost of missing one ATS keyword.

Part 4: role-specific skill examples

Software engineering

``` Technical: Python, Go, TypeScript, React, Node.js, GraphQL, REST APIs Cloud: AWS (EC2, S3, Lambda, RDS, DynamoDB), Docker, Kubernetes, Terraform Data: PostgreSQL, Redis, MongoDB, BigQuery, Kafka, Elasticsearch Tools: Git, GitHub Actions, Jira, Linear, Datadog, Sentry, PagerDuty Methodologies: Agile, Scrum, TDD, design review, on-call rotation ```

Product management

``` Strategy: Product roadmap, OKR design, product/market fit, North Star metrics, JTBD Research: User interviews, usability testing, A/B testing, customer feedback synthesis Analysis: SQL, cohort analysis, retention analysis, funnel metrics, RFM Tools: Jira, Linear, Notion, Figma, Mixpanel, Amplitude, Looker, Heap Domain: B2B SaaS, marketplaces, consumer subscription, enterprise integrations ```

Marketing

``` Strategy: Content strategy, brand positioning, GTM strategy, marketing mix modeling Channels: SEO, paid search (Google, Bing), paid social (Meta, LinkedIn, TikTok), email Analytics: Google Analytics, Adobe Analytics, attribution modeling, ROI/ROAS analysis Tools: HubSpot, Marketo, Salesforce, Ahrefs, Semrush, Google Ads, Meta Business Domain: Demand generation, content marketing, ABM, B2B SaaS, e-commerce ```

Sales

``` Process: Outbound prospecting, inbound qualification, MEDDIC, BANT, Challenger sale Domain: Enterprise SaaS, mid-market, financial services, healthcare, manufacturing Tools: Salesforce, Outreach.io, Salesloft, ZoomInfo, LinkedIn Sales Navigator Skills: Forecasting, pipeline management, deal coaching, RFP responses Industry: Cybersecurity, fintech, healthtech, EdTech ```

Finance / FP&A

``` Modeling: Three-statement modeling, DCF, LBO, M&A, scenario analysis, sensitivity Analysis: Variance analysis, cohort analysis, unit economics, contribution margin Tools: Excel (advanced — pivot tables, INDEX/MATCH, dynamic arrays, Power Query), Tableau, Hyperion, Anaplan, NetSuite Process: Annual operating plan, monthly close, board reporting, audit preparation Domain: SaaS metrics (ARR, NDR, LTV/CAC), retail/e-commerce, healthcare ```

Data engineering

``` Languages: Python, SQL, Scala, Go Pipelines: Airflow, Dagster, dbt, Spark, Beam, Kafka Warehouses: Snowflake, BigQuery, Redshift, Databricks Cloud: AWS (EMR, Glue, Lambda), GCP (Dataflow, Dataproc), Azure Synapse Tools: Git, Docker, Kubernetes, Terraform, Looker, Datadog ```

Design (UX/UI)

``` Design: Figma, Sketch, Framer, Principle, Adobe Creative Suite, InDesign Research: User interviews, usability testing, card sorting, tree testing, A/B testing Methods: Design systems, design tokens, JTBD framework, design ops, accessibility (WCAG) Tools: Maze, Lookback, UserTesting, Optimal Workshop, Notion, Linear Domain: B2B SaaS, mobile apps, fintech, healthcare, EdTech ```

Operations / People Ops

``` HRIS: Workday, BambooHR, Rippling, Justworks, Gusto, ADP Process: Performance management, compensation review, onboarding, offboarding Analytics: Headcount modeling, attrition analysis, comp benchmarking, OKR tracking Compliance: FLSA, FMLA, ADA, COBRA, ERISA, state-specific employment law Tools: Greenhouse, Lever, Ashby, 15Five, Lattice, Culture Amp ```

Part 5: certifications and credentials

If you have professional certifications, they belong in the skills section (or a separate "Certifications" section if you have many).

Common certifications by industry:

• Tech: AWS Solutions Architect, AWS DevOps Engineer, Google Cloud Professional, CKA (Kubernetes), CISSP, CEH
• Project management: PMP, CSM, SAFe, Six Sigma Green Belt, Six Sigma Black Belt
• Finance: CFA (Levels I/II/III), CPA, CFP, Series 7, Series 63, Series 65, Series 79
• Healthcare: RN, BSN, MSN, NP, MBA-HCA, CPHIMS
• Marketing: Google Ads Certified, HubSpot Inbound, Facebook Blueprint, AMA PCM
• Education: PD certifications, state-specific teaching licenses, Praxis

Format: "AWS Solutions Architect Associate (2024)" — include year for currency.

Part 6: languages

If you speak multiple languages, list them with proficiency level using a clear scale:

• Native — first language, full fluency including idiom
• Fluent / professional working — comfortable in business contexts
• Conversational — daily-life and basic professional contexts
• Basic / elementary — limited utility; only include if directly relevant to the role

Standard format: "English (native), Spanish (fluent), Mandarin (conversational)"

For international roles or roles explicitly requiring language skills, the language section can be more prominent — sometimes its own section above Education.

Part 7: when to tailor the skills section

The skills section should change for each application based on the JD. Specifically:

• Add JD-specific keywords you have but didn't include in the previous version.
• Reorder categories to lead with what the JD emphasizes most.
• Remove skills that aren't relevant to the target role (don't bury the relevant ones).

This is part of the broader resume tailoring workflow.

Part 8: common skills-section mistakes

Mistake: skills listed as paragraph text

Putting skills in flowing prose makes ATS parsing harder and recruiter scanning harder. ATS systems work better with clean, comma-separated lists organized by category. Always use list or category format, not paragraphs.

Mistake: skills proficiency ratings

"Excel: ★★★★★" or "Python: Advanced" rarely helps. Self-ratings are unverifiable. Either you can do the work in an interview or you can't; the rating doesn't change that. Exception: language proficiency, where a clear scale (native/fluent/conversational) is genuinely informative.

Mistake: outdated technologies listed prominently

Listing "Windows XP, Internet Explorer, Microsoft Office 2010" signals that your skill stack hasn't refreshed. List current versions or omit. If a specific old technology is genuinely required for the target role (some financial institutions still use legacy systems), call out the version.

Mistake: skills that don't match the actual role

A backend engineer's resume listing Figma and Adobe Creative Suite signals lack of focus. A product manager's resume listing 14 programming languages suggests they may not be a real PM. Tailor the skills section to the role; don't dump every skill you've ever touched.

Mistake: not aligning the skills section to the rest of the resume

Skills listed in the skills section should also appear demonstrated in bullets. If you list "SQL" but no bullet mentions SQL work, the ATS keyword match is hollow and the human reader notices the gap. Make sure listed skills are backed by evidence in the work history bullets.

Editorial methodology

This guide reflects 2026 U.S. professional resume conventions across the major white-collar industries. Specific skill norms vary by industry, geography, seniority, and ATS platform. Major 2026 ATS platforms include Workday, Greenhouse, Lever, iCIMS, Ashby, and SmartRecruiters; each parses skills sections slightly differently, but the principles in this guide apply across them. This guide is informational, not professional career-counseling advice. Last reviewed: 2026-05-12.

For broader resume guidance, see How to write resume bullets in 2026, How to tailor your resume to a job description, How to beat the ATS in 2026, and Career change resume in 2026.

If you're updating your resume to support an active job search and salary negotiation, see What is total compensation? — the comp negotiation is downstream of the resume work; both matter.