Resume Skills Section: What to Include and How to Format It

The skills section is one of the most misunderstood parts of a resume. Some candidates skip it entirely. Others list 40 skills in an undifferentiated wall of text. Neither is helpful to a recruiter or an ATS.

A well-built skills section does three things: it signals your technical capabilities at a glance, it satisfies keyword matching for ATS, and it helps the recruiter quickly assess fit without re-reading your entire work history.

Here's how to build one that works.

Hard Skills vs Soft Skills

The most important thing to understand about your skills section: soft skills don't belong there.

Hard skills are concrete, teachable, and verifiable. Python. SQL. Salesforce. Excel. After Effects. Managing a P&L. Conducting user interviews. These belong in your skills section because they're searchable (ATS scans for them) and because a recruiter can verify them.

Soft skills are personality traits or interpersonal qualities. Communication, teamwork, leadership, adaptability. These do NOT belong in your skills section because they're not searchable, they're not verifiable from a list, and every candidate on the pile has them listed. They become meaningful when demonstrated through your bullet points — not asserted in a list.

Wrong: Skills: Python, SQL, Salesforce, Communication, Teamwork, Leadership, Problem-solving, Excel Right: Technical: Python, SQL, Salesforce, Excel, Tableau | Languages: English (native), German (B2)

What Goes in a Skills Section

Think in categories based on what's most relevant to your field:

For software engineers:

• Languages: Python, JavaScript (TypeScript), Go, Rust
• Frameworks: React, Next.js, FastAPI, Django
• Infrastructure: AWS, Kubernetes, Docker, Terraform
• Databases: PostgreSQL, MongoDB, Redis
• Tools: GitHub Actions, Datadog, Jira

For marketers:

• Channels: SEO, Paid Social (Meta, Google), Email Marketing, Content
• Tools: HubSpot, Salesforce, GA4, Ahrefs, Marketo
• Technical: SQL (basic), Looker, Tableau

For finance professionals:

• Analysis: Financial modeling, DCF, LBO, M&A analysis
• Software: Excel (advanced), SQL, Bloomberg Terminal, Tableau
• Certifications: CFA Level II, CPA

For sales professionals:

• Process: Enterprise sales, MEDDIC, Challenger Sale
• CRM: Salesforce, HubSpot, Outreach
• Technical: SQL (basic), Tableau, G Suite

ATS and Your Skills Section

When a recruiter searches their ATS database for "Senior PM with Figma experience," the system scans the entire resume including the skills section. If you have Figma experience but it only appears in one bullet under a 2015 role, it might be weighted lower than if it's also in your skills section.

The skills section acts as a summary index — it increases the keyword frequency for important terms in a legitimate way.

One exception: don't put a tool in your skills section if it doesn't appear anywhere in your work history. Floating skills with no supporting context look padded and can create awkward moments if a recruiter asks you to elaborate.

How to Format Your Skills Section

The readable format (categories):

Skills
Technical:    Python, SQL, Tableau, dbt, BigQuery
Tools:        Looker, Snowflake, Fivetran, dbt Cloud, Airflow
Languages:    English (native), French (conversational)
Certifications: AWS Cloud Practitioner, Google Analytics 4

The ATS-safe format (plain text, no special characters):

Skills: Python | SQL | Tableau | dbt | BigQuery | Looker | Snowflake | AWS | Data Modeling | ETL

What to avoid:

• Skill bars or percentage ratings ("SQL — 80%") — these add no information and make you look like you don't understand the field
• Lengthy descriptions next to each skill
• Progress bars (visual graphics) — invisible to ATS
• Listing more than 20-25 skills — at that point you're padding, not signaling

Skills by Experience Level

Entry-level: Your skills section can be proportionally larger because your work history is shorter. List every technical skill and tool you have, including ones from coursework. Add a "Currently learning:" subsection to signal growth orientation.

Mid-career (5-10 years): Keep it concise. Your work history carries the weight. List your 10-15 most important skills, grouped by category.

Senior / Executive: The skills section shrinks. Senior roles prioritize leadership evidence over tool proficiency. You might just list: "Proficiencies: [5-8 key items] | Languages: [X]" and keep the focus on your work history.

The Certification Sub-Section

If you have relevant professional certifications, either include them in the skills section or give them their own section:

Certifications
PMP (Project Management Professional) — PMI, 2024
AWS Solutions Architect — Associate, 2023
Google Analytics 4 Certification, 2025

Include: certification name, issuing body, year obtained (or expiration if relevant). Don't include courses that didn't produce a credential — "Completed LinkedIn Learning's Figma course" is not a certification.

The Languages Sub-Section

If you speak more than one language professionally, list it:

Languages
English — Native
Spanish — Professional working proficiency (C1)
German — Conversational (B1)

CEFR levels (A1 through C2) or familiar equivalents (Native, Fluent, Professional, Conversational, Basic) are both acceptable. Don't overstate — "Conversational" German that you haven't used in 5 years will come up in an interview.

When to Skip the Skills Section

Skip it only if:

• You're applying for a senior leadership role where skills lists look thin compared to your executive profile
• Your field genuinely doesn't use tool-based skills (certain creative, academic, or advisory roles)

For the vast majority of roles in tech, finance, marketing, operations, healthcare, and sales — a well-built skills section is a meaningful positive signal.

The transferable skills that don't fit cleanly into a skills list — project management, cross-functional leadership, user research — are better demonstrated in bullet points than listed abstractly. Let your experience prove what your skills section labels.