CVBase Build your resume
Resume Writing

Resume Skills Section: What to Include (and What to Skip)

Master your resume skills section with expert guidance on hard vs. soft skills, ATS optimization, proficiency levels, and industry-specific skills that get interviews.

By the CVBase teamMarch 17, 202415 min readIntermediate

Introduction

Your resume's skills section can be the difference between passing the ATS scan and landing in the rejection pile. But here's the paradox: most professionals either overcrowd it with every skill they've ever touched, or undersell themselves by listing only the obvious.

"Proficient in Microsoft Office."

This tells recruiters nothing in 2024. Everyone claims Office proficiency. Meanwhile, the candidate who writes "Advanced Excel: Pivot tables, VLOOKUP, macros, Power Query for datasets exceeding 100K rows" instantly stands out.

Your skills section is prime real estate on your resume. It's where ATS systems scan for keywords. It's where recruiters verify you have the technical foundation for the role. It's where hiring managers quickly assess if you're worth a phone screen.

This guide will show you exactly which skills to include, how to organize them, what proficiency levels actually mean, and how to optimize for both robots and humans.

The Two Types of Skills: Hard vs. Soft

Hard Skills: Teachable, Measurable, Specific

Hard skills are technical abilities you can learn through training, education, or experience. They're measurable and verifiable:

Soft Skills: Interpersonal, Harder to Measure

Soft skills relate to how you work and interact with others:

The Critical Distinction for Your Resume

Here's the truth most resume guides won't tell you: soft skills don't belong in your skills section.

Why? Because everyone lists them, and they mean nothing without proof.

Compare these two approaches:

Weak (Skills Section):

Strong (Demonstrated in Experience Section): "Communicated complex technical concepts to non-technical stakeholders, resulting in 100% project approval rate across 15 presentations"

Soft skills should be proven through your accomplishments, not listed as claims. Your skills section should focus on hard, verifiable skills that pass ATS scans.

Organizing Your Technical Skills

The Best Structure Depends on Your Industry

Format 1: Categorized by Type (Best for Technical Roles)

Technical Skills:

This format works well for:

Format 2: Prioritized by Relevance (Best for Career Changers)

Skills:

This format highlights transferable skills first, showing you have the core competencies even if you're changing industries.

Format 3: Combined Skills (Best for Mid-Level Professionals)

Skills: Python • SQL • Tableau • Salesforce • Project Management • Data Visualization • Excel (Advanced) • Google Analytics • A/B Testing • CRM Management

This compact format works when you have diverse skills and limited space. Use bullets or separators for easy scanning.

Format 4: Proficiency Levels (Best for Senior Roles)

Technical Proficiency:

This format is risky unless you can truly defend these levels. Only use it if the job posting specifically requests proficiency indicators.

Understanding Proficiency Levels

The Problem with Self-Assessment

Most people overestimate beginner work and underestimate expert-level knowledge. Here's what these terms actually mean:

Beginner/Fundamental

When to claim it: Almost never on your resume. If you're at beginner level, it's not adding value.

Exception: Career changers showing they've started learning a required skill: "Currently developing Python skills through data analysis coursework"

Intermediate/Proficient

When to claim it: This is the default level for skills you've used meaningfully in work.

Example: "Intermediate SQL: Write complex joins, subqueries, and window functions; optimize query performance for datasets up to 10M rows"

Advanced/Expert

When to claim it: Be conservative. If you claim expert-level, be prepared for deep technical interviews.

Example: "Expert Python: Design scalable data pipelines, optimize performance for big data applications, contribute to open-source libraries"

The Safe Approach

Unless the job posting specifically requests proficiency levels, just list your skills without labels. Your experience section should demonstrate your actual level:

Skills Section:

Experience Section: "Built automated data pipeline using Python (pandas, SQLAlchemy) processing 5M+ records daily; optimized SQL queries reducing report generation time from 45 minutes to 3 minutes"

This proves advanced proficiency without claiming it.

Certifications: How to List Them

Certifications Belong Here If They're Active and Relevant

When to Include in Skills Section:

Format Option 1 (Integrated): Technical Skills:

Format Option 2 (Separate Section): Certifications:

Format Option 3 (In Main Skills List): Skills: AWS (Solutions Architect Certified) • PMP • Python • SQL • Tableau • Agile/Scrum (CSM)

Critical Rules for Certifications:

✅ Include expiration or achievement date: Shows currency ✅ Use official names: "PMP" not "project management certification" ✅ Prioritize industry-recognized certs: AWS, PMP, CPA, Six Sigma ✅ List issuing organization for lesser-known certs: "HubSpot Inbound Marketing Certification"

❌ Don't list expired certifications (unless recently expired and you're recertifying) ❌ Don't include every Udemy/Coursera certificate (save for LinkedIn) ❌ Don't list certifications unrelated to target role (keep focused)

