How to List Skills on a Resume (+ Examples)
Last updated:
The skills section is one of the most-read and most-misused parts of a resume. Recruiters scan it in seconds to confirm you have what the job needs, and applicant tracking systems (ATS) parse it for the exact keywords from the job description. Done well, it gets you past the first filter. Done poorly — a generic wall of buzzwords, or skill bars an ATS can't read — it wastes the prime real estate near the top of your page.
This guide covers the decisions that actually matter: where skills belong (in a dedicated section and inside your experience bullets — both), which skills to include and how many, how to choose them by mirroring the job description, how to prove a skill instead of merely claiming it, and how to format the section so an ATS can read it. There is a copyable skills-section template and strong examples at the end.
Where skills go on a resume (two places, not one)
The most common mistake is treating the skills section as the only place skills live. The strongest resumes put skills in two places that do different jobs. A dedicated "Skills" section gives recruiters and the ATS a fast, scannable keyword block, usually placed just under your summary near the top of the page. Your experience bullets are where those same skills show up in context — applied to a real task with a real result — which is what actually convinces the human reading after the ATS.
Think of it as claim and proof. The skills section claims you have a skill; the bullet proves it. Listing "SQL" in your skills section gets you matched; a bullet that reads "Built SQL pipelines that cut reporting time 40%" is what gets you the interview. A skill that appears in your section but never in your experience reads as a keyword you padded in — and a skill in your bullets that never makes the section can be missed by an ATS scanning for the exact term.
What each placement is for
- Dedicated Skills section — a scannable, categorized keyword block near the top. This is your ATS-match surface and the first thing a recruiter's eye lands on after your summary.
- Inside experience bullets — the same skills, demonstrated with a task and a result. This is your proof, and where the human reader is persuaded.
- Optionally in the summary — your two or three signature skills can appear in your professional summary up top, especially if they define the role you're targeting.
Hard skills vs. soft skills (quick version)
Hard skills are specific, teachable, and verifiable — Python, financial modeling, Salesforce, Spanish, AWS. Soft skills are interpersonal and behavioral — communication, leadership, problem-solving, adaptability. Both belong on a resume, but they earn their place differently.
Lead your skills section with hard skills, because those are what the ATS and the hiring manager screen for and what the job description usually names explicitly. Keep soft skills to a short, honest handful — and prove them in your experience bullets rather than stacking adjectives in a list. Anyone can type "strong leadership"; a bullet that says "Led a team of 6 through a platform migration delivered two weeks early" proves it. For the full breakdown of which is which and how to balance them, see our guide on hard skills vs. soft skills.
How many skills to list, and how to choose them
Aim for roughly 8-12 skills in your dedicated section — enough to cover the core competencies the role needs, few enough that each one is clearly relevant. A section with 30 skills isn't impressive; it signals you copied a list instead of choosing the ones that fit. Quality and relevance beat quantity every time.
Choose those 8-12 by mirroring the job description. Read the posting, pull out the skills, tools, and qualifications it names — especially anything in the "requirements" or "what you'll do" sections — and reflect the ones you genuinely have back in your wording. ATS match resumes against the posting's keywords, so using the employer's exact phrasing ("project management," not "managing projects"; "JavaScript," not "JS") is one of the most reliable ways to rank higher in the screen.
Mirroring the job description (the right way)
- List the job's named tools and technologies in the exact form it uses — match "Microsoft Excel," "Adobe Photoshop," or "Kubernetes" word for word.
- Include both the spelled-out term and its acronym where relevant ("Search Engine Optimization (SEO)") so you match either ATS configuration.
- Only mirror skills you can actually back up in an interview — keyword-stuffing a skill you don't have backfires the moment you're asked about it.
- Prioritize skills that appear in the requirements section over nice-to-haves, and lead with the ones repeated most often.
Not sure which skills your role needs?
If you're staring at a blank section, start from a role-specific list and trim to the job. Our resume skills by role pages list the most in-demand hard and soft skills for dozens of jobs — from software engineer and data analyst to nurse, accountant, and project manager — so you can pick the relevant ones and phrase them the way employers do.
Prove your skills — don’t just list them
A skills section that isn't backed up anywhere is weak. The fix is evidence: for every important skill, make sure it shows up in an experience bullet attached to a concrete action and, ideally, a measurable result. This is the single biggest difference between a resume that lists skills and one that demonstrates them.
The reliable pattern is skill + what you did with it + the outcome. Don't write "Skilled in data analysis." Write "Analyzed 12 months of churn data in SQL and Tableau, surfacing the three drivers behind a 40% improvement in retention." The second version contains the same keywords the ATS wants and the proof the hiring manager wants — in one line.
| Skill claimed in section | Weak (just listed) | Strong (proven in a bullet) |
|---|---|---|
| Project management | Project management | Managed a $1.2M product launch across 4 teams, delivered on time and 8% under budget |
| SQL | SQL | Built SQL reporting pipelines that cut weekly reporting time from 6 hours to 1 |
| Customer service | Excellent customer service | Resolved 60+ support tickets per day at a 97% satisfaction rating |
| Leadership | Strong leadership | Led and mentored a team of 6, cutting onboarding time for new hires by half |
How to format the skills section (ATS-safe)
Format the section as plain, categorized text lists. Group related skills under short labels — "Technical Skills," "Tools & Software," "Languages" — and list each group as a simple comma-separated line. Categories make a long list scannable and help a recruiter find what they're looking for without reading every word.
Critically, do not use skill bars, star ratings, percentages, or graphics to show proficiency. They look modern, but an ATS reads them as nothing — or as garbled text — so the skill effectively disappears from the scan. They also force a reader to guess what "4 out of 5 stars in Python" means. If you want to convey level, use plain words like "Fluent," "Proficient," or "Working knowledge" for languages, and let your experience bullets do the rest. Keep the whole section in standard resume formatting with no tables, text boxes, or columns that can confuse a parser.
Do
- Group skills into 2-4 short, labeled categories.
- Write each category as a plain comma-separated list.
- Use the exact terms (and acronyms) from the job description.
- Use plain words for language proficiency ("Fluent," "Conversational").
Don't
- Use skill bars, star ratings, dials, or percentage graphics — ATS can't read them.
- Bury skills in tables, columns, or text boxes that break parsing.
- Pad the section with 20+ generic skills or a string of soft-skill adjectives.
- List a skill you can't demonstrate or discuss in an interview.
Skills section examples
Here are strong, categorized skills sections for three different roles. Notice that each leads with hard, job-specific skills, keeps soft skills short, and uses plain comma-separated lists — no bars or ratings.
Software engineer
- Languages — Python, JavaScript, TypeScript, SQL, Go
- Frameworks & Tools — React, Node.js, Django, Docker, Kubernetes, Git
- Cloud & Data — AWS, PostgreSQL, Redis, CI/CD pipelines
Marketing manager
- Marketing — SEO, SEM, content strategy, email marketing, A/B testing
- Tools — Google Analytics, HubSpot, Google Ads, Meta Ads Manager, Figma
- Strengths — Cross-functional collaboration, data-driven decision-making
Registered nurse
- Clinical — Patient assessment, medication administration, IV therapy, wound care
- Certifications — RN (active), BLS, ACLS
- Systems — Epic EHR, Cerner, telemetry monitoring
Copyable skills-section template
Drop this structure into your resume and swap in the skills your target job names. Keep it to 2-4 categories and 8-12 total skills, and mirror the job description's exact wording.
Skills section template
SKILLS Technical Skills: [Skill], [Skill], [Skill], [Skill] Tools & Software: [Tool], [Tool], [Tool] Languages: [Language] (Fluent), [Language] (Conversational) Example — Data Analyst: Technical Skills: SQL, Python, Excel, statistical analysis, data visualization Tools & Software: Tableau, Power BI, Google Analytics, Snowflake Strengths: Stakeholder communication, problem-solving
Common mistakes to avoid
- Listing skills only in a section and never proving them in your experience bullets.
- Using skill bars, star ratings, or graphics an ATS can't read.
- Padding the section with 20+ skills or a long string of soft-skill adjectives.
- Using generic phrasing instead of the exact keywords from the job description.
- Keyword-stuffing skills you can't actually back up in an interview.
- Hiding skills in tables, columns, or text boxes that break ATS parsing.
Get a skills section that beats the ATS
Resumly's AI resume builder pulls the right skills from the job description, places them where recruiters and ATS expect, and then runs a free ATS check on the whole resume. Free to start, no credit card.
Build my resume freeFree forever plan · No credit card required
Frequently asked questions
How many skills should you list on a resume?
List about 8-12 skills in your dedicated skills section — enough to cover the role’s core requirements, few enough that each is clearly relevant. Choose them by mirroring the specific job description rather than listing every skill you have. Relevance matters far more than quantity; a tight list of on-target skills beats a wall of generic ones.
What is the difference between hard skills and soft skills on a resume?
Hard skills are specific and verifiable (Python, financial modeling, Spanish, AWS); soft skills are interpersonal (communication, leadership, adaptability). Lead your skills section with hard skills because that’s what the ATS and hiring manager screen for, and keep soft skills short — proving them in your experience bullets instead of stacking adjectives. See our hard skills vs. soft skills guide for the full breakdown.
Where should you put the skills section on a resume?
Put a dedicated, labeled skills section near the top, just under your professional summary, so recruiters and ATS see it immediately. But skills should live in two places: the section gives a fast keyword block, and your experience bullets prove each skill with a real task and result. The strongest resumes do both.
Should you use skill bars or ratings on a resume?
No. Skill bars, star ratings, dials, and percentage graphics may look modern, but applicant tracking systems can’t read them — the skill effectively disappears from the scan — and they make readers guess what a rating means. Use plain comma-separated lists instead, and convey language proficiency with words like "Fluent" or "Conversational."
How do you choose which skills to put on a resume?
Mirror the job description. Pull the skills, tools, and qualifications the posting names — especially in its requirements section — and reflect the ones you genuinely have back in the employer’s exact wording, since ATS match against those keywords. If you’re unsure what your role needs, start from a role-specific skills list and trim it to the job.
Is it enough to just list skills, or do you need to prove them?
Listing isn’t enough. The skills section claims you have a skill; your experience bullets prove it. For every important skill, show it in a bullet attached to a concrete action and, ideally, a measurable result — for example, "Built SQL pipelines that cut reporting time 40%." That single line carries the keyword the ATS wants and the evidence the hiring manager wants.
