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.
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:
- Programming languages (Python, Java, JavaScript)
- Software tools (Salesforce, Adobe Creative Suite, AutoCAD)
- Technical competencies (data analysis, financial modeling, SEO)
- Certifications (PMP, CPA, AWS Solutions Architect)
- Languages (Spanish fluency, Mandarin conversational)
Soft Skills: Interpersonal, Harder to Measure
Soft skills relate to how you work and interact with others:
- Communication
- Leadership
- Problem-solving
- Teamwork
- Adaptability
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 communication skills
- Excellent leadership
- Great problem-solver
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:
- Programming Languages: Python, JavaScript, SQL, R
- Frameworks/Libraries: React, Node.js, Django, TensorFlow
- Tools & Platforms: AWS, Docker, Git, Jenkins, Kubernetes
- Databases: PostgreSQL, MongoDB, Redis
- Methodologies: Agile/Scrum, Test-Driven Development, CI/CD
This format works well for:
- Software engineers
- Data scientists
- DevOps engineers
- Technical program managers
Format 2: Prioritized by Relevance (Best for Career Changers)
Skills:
- Data Analysis: SQL, Python (pandas, NumPy), Tableau, Excel (pivot tables, Power Query)
- Digital Marketing: Google Analytics, SEO/SEM, HubSpot, A/B testing
- Project Management: Agile/Scrum, JIRA, Asana, stakeholder management
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:
- Expert: Python, SQL, AWS, Tableau
- Advanced: JavaScript, React, Docker
- Intermediate: Kubernetes, Go
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
- Used the tool/skill in a controlled environment (courses, tutorials)
- Can perform basic tasks with guidance
- Limited to simple, common use cases
- Would need significant ramp-up time in a production environment
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
- Used regularly in professional setting for 1+ years
- Can work independently on standard tasks
- Understand best practices and common patterns
- Can troubleshoot typical issues without constant support
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
- Multiple years of intensive, production-level experience
- Can handle complex, unusual scenarios
- Teach or mentor others in this skill
- Recognized by peers as a go-to resource
- Comfortable with architecture decisions, not just implementation
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:
- Python, SQL, AWS, Tableau
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:
- Cloud Architecture (AWS Solutions Architect - Associate)
- Project Management (PMP, Scrum Master)
- Data Analysis (Google Analytics Certified)
Format Option 2 (Separate Section): Certifications:
- AWS Certified Solutions Architect - Associate (2023)
- Project Management Professional (PMP) - PMI (2022)
- Certified Scrum Master (CSM) - Scrum Alliance (2021)
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:
- AWS/Azure/GCP Cloud certifications
- CISSP (Cybersecurity)
- Cisco CCNA/CCNP (Networking)
- Google Professional Cloud Architect
Project Management:
- PMP (Project Management Professional)
- Certified Scrum Master (CSM)
- PRINCE2
- Lean Six Sigma (Green Belt, Black Belt)
Finance/Accounting:
- CPA (Certified Public Accountant)
- CFA (Chartered Financial Analyst)
- CFP (Certified Financial Planner)
Marketing:
- Google Analytics Individual Qualification
- HubSpot Inbound Marketing
- Facebook Blueprint
- Hootsuite Social Marketing
HR:
- SHRM-CP/SHRM-SCP
- PHR/SPHR
- Certified Compensation Professional
Medical/Healthcare:
- Board certifications
- ACLS (Advanced Cardiac Life Support)
- Specialty certifications
Languages and Fluency Levels
The Standard Framework: ILR Scale
The Interagency Language Roundtable (ILR) scale is recognized globally:
Level 0 - No Proficiency
- Don't list this
Level 1 - Elementary
- Can handle basic conversations
- Limited vocabulary
- Resume language: "Basic [Language]" or "Conversational [Language]"
- Example: "Spanish (Conversational): Can conduct simple business discussions"
Level 2 - Limited Working
- Can participate in routine social/work conversations
- Can read standard texts
- Resume language: "Professional Working Proficiency"
- Example: "French (Professional Working Proficiency): Conduct client meetings, write business emails"
Level 3 - Professional Working
- Can discuss complex topics
- Can function in professional environments
- Resume language: "Full Professional Proficiency" or "Fluent"
- Example: "Mandarin (Fluent): Present to senior executives, negotiate contracts"
Level 4 - Full Professional
- Near-native fluency
- Can handle any professional situation
- Resume language: "Native/Bilingual Proficiency"
- Example: "English/Spanish (Native Bilingual)"
Level 5 - Native
- Native speaker
- Resume language: "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:
- English (Native)
- Spanish (Full Professional Proficiency): Business negotiations, client presentations
- Mandarin (Professional Working Proficiency): Customer meetings, email correspondence
Tools and Software: The Modern Essential
Industry-Specific Tool Skills
Software Engineering
Core Tools:
- Version Control: Git, GitHub, GitLab
- IDEs: VS Code, IntelliJ, PyCharm
- Cloud Platforms: AWS, Azure, GCP
- CI/CD: Jenkins, CircleCI, GitHub Actions
- Containers: Docker, Kubernetes
- Monitoring: Datadog, New Relic, Grafana
Don't bother listing: Operating systems (Windows, Mac, Linux) unless the job specifically requires Linux administration
Data Analytics
Core Tools:
- Visualization: Tableau, Power BI, Looker
- Analysis: SQL, Python (pandas, NumPy), R
- Database: PostgreSQL, MySQL, BigQuery, Snowflake
- Spreadsheets: Excel (Advanced: pivot tables, Power Query, macros)
- Cloud: AWS (S3, Redshift), Google Cloud Platform
Don't bother listing: Excel unless you specify advanced features, basic spreadsheet skills
Marketing
Core Tools:
- Analytics: Google Analytics, Adobe Analytics, Mixpanel
- SEO: SEMrush, Ahrefs, Moz, Google Search Console
- Email: HubSpot, Mailchimp, Marketo
- Social: Hootsuite, Buffer, Sprout Social
- Ads: Google Ads, Facebook Ads Manager, LinkedIn Campaign Manager
- CMS: WordPress, Drupal, Contentful
- Design: Canva, Adobe Creative Suite (if you actually use it)
Don't bother listing: Social media platforms (everyone uses Facebook), basic email
Sales
Core Tools:
- CRM: Salesforce, HubSpot CRM, Microsoft Dynamics
- Sales Engagement: Outreach, SalesLoft, Apollo
- Communication: Zoom, Gong, Chorus (if you use them strategically)
- Data: LinkedIn Sales Navigator, ZoomInfo
- Proposals: PandaDoc, DocuSign
Don't bother listing: Phone, email (obviously), PowerPoint (unless creating complex decks is a key skill)
Project Management
Core Tools:
- PM Software: JIRA, Asana, Monday.com, Microsoft Project
- Collaboration: Confluence, Notion, SharePoint
- Agile: Rally, VersionOne, Jira Agile
- Documentation: Lucidchart, Miro, Draw.io
- Communication: Slack, Microsoft Teams (only if you're an admin/power user)
Don't bother listing: Basic office tools unless PM role requires advanced Excel modeling
Design
Core Tools:
- Adobe Creative Suite: Photoshop, Illustrator, InDesign, After Effects (list specifically)
- UI/UX: Figma, Sketch, Adobe XD, InVision
- Prototyping: Principle, ProtoPie, Framer
- 3D: Blender, Cinema 4D, Maya
- Web: HTML, CSS, JavaScript (if you code your designs)
Don't bother listing: Canva (unless applying to small businesses), PowerPoint design
Finance
Core Tools:
- Analysis: Excel (Advanced: VBA, Power Query, complex modeling), Bloomberg Terminal
- ERP: SAP, Oracle, NetSuite
- Databases: SQL, Access (if truly advanced)
- Visualization: Tableau, Power BI
- Specific: QuickBooks, Xero (for accounting roles)
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
- Exception: "Advanced Excel: Financial modeling, VBA macros, Power Query, pivot tables for 100K+ row datasets"
❌ 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
- Exception: "Social Media Management: Grew Instagram following from 5K to 50K, 200% engagement increase"
❌ "Microsoft Word" - Everyone can type a document
- Exception: "Advanced Word: Mail merge for 10K+ recipients, template design, style management for 100+ page reports"
❌ "PowerPoint" - Making slides isn't special
- Exception: "Executive Presentation Design: Create investor pitch decks, board presentations, complex data visualization in PowerPoint"
❌ "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:
- Programming languages (2-4 relevant ones)
- Version control (Git)
- Cloud platform (AWS/Azure/GCP)
- Database (SQL + NoSQL)
- Framework relevant to your stack
Nice-to-Have:
- Testing frameworks
- CI/CD tools
- Container orchestration
- Monitoring/logging tools
- Security certifications
Data Science
Must-Have:
- Python or R
- SQL
- Machine learning libraries (scikit-learn, TensorFlow, PyTorch)
- Data visualization (Tableau, matplotlib, seaborn)
- Statistics knowledge
Nice-to-Have:
- Big data tools (Spark, Hadoop)
- Cloud platforms (AWS SageMaker, GCP Vertex AI)
- MLOps tools
- Deep learning specialization
- Domain expertise (NLP, computer vision, etc.)
Digital Marketing
Must-Have:
- Google Analytics
- SEO fundamentals
- Content management system (WordPress, etc.)
- Email marketing platform
- Social media advertising
Nice-to-Have:
- Marketing automation (HubSpot, Marketo)
- A/B testing platforms
- SQL for data analysis
- Basic HTML/CSS
- Graphic design tools
Financial Analysis
Must-Have:
- Advanced Excel (financial modeling)
- Financial statement analysis
- Valuation techniques
- SQL (increasingly important)
- Bloomberg Terminal (for many roles)
Nice-to-Have:
- Tableau/Power BI
- Programming (Python, R for quantitative roles)
- Specific industry knowledge
- CFA Level I, II, or III
- Treasury/risk management tools
Product Management
Must-Have:
- Product roadmapping tools (Aha!, ProductPlan)
- Analytics (Google Analytics, Mixpanel, Amplitude)
- Project management (JIRA, Asana)
- SQL (for data-driven decisions)
- Wireframing/prototyping (Figma, Sketch)
Nice-to-Have:
- Basic coding knowledge
- A/B testing platforms
- User research tools
- Technical writing
- Specific domain expertise
UX/UI Design
Must-Have:
- Figma or Sketch
- Prototyping tools (InVision, Principle)
- User research methodologies
- Design systems knowledge
- Basic front-end understanding (HTML/CSS)
Nice-to-Have:
- Adobe Creative Suite
- Motion design (After Effects, Principle)
- Accessibility standards (WCAG)
- Actual coding ability (React, etc.)
- Specific platform expertise (iOS, Android)
Human Resources
Must-Have:
- HRIS (Workday, ADP, BambooHR)
- Applicant Tracking Systems (Greenhouse, Lever)
- Excel (for HR analytics)
- Compliance knowledge (FMLA, EEO, etc.)
- HR certification (PHR, SHRM-CP)
Nice-to-Have:
- SQL for people analytics
- Survey tools (Qualtrics, Culture Amp)
- Learning Management Systems
- Compensation analysis tools
- Diversity & inclusion training
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:
- SEO (Search Engine Optimization)
- PMP (Project Management Professional)
- AWS (Amazon Web Services)
Strategy 3: Don't Get Creative with Formatting
❌ ATS Struggles With:
- Skills in text boxes
- Skills in headers/footers
- Skills in tables (sometimes)
- Skills in graphics
- Skills in columns (sometimes)
✅ ATS Reads Well:
- Simple bullet lists
- Skills separated by bullets (•) or pipes (|)
- Clear section headers ("Skills," "Technical Skills," "Core Competencies")
- Standard fonts
Strategy 4: Include Variations
Some systems search for variations:
- JavaScript / JS / ECMAScript
- Artificial Intelligence / AI / Machine Learning
- Customer Relationship Management / CRM
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:
- Contact information
- Professional summary (optional)
- Skills section
- Experience
- Education
Alternative order (for senior roles):
- Contact information
- Executive summary
- Experience
- Technical/Core Competencies (skills)
- 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?"
- "Microsoft Office" → No, everyone lists this
- "Advanced Excel: Financial modeling, VBA, Power Query" → Yes, this is specific and valuable
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:
- Technical skills from current job
- Tools/software you use regularly
- Certifications you hold
- Languages you speak
- Skills from previous roles still relevant
- Skills from side projects/freelance
Step 2: Analyze Target Job Postings (20 minutes)
Find 3-5 job postings for roles you want. Highlight:
- Required skills (must-have)
- Preferred skills (nice-to-have)
- Repeated skills across multiple postings (industry standards)
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:
- Programming: Python, JavaScript, SQL
- Cloud: AWS, Azure
- Tools: Git, Docker, JIRA
- Certifications: PMP, AWS Solutions Architect
Step 5: Format for ATS and Readability (10 minutes)
Choose format based on your level and industry:
- Entry-level: Simple list with bullets
- Mid-level: Categorized skills
- Senior: Prioritized by relevance with proficiency indicators (if applicable)
Step 6: Test and Refine (15 minutes)
Run through the three tests:
- Relevance: Can you speak confidently about each skill?
- Value: Does each skill differentiate you?
- 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.