Skills to Put on a Resume in 2026 (100+ Examples by Role)

The "Skills" section is the most mishandled part of most resumes. Job seekers either stuff it with buzzwords ("team player, go-getter, self-starter") or leave it generic to the point of uselessness ("Microsoft Office, communication, problem solving").

Meanwhile, applicant tracking systems (ATS) use that exact section to decide whether you match the role. Get it wrong and you're filtered out before a human sees your name.

This guide fixes that. You'll get 100+ real skill examples by role, the difference between skills that help and skills that hurt, and how to match your skills section to the ATS keywords that actually trigger callbacks.

The Two-Minute Rule for Picking Skills

Before you list a single skill, open the job description you're targeting and do this:

1. Copy the job description into a text document.
2. Highlight every noun that sounds like a skill (tool, language, framework, methodology, soft skill).
3. Cross-reference against your actual experience. Which ones can you honestly claim?
4. List those on your resume, exactly as worded in the JD.

That's it. The skills section isn't about listing everything you've ever touched — it's about signaling "I have exactly what you asked for" to both the ATS and the human reader.

Hard Skills vs Soft Skills — and Why the Balance Matters

Hard skills are specific, teachable, and usually tool- or process-based. They're the ones ATS parsers love because they're concrete and searchable. Examples: Python, SQL, Figma, Salesforce, French (B2), SEO, Agile/Scrum, financial modeling, CAD, video editing in Premiere Pro.

Soft skills are harder to measure but often the thing that actually gets you hired once you're in the room. ATS parsers rarely trigger on soft skills, but human readers weight them heavily. Examples: stakeholder management, cross-functional collaboration, executive communication, mentoring, conflict resolution.

The right ratio for 2026: About 70% hard skills, 30% soft skills in your skills section. List 8–12 skills total — more looks like padding, less looks like you're hiding something.

What to Cut from Your Skills Section (Immediately)

