How to List Skills on a Resume (With Real Examples)

The Skills Section Most People Write (And Why It Fails)

Last month a client sent me her resume for a product manager role. Her skills section listed twenty-three items including "team player," "detail-oriented," "Microsoft Office," and "communication." When I asked her which three skills from that list got her promoted twice in four years, she couldn't answer. That's the problem with most skills sections: they're optimized for nothing except filling space.

I've reviewed over 3,000 resumes as a hiring manager and career coach. The skills section is where candidates either demonstrate they understand the role or reveal they're applying to everything with a pulse. A strong skills section does three things: proves technical capability, passes ATS screening, and gives interviewers concrete topics to explore. A weak one does none of those.

Before we fix yours, understand that ATS systems scan for specific keywords from the job posting. But keyword-stuffing without context is worse than leaving skills off entirely. You need the right skills, in the right format, with proof they're real.

Hard Skills vs Soft Skills: What Actually Belongs on Your Resume

Hard skills are measurable, teachable abilities: Python programming, financial modeling, CAD software, Spanish fluency, SEO strategy. Soft skills are interpersonal traits: leadership, communication, problem-solving, adaptability. Your resume needs both, but in very different ways.

Hard skills belong in a dedicated skills section because they're searchable, verifiable, and role-specific. When a recruiter searches the ATS for "Salesforce" or "Google Analytics," you either show up or you don't. Soft skills belong in your experience bullets where you demonstrate them through results, not in a list where they mean nothing.

The ratio matters. For technical roles, your skills section might be 90% hard skills. For leadership positions, you'll still list hard skills but prove soft skills throughout your experience section. I once coached a VP of Operations who listed "strategic thinking" as a skill. We replaced it with "P&L management, supply chain optimization, Lean Six Sigma" and moved the strategic thinking proof into her accomplishment bullets. She got three interviews in two weeks.

What Counts as a Hard Skill

• Software and tools: Specific platforms, not categories ("Tableau" not "data visualization tools")
• Technical abilities: Programming languages, design software, lab techniques, machinery operation
• Certifications and methodologies: PMP, CPA, Agile, HIPAA compliance
• Language proficiency: Specify level (conversational, business fluent, native)
• Industry-specific knowledge: FDA regulations, GAAP accounting, AP style

What Doesn't Belong in Your Skills Section

• Vague soft skills without context: "team player," "hard worker," "detail-oriented"
• Obvious baseline abilities: "Microsoft Word," "email," "internet research"
• Outdated technologies: Unless the job specifically requires legacy systems
• Personal attributes: "creative," "passionate," "dedicated"
• Skills you can't discuss in an interview: If you took one online course three years ago, it's not a resume skill

How Many Skills Should You List (And in What Order)

The right number is between 6 and 12 hard skills. Fewer than six looks thin. More than twelve suggests you're either padding or haven't prioritized what matters for this specific role. I see resumes with 30+ skills listed and my first thought is always: this person applied to fifty different jobs with the same resume.

Order matters as much as selection. List skills in descending priority based on the job posting. If the posting mentions "SQL" three times and "Python" once, SQL goes first. ATS systems weight earlier mentions more heavily, and human readers scan top to bottom. Your most relevant, strongest skills should appear in the first line.

Group related skills logically. Don't scatter "Excel," "Tableau," and "Power BI" across your list with unrelated items in between. Cluster them as "Data Analysis: Excel, Tableau, Power BI, SQL" so recruiters see the full picture of your analytical toolkit at a glance.

Real Examples: Skills Sections That Work

Theory is useless without application. Here are five skills sections for different roles, showing exactly how to structure yours based on your field and experience level.

Software Engineer (Mid-Level)

Before:

• Programming languages: Python, Java, C++, JavaScript, Ruby, Go, Rust
• Frameworks: React, Angular, Vue, Django, Flask, Spring
• Tools: Git, Docker, Jenkins, AWS, Azure, GCP
• Soft skills: Problem-solving, teamwork, communication, agile

After:

• Languages: Python, JavaScript, Java
• Frameworks & Libraries: React, Node.js, Django REST Framework
• Cloud & DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, CI/CD (Jenkins, GitHub Actions)
• Databases: PostgreSQL, MongoDB, Redis
• Tools: Git, Jira, Datadog

The difference: The first version lists everything the candidate has ever touched, including languages they haven't used in three years. The second focuses on current, job-relevant skills with specific AWS services called out. Soft skills moved to experience bullets. The groupings help recruiters see the candidate's full stack at a glance.

Marketing Manager

Before:

• Social media, content creation, SEO, email marketing, analytics, leadership, creative thinking, brand management, customer focus, Microsoft Office, Adobe Creative Suite

After:

• Digital Marketing: SEO/SEM, Google Ads, Meta Ads Manager, email automation (HubSpot, Mailchimp)
• Analytics & Reporting: Google Analytics 4, Tableau, marketing attribution modeling
• Content & Design: Adobe Creative Suite (Photoshop, Illustrator), Canva, WordPress
• Marketing Automation: HubSpot, Marketo, Salesforce Marketing Cloud
• Project Management: Asana, Monday.com, budget management ($500K+ annual spend)

The difference: Specific platforms replace vague categories. "Social media" becomes "Meta Ads Manager." "Analytics" becomes "Google Analytics 4" with a specific tool version. The budget figure adds credibility to project management. Generic soft skills are gone.

Financial Analyst (Entry-Level)

Before:

• Excel, financial modeling, analytical skills, attention to detail, quick learner, PowerPoint, communication, teamwork, problem-solving

After:

• Financial Analysis: Financial modeling, variance analysis, forecasting, budgeting
• Technical: Excel (advanced: pivot tables, VLOOKUP, macros), Bloomberg Terminal, Capital IQ
• Accounting & Compliance: GAAP principles, financial statement analysis, SOX compliance
• Tools: PowerPoint, Tableau, SAP, QuickBooks

The difference: "Excel" becomes "Excel (advanced: pivot tables, VLOOKUP, macros)" with specific functions listed. Financial concepts are grouped to show depth. For entry-level candidates, this level of specificity matters because you're competing against people with similar educational backgrounds. Showing exactly what you can do separates you from candidates who just list "Excel" and hope for the best.

Project Manager (Senior)

Before:

• Project management, Agile, Scrum, leadership, stakeholder management, risk management, budget management, team building, strategic planning, Microsoft Project

After:

• Methodologies: Agile (Scrum, Kanban), Waterfall, Hybrid, Lean Six Sigma (Green Belt)
• Tools & Platforms: Jira, Asana, Microsoft Project, Smartsheet, Confluence
• Certifications: PMP, CSM (Certified Scrum Master), SAFe 5 Agilist
• Technical: Budget management ($2M-$10M projects), resource allocation, risk assessment frameworks
• Industries: SaaS, financial services, healthcare IT

The difference: Certifications are called out explicitly because they're searchable requirements. Budget ranges quantify scope. Industry experience is listed because senior PMs often get hired for domain knowledge as much as methodology. The soft skills from the before version are now proven in experience bullets.

Registered Nurse (ICU)

Before:

• Patient care, compassionate, critical thinking, IV insertion, medication administration, team player, BLS, ACLS, detail-oriented, electronic health records

After:

• Clinical Skills: Advanced cardiac life support, hemodynamic monitoring, ventilator management, central line care, titration of vasoactive drips
• Certifications: RN (Ontario), BLS, ACLS, CCRN (Critical Care Registered Nurse)
• Systems & Technology: Epic, Cerner, Meditech, IV pump programming
• Specializations: Post-cardiac surgery care, sepsis management, trauma resuscitation

The difference: Specific clinical competencies replace vague patient care language. Certifications include the credential acronyms that nurse recruiters search for. EHR systems are named specifically. The specializations show ICU depth rather than general nursing skills.

Common Skills Section Mistakes (And How to Fix Them)

Even with good examples, candidates make predictable errors. Here are the five I see most often in resume reviews, with specific fixes.

Mistake 1: Listing Skills You Don't Actually Have

A candidate once listed "advanced Python" on his resume. In the technical interview, they asked him to explain list comprehensions. He couldn't. The interview ended in twelve minutes. If you took one Coursera course or used a tool once in 2023, it's not a resume skill. The interview will expose you, and you'll have wasted everyone's time including your own.

Fix: Only list skills you could discuss competently in an interview today. If you need a refresher before you could explain it, leave it off.

Mistake 2: Using the Same Skills Section for Every Application

Your skills section should flex to match each job posting. A data analyst role emphasizing SQL and Tableau needs different skill ordering than one focused on Python and machine learning. Generic applications get generic results. I tracked this with a client: when she customized her skills section to mirror job posting language, her callback rate jumped from 8% to 31%.

Fix: Spend five minutes reordering and adjusting your skills section for each application. Lead with what they want most.

Mistake 3: Burying Important Skills in Paragraphs

Some candidates write skills into their summary or scatter them through experience bullets without a dedicated section. This fails ATS parsing. When a recruiter searches for "Salesforce," the system looks for exact keyword matches, often in specific sections. If your Salesforce expertise is buried in a paragraph about Q3 sales achievements, the ATS might miss it entirely.

Fix: Have a clearly labeled "Skills" or "Technical Skills" section. Then reinforce those skills with context in your experience bullets.

Mistake 4: Listing Soft Skills Without Proof

"Leadership," "communication," "problem-solving" mean nothing in a skills list. Every candidate claims them. They're not searchable. They're not verifiable. They take up space that could go to actual technical competencies.

