Should I put soft skills in the skills section of my resume?

Generally, no. Soft skills like 'communication' or 'leadership' carry no weight in a standalone list because they're unverifiable. Instead, demonstrate them through specific accomplishments in your work experience bullets — for example, 'Led cross-functional team of 8 to deliver product launch 3 weeks ahead of schedule' shows leadership far more convincingly.

How do I know which skills to include for a specific job?

Read the job description carefully and highlight every skill, tool, platform, or methodology mentioned — especially anything listed under 'Required' or repeated more than once. Cross-reference that list against your actual experience and include every match. Tailor this for each application rather than using one static list.

Where should the skills section go on a resume?

For technical and specialized roles, place the skills section near the top — directly after your summary or headline — so recruiters and ATS systems encounter your qualifications immediately. For roles where experience and accomplishments outweigh technical tools, placing skills after your work history is acceptable, but never bury it on page two.

All guides

What to Put in the Skills Section of a Resume

5 min read · Updated September 11, 2026

The skills section of a resume is one of the first things an applicant tracking system scans and one of the first things a recruiter skims — so what you put there either opens doors or quietly kills your application. Most candidates either cram in every tool they've ever touched or list vague soft skills that say nothing. This guide tells you exactly what belongs, what doesn't, and how to format it so both software and humans take notice.

Hard Skills vs. Soft Skills: What Actually Belongs

Your skills section should be dominated by hard skills — specific, teachable, and verifiable abilities. Think programming languages, software platforms, certifications, methodologies, and technical tools. These are the items ATS software is hunting for when it scans your resume against a job description.

Soft skills like 'strong communicator' or 'team player' belong in your bullet points under work experience, where you can back them up with evidence. Listing 'leadership' in a standalone skills section is meaningless — a hiring manager has no way to evaluate it. Reserve that real estate for concrete competencies.

Hard skill examples: Python, Salesforce CRM, SQL, Adobe Illustrator, GAAP accounting, AutoCAD, Google Analytics
Methodology examples: Agile/Scrum, Six Sigma, ITIL, PMP, Lean manufacturing
Certifications worth listing here: AWS Certified Solutions Architect, CPA, PMP, SHRM-CP, CompTIA Security+
What to cut: 'Microsoft Office' (too generic unless the role specifies Excel modeling), 'good communicator', 'detail-oriented', 'hardworking'

Mirror the Job Description — Strategically

Every job posting is a cheat sheet. Recruiters write job descriptions using the exact keywords their ATS is programmed to find. Pull the posting apart and identify the skills mentioned more than once or listed under 'Required.' Those are your priority terms.

Don't copy-paste blindly — only list skills you actually have. But if you call the tool 'HubSpot' and the job description calls it 'HubSpot Marketing Hub,' use their phrasing. Exact string matches score higher in most ATS platforms. Do this for every application; a single static skills section will underperform.

How Many Skills to List and How to Organize Them

Aim for 10–18 skills. Fewer than 10 looks thin; more than 20 starts to look like you padded it. Group related skills into short categories so the section is scannable in under five seconds.

A clean format uses two or three columns or a simple category-label approach. Avoid rating bars or proficiency stars — they're visual noise that conveys nothing standardized (your '4 out of 5' in Python means nothing to a recruiter).

Example grouping for a data analyst: Languages & Tools | Python, R, SQL, Tableau, Power BI
Example grouping: Cloud Platforms | AWS (EC2, S3, Lambda), Google Cloud, Azure
Example grouping for a marketer: Paid Media | Google Ads, Meta Ads Manager, LinkedIn Campaign Manager
Example grouping: Frameworks & Methods | Agile, A/B Testing, Conversion Rate Optimization

Skills to Always Include for Your Field

Certain skills are table stakes in specific industries — if you have them and don't list them, you'll be filtered out before a human ever reads your name. Here are field-specific must-haves you should verify are present.

Software engineering: Version control (Git), CI/CD pipelines, your primary languages, testing frameworks
Finance/accounting: Excel (specify: financial modeling, pivot tables, VLOOKUP), ERP systems (SAP, Oracle), GAAP or IFRS
Marketing: SEO/SEM, CRM platforms, email marketing tools (Klaviyo, Mailchimp), analytics (GA4)
Project management: PMP or equivalent cert, MS Project or Asana/Jira, budget management, stakeholder communication
Healthcare administration: EHR systems (Epic, Cerner), HIPAA compliance, medical billing/coding (CPT, ICD-10)
Human resources: HRIS platforms (Workday, ADP), recruiting tools (Greenhouse, Lever), employment law basics

Common Mistakes That Undermine Your Skills Section

Listing outdated technology signals that you haven't kept up. If you're applying for a web development role and you list 'Flash' or 'Dreamweaver,' you've just dated yourself. Audit your list annually and replace legacy tools with current equivalents.

Another frequent error is burying the skills section at the bottom of the resume. For technical roles especially, move it above your work experience or directly below your summary. Recruiters doing a quick scan should hit your key qualifications within the first third of the page.

Don't list skills at a beginner level unless the job explicitly asks for entry-level exposure
Don't include skills you can't speak to confidently in an interview — you will be asked
Don't use acronyms without context if the full term is more searchable (write 'Search Engine Optimization (SEO)' the first time)

When to Add a Proficiency Level

Proficiency labels are useful in one specific scenario: when there's a meaningful gap between your skills. If you're fluent in Python but only familiar with R, say so — 'Python (advanced), R (working knowledge).' This prevents you from being handed a project that requires deep R expertise on day one.

For languages spoken, always include proficiency: 'Spanish (professional working proficiency)' or 'Mandarin (native).' Use the ILR or CEFR scale if you know it — it gives employers a standardized reference point.

Build Your Resume

Resumade's resume builder prompts you to add role-specific skills based on your target job title and automatically formats them in a clean, ATS-friendly layout.