• "Microsoft Office" or "Microsoft Word." It's 2026. Recruiters assume you can use a word processor.
• "Communication." Everyone claims it. Without context, it means nothing. Replace with "Executive presentation," "Technical writing," or "Client-facing communication."
• "Hardworking" / "Team player" / "Go-getter." Not skills. Adjectives. Every candidate uses them.
• Languages you took in high school. Unless you can hold a professional conversation, don't list it.
• Software from 10 years ago (unless it's still industry-standard).
• Generic buzzwords without a system attached. "Leadership" alone is weak. "Cross-functional team leadership" is fine and credible.

100+ Skills Organized by Role

Pull from these based on what fits your actual experience AND the job description. Don't list skills you can't back up if asked in an interview.

Software Engineering / Technical

Languages & Frameworks: Python, JavaScript, TypeScript, Go, Rust, Java, C++, C#, Ruby, Swift, Kotlin, React, Next.js, Vue.js, Angular, Node.js, Django, Flask, Spring Boot, .NET, Laravel, Rails

Data & Infrastructure: PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, GraphQL, REST APIs, gRPC, AWS (EC2, S3, Lambda, RDS), GCP, Azure, Kubernetes, Docker, Terraform, CI/CD, GitHub Actions, Jenkins

Practices: Test-driven development, Code review, Microservices architecture, Event-driven design, Agile/Scrum, System design, Performance optimization, Security best practices

Data / Analytics

SQL, Python (pandas, NumPy, scikit-learn), R, Tableau, Power BI, Looker, dbt, Snowflake, BigQuery, Databricks, Airflow, Statistical modeling, A/B testing, Experiment design, Cohort analysis, Regression analysis, Forecasting, Data visualization, ETL, Data warehousing

Product Management

Roadmap planning, User research, Product strategy, Stakeholder management, JIRA, Linear, Figma, Miro, Notion, Productboard, Amplitude, Mixpanel, A/B testing, OKR frameworks, Agile, Scrum, Kanban, User story writing, PRD writing, Cross-functional leadership, Technical fluency, Go-to-market strategy

Design / UX

Figma, Adobe XD, Sketch, Framer, Principle, InVision, Prototyping, Wireframing, User research, Usability testing, Design systems, Accessibility (WCAG), Interaction design, Information architecture, Motion design, Design ops, HTML/CSS, Adobe Creative Suite

Marketing

SEO, SEM, Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Google Analytics 4, Google Tag Manager, HubSpot, Marketo, Salesforce Marketing Cloud, Mailchimp, Klaviyo, Email marketing, Lifecycle marketing, Content strategy, Brand strategy, Marketing analytics, Attribution modeling, CRO, Performance marketing, Growth marketing, B2B marketing, B2C marketing

Sales

Salesforce CRM, HubSpot CRM, Outreach, Salesloft, Gong, Lead generation, Prospecting, Cold outreach, Discovery calls, Solution selling, MEDDIC, SPIN selling, Challenger sale, Pipeline management, Forecasting, Contract negotiation, Account management, Territory planning, Quota carrying, Upselling, Cross-selling, Customer retention

Finance / Accounting

Financial modeling, Forecasting, Budgeting, Variance analysis, Excel (advanced), SQL, Bloomberg Terminal, FactSet, NetSuite, QuickBooks, SAP, Oracle Financials, GAAP, IFRS, Audit, FP&A, Capital planning, Cash flow analysis, Valuation (DCF, comps, precedent transactions), M&A analysis

Operations / Project Management

PMP, PRINCE2, Agile, Scrum, Lean, Six Sigma, Kanban, JIRA, Asana, Monday, Smartsheet, Project scheduling, Resource allocation, Risk management, Vendor management, Process improvement, SOPs, KPI tracking, Cross-functional collaboration, Stakeholder communication

General Soft Skills (Use Sparingly, With Context)

Executive communication, Written communication, Public speaking, Cross-functional collaboration, Stakeholder management, Mentoring and coaching, Conflict resolution, Decision-making under uncertainty, Prioritization, Adaptability, Analytical thinking, Systems thinking, Customer empathy, Strategic thinking

How to Match Your Skills to ATS Keywords

This is the part most job seekers skip — and it's the single biggest lever on whether your resume gets through.

Step 1: Scrape the exact keywords from the job description. Look at the "Requirements" and "Qualifications" sections. Every skill listed there is a keyword the ATS will scan for. If they wrote "Salesforce CRM," use "Salesforce CRM" on your resume — not "SFDC," not "CRM systems."

Step 2: Check which of those keywords already appear on your resume. Go through your resume and highlight every instance. Missing a key term? Add it (if you can honestly claim it).

Step 3: Prioritize keywords that appear multiple times in the JD. If a JD mentions "Python" once and "SQL" five times, SQL is clearly higher-weighted. Make sure SQL shows up in your skills section AND at least one bullet point.

Step 4: Don't stuff keywords where they don't belong. ATS systems are reasonably good at detecting keyword stuffing.

Free Tool to Do This in Seconds

Matching keywords manually is tedious. That's why we built our ATS Checker — paste your resume and any job description, and it tells you your match percentage, which required keywords are missing, which skills are underweighted, and where exactly to add each keyword in your resume.

The Three Skills Section Formats That Work

Format 1: Grouped by Category (best for most roles)

SKILLS
Technical: Python, SQL, Tableau, dbt, Snowflake, Airflow
Analytical: A/B testing, Cohort analysis, Forecasting, Regression modeling
Business: Stakeholder management, Cross-functional collaboration, Executive communication

Format 2: Flat List (best for senior or technical roles)

SKILLS
Python • SQL • Tableau • dbt • Snowflake • Airflow • A/B testing • Cohort analysis • Stakeholder management

Format 3: Rated / Proficiency (USE WITH CAUTION)

Warning: Don't use the rated format unless you're fully willing to defend the ratings in interviews. "Expert in SQL" gets you a whiteboard test.

Industry-Specific Keyword Patterns (2026)

• AI / ML engineering: LLMs, prompt engineering, RAG, vector databases, fine-tuning, PyTorch, Transformers, LangChain, evaluation frameworks
• Fintech: KYC/AML compliance, PCI DSS, fraud detection, SOC 2, real-time payments, risk modeling
• Health tech: HIPAA, HL7/FHIR, clinical workflows, EHR integration (Epic, Cerner), medical coding (ICD-10, CPT)
• Climate / clean energy: ESG reporting, carbon accounting (GHG Protocol), LCA, renewable energy systems, grid optimization
• Creator economy / content: Short-form video strategy, community management, creator partnerships, influencer analytics, platform-specific growth

Skills Mistakes That Get You Rejected

1. Listing skills you can't back up. A single interview question exposes the lie. Never list a skill you can't discuss for three minutes.
2. Using the wrong level of seniority language. A senior resume that says "basic knowledge of Python" looks weaker than one that says "Python for data analysis."
3. Spelling errors in skill names. "Javscript." "Illustrater." "Kubernetees." It's 2026 and spellcheck exists.
4. Adding skills that contradict your resume. Skills should reinforce the story, not contradict it.
5. Forgetting to update for the target role. A static skills section = lower match rate.

Quick Checklist Before You Submit

• ✅ Skills section has 8–12 skills, not 30
• ✅ Hard skills and soft skills at roughly 70/30
• ✅ Exact keywords from the job description are present
• ✅ No "Microsoft Office" or "communication" without qualification
• ✅ No skills you can't honestly defend in an interview
• ✅ Spelling and capitalization match industry conventions
• ✅ Your skills reinforce, not contradict, your experience bullets
• ✅ Customized to this specific role — not the same list for every application

The TL;DR

The skills section isn't a dumping ground. It's a precision tool for signaling to both ATS parsers and human readers that you match the role. Pull exact keywords from the job description, list 8–12 skills you can defend, skip the buzzwords, and update the section for every application. Do that, and your callback rate will jump — often dramatically.