Which Certifications Actually Matter?

High-Value Certifications by Field:

Technology:

Project Management:

Finance/Accounting:

Marketing:

HR:

Medical/Healthcare:

Languages and Fluency Levels

The Standard Framework: ILR Scale

The Interagency Language Roundtable (ILR) scale is recognized globally:

Level 0 - No Proficiency

Level 1 - Elementary

Level 2 - Limited Working

Level 3 - Professional Working

Level 4 - Full Professional

Level 5 - Native

Best Practices for Language Skills:

✅ Be honest: You may be tested in an interview ✅ Specify dialect if relevant: "Mandarin (Simplified)" vs. "Cantonese" ✅ Highlight business context: "Japanese (Business Fluent): Negotiate contracts, manage client relationships" ✅ List in order of proficiency: Native language first, then strongest second language

❌ Don't claim fluency if you're conversational: It will be exposed ❌ Don't list ancient/dead languages unless directly relevant: Nobody cares about your high school Latin ❌ Don't forget sign language: ASL is a valuable business skill

Format Examples:

Option 1 (Simple): Languages: English (Native), Spanish (Fluent), French (Conversational)

Option 2 (Detailed): Languages:

Tools and Software: The Modern Essential

Industry-Specific Tool Skills

Software Engineering

Core Tools:

Don't bother listing: Operating systems (Windows, Mac, Linux) unless the job specifically requires Linux administration

Data Analytics

Core Tools:

Don't bother listing: Excel unless you specify advanced features, basic spreadsheet skills

Marketing

Core Tools:

Don't bother listing: Social media platforms (everyone uses Facebook), basic email

Sales

Core Tools:

Don't bother listing: Phone, email (obviously), PowerPoint (unless creating complex decks is a key skill)

Project Management

Core Tools:

Don't bother listing: Basic office tools unless PM role requires advanced Excel modeling

Design

Core Tools:

Don't bother listing: Canva (unless applying to small businesses), PowerPoint design

Finance

Core Tools:

Don't bother listing: Calculator, basic Excel, basic accounting software

What to Skip: The "Everyone Has This" List

Never List These (Unless It's 1995):

❌ Microsoft Office - Everyone claims this; it's meaningless

❌ Email - Seriously?

❌ Internet research - This is not a skill in 2024

❌ "Computer skills" - Be specific or don't list it

❌ "Fast learner" - This is a soft skill claim, not a hard skill

❌ "Detail-oriented" - Show it, don't list it

❌ "Team player" - Meaningless without context

❌ Social media - Unless you manage it professionally

❌ "Microsoft Word" - Everyone can type a document

❌ "PowerPoint" - Making slides isn't special

❌ "Customer service" - This is demonstrated through experience, not listed as a skill

❌ "Communication skills" - Soft skill that must be proven

❌ "Typing" - Unless applying for transcription role requiring 80+ WPM

❌ "Windows" or "Mac OS" - Basic computer literacy assumed

Industry-Specific Skills by Field

Software Engineering

Must-Have:

Nice-to-Have:

Data Science

Must-Have:

Nice-to-Have:

Digital Marketing

Must-Have:

Nice-to-Have:

Financial Analysis

Must-Have:

Nice-to-Have:

Product Management

Must-Have:

Nice-to-Have:

UX/UI Design

Must-Have:

Nice-to-Have:

Human Resources

Must-Have:

Nice-to-Have:

ATS Optimization: Making Robots Love Your Skills

How ATS Systems Scan Skills Sections

Applicant Tracking Systems parse your resume looking for exact and close keyword matches to the job posting. Here's how to optimize:

Strategy 1: Mirror Job Posting Language

If the job says "Python," write "Python" (not "Python programming" or "Python 3.11").

If the job says "Salesforce CRM," write "Salesforce CRM" (not just "Salesforce").

Job Posting Says: "Required: Proficiency in SQL, Tableau, Python; experience with AWS"

Your Skills Section Should Include: SQL • Tableau • Python • AWS

(Exact matches first, then elaboration if space permits)

Strategy 2: Use Both Acronyms and Full Names

ATS systems sometimes search for "Search Engine Optimization" and sometimes for "SEO."

Safe approach:

Strategy 3: Don't Get Creative with Formatting

❌ ATS Struggles With:

✅ ATS Reads Well:

Strategy 4: Include Variations

Some systems search for variations:

Smart format: "JavaScript (JS), Artificial Intelligence (AI), Customer Relationship Management (CRM)"

Strategy 5: Don't Keyword Stuff

ATS systems are smarter now. Listing 50+ skills or hiding white text triggers spam filters.

❌ Keyword Stuffing: Python Java JavaScript C++ Ruby Go Rust PHP Swift Kotlin Scala Perl R MATLAB Julia... (listing every language)

✅ Focused Approach: Python • JavaScript • SQL • Go (only languages you actually use professionally)

Strategy 6: Keep Skills Section Near Top

ATS gives more weight to content appearing earlier in the document.

Optimal order:

  1. Contact information
  2. Professional summary (optional)
  3. Skills section
  4. Experience
  5. Education

Alternative order (for senior roles):

  1. Contact information
  2. Executive summary
  3. Experience
  4. Technical/Core Competencies (skills)
  5. Education

Testing Your Skills Section

The Three-Test Process

Test 1: The Relevance Test

For each skill, ask: "Would I be comfortable being tested on this in an interview?"

If the answer is no, remove it or clarify your actual level.

Test 2: The Value Test

For each skill, ask: "Does this differentiate me from 90% of other candidates?"

Test 3: The ATS Test

Copy the job description. Highlight required skills. Compare to your skills section.

Required skills you have but didn't list: Add them Required skills you don't have: Don't lie, but consider if you have something close Skills you listed that aren't mentioned: Keep only if they're industry-standard or exceptionally relevant

Common Mistakes and How to Fix Them

Mistake 1: The Everything List

Problem: 50+ skills listed, including irrelevant and basic items

Example: "Skills: Python, Java, C++, JavaScript, HTML, CSS, Ruby, PHP, Go, Rust, Scala, Perl, R, MATLAB, Excel, Word, PowerPoint, Windows, Mac, Linux, Communication, Leadership, Problem Solving, Team Player, Fast Learner..."

Fix: Focus on 8-15 highly relevant skills

"Technical Skills: Python, JavaScript, SQL, AWS, Docker, React, PostgreSQL, Git"

Mistake 2: The Vague List

Problem: Skills are too generic to mean anything

Example: "Skills: Microsoft Office, social media, customer service, computers"

Fix: Be specific about what you can actually do

"Technical Proficiency: Advanced Excel (financial modeling, VBA macros, Power Query), Salesforce CRM administration, SQL database querying"

Mistake 3: Soft Skills Takeover

Problem: Skills section dominated by unprovable soft skills

Example: "Skills: Leadership, Communication, Problem Solving, Teamwork, Adaptability, Critical Thinking, Time Management"

Fix: Replace with hard skills; demonstrate soft skills in experience bullets

"Skills: Project Management (PMP), Agile/Scrum, JIRA, Stakeholder Management, Budget Management ($5M+)"

Mistake 4: Outdated Skills

Problem: Listing technologies/tools no longer in use

Example: "Skills: Flash, Dreamweaver, Internet Explorer optimization, Perl, COBOL"

Fix: Remove obsolete skills unless applying to legacy system roles

Mistake 5: Exaggerated Proficiency

Problem: Claiming expert level on skills you've barely used

Example: "Expert: Python, R, Java, C++, Machine Learning, Deep Learning, AWS, Azure, GCP" (but you've only taken online courses)

Fix: Be honest; your interview will expose exaggerations

"Technical Skills: Python (professional experience), SQL (advanced), Machine Learning (academic projects and coursework)"

Action Plan: Building Your Perfect Skills Section

Step 1: Inventory Your Skills (30 minutes)

Create a master list:

Step 2: Analyze Target Job Postings (20 minutes)

Find 3-5 job postings for roles you want. Highlight:

Step 3: Match and Prioritize (15 minutes)

Compare your inventory to job requirements:

✅ Skills you have that match requirements → Include these first ⚠️ Skills you have that are adjacent to requirements → Include if space permits ❌ Skills you have that aren't relevant → Remove for this version

Step 4: Organize by Category (10 minutes)

Group related skills:

Step 5: Format for ATS and Readability (10 minutes)

Choose format based on your level and industry:

Step 6: Test and Refine (15 minutes)

Run through the three tests:

  1. Relevance: Can you speak confidently about each skill?
  2. Value: Does each skill differentiate you?
  3. ATS: Does it match job posting keywords?

Conclusion

Your skills section is not a dumping ground for every tool you've ever touched. It's a strategic showcase of your technical qualifications, optimized for ATS and designed to prove you can do the job.

The difference between:

"Skills: Microsoft Office, communication, team player, fast learner"

and

"Technical Skills: Python (pandas, scikit-learn), SQL (PostgreSQL, MySQL), Tableau, AWS (S3, EC2, Lambda), Git, Agile/Scrum, Google Analytics"

...is the difference between getting filtered out by the ATS and landing an interview.

Don't list skills you can't defend. Don't skip skills you take for granted. Match the job posting language. Be specific. Be honest.

Your skills section should make recruiters think: "This person can do the job." Nothing more, nothing less.

More on resume writing