Fix: Delete soft skills from your skills section entirely. Prove them in your experience bullets with specific outcomes. "Led cross-functional team of 12 through product launch, delivering two weeks ahead of schedule" proves leadership. The word "leadership" in a list proves nothing.

Mistake 5: Using Skill Ratings or Progress Bars

Those visual resume templates with skill bars showing "Excel: 85%" or star ratings look modern but create two problems. First, ATS systems can't parse graphics, so your skills become invisible to automated screening. Second, what does "85% proficient in Excel" even mean? Compared to whom? Based on what standard?

Fix: Use a clean, text-based format. If you want to indicate proficiency level, use words: "Python (advanced)," "Spanish (conversational)," "Tableau (intermediate)." Better yet, let your experience bullets demonstrate proficiency through what you've accomplished with each skill.

Where to Put Your Skills Section (Format and Placement)

Location matters. For most candidates, the skills section belongs after your professional summary and before your work experience. This placement serves ATS parsing and human readers equally: systems find keywords early, and recruiters see your qualifications before diving into job history.

For technical roles, some candidates put skills at the very top, immediately after contact information. This works if your technical stack is your primary selling point and you're applying to roles where specific tools matter more than company names. A software engineer with strong Python/AWS skills might lead with that rather than a job title from a company recruiters don't recognize.

For career changers, skills can help bridge the gap between your old field and your new one. If you're transitioning from teaching to instructional design, leading with "Articulate Storyline, Adobe Captivate, learning management systems" signals capability before your job titles suggest otherwise. Strategic placement helps reframe your narrative when your work history doesn't obviously connect to the target role.

One format I recommend for technical roles: category headers with skills listed underneath. Instead of a flat list of fifteen tools, group them logically. "Programming Languages: Python, JavaScript, SQL" then "Cloud Platforms: AWS, Azure" then "Databases: PostgreSQL, MongoDB, Redis." This organization helps recruiters assess your full technical stack quickly while keeping related skills together.

How to Identify Which Skills to Include

The job posting tells you exactly what to include. I'm not suggesting you copy-paste their requirements list into your resume. I'm saying you should treat the posting as a blueprint for which of your many skills deserve the limited space on your resume.

Here's the process I use with coaching clients:

1. Pull up the job posting and highlight every skill, tool, or qualification mentioned. Include both the required and preferred sections.
2. Make a list of all your relevant skills, even ones not mentioned in the posting. Be honest about proficiency.
3. Match your skills to their requirements. Direct matches go on your resume first. Adjacent skills (they want Tableau, you have Power BI) go second.
4. Add 2-3 skills not in the posting but relevant to the role. This shows depth beyond their minimum requirements.
5. Cut everything else. If a skill isn't relevant to this specific job, it's taking space from skills that are.

A client applied for a data analyst role that mentioned SQL five times, Python twice, and Tableau once. Her skills section led with "Python, R, SQL, Tableau" because she'd used Python more recently. We reordered to "SQL, Python, Tableau, R" to mirror their priorities. She got the interview. Small changes compound.

If you're struggling to identify which skills matter most, an ATS-optimized resume builder can analyze job postings and suggest relevant skills based on the role and industry. But the final decision about what to include should still be yours, based on what you can actually discuss in an interview.

Skills Section FAQ

These are the questions I get asked most often in coaching sessions about skills sections.

Should I include Microsoft Office?

Only if the job posting specifically requires it or if you have genuinely advanced skills. For most professional roles, basic Word and email proficiency is assumed. But if you're applying for an executive assistant role that requires "advanced PowerPoint and Excel," then yes, list "Microsoft Office Suite (advanced PowerPoint, Excel with macros and pivot tables)." Specificity matters.

How do I list skills I'm currently learning?

Don't put them in your skills section. If you're halfway through a Python course, you can mention it in a "Professional Development" section or in your summary as "Currently developing Python skills for data analysis." But the skills section should only include abilities you could use on the job starting next week. Aspirational skills belong elsewhere or nowhere.

What if I have more than 12 relevant skills?

Prioritize ruthlessly. List the 10-12 most relevant to the specific job. The others can appear in context within your experience bullets. A skill mentioned in an accomplishment bullet still counts for ATS keyword matching. You don't need to list every competency in one section.

Should I separate technical and soft skills into different sections?

No. Have one "Skills" or "Technical Skills" section with hard skills only. Soft skills don't belong in a separate section either. They belong demonstrated through outcomes in your experience bullets. The two-section approach just gives you more space to list vague qualities that don't help your candidacy.

Can I use acronyms or should I spell everything out?

Use the version that appears in the job posting. If they write "Search Engine Optimization (SEO)," use that format the first time, then SEO after. If they just write "SEO," use the acronym. Some ATS systems search for both, but matching their exact language is safest. When in doubt, use "Full Name (ACRONYM)" format for the first mention.