How to List Skills on a Resume (With Examples)
Which skills to put on your resume, how many, where they go and how to prove them. A simple method that works for recruiters and ATS software, with examples.
A skills section is the part of a resume recruiters scan fastest and trust least. Anyone can type "Python" or "leadership". What makes skills count is two things: they match the job, and your experience proves them.
Hard skills and soft skills
- Hard skills are specific and testable: SQL, Tally, AutoCAD, React, GST filing, Google Ads, financial modelling, a language.
- Soft skills are how you work: communication, problem solving, leadership, attention to detail.
Hard skills belong in your skills section. Soft skills mostly don't. Writing "excellent communication" proves nothing. Writing "presented quarterly results to the leadership team" in a bullet proves it.
Step 1: start from the job description
Read the ad and highlight every skill, tool and qualification it names. Sort them into three groups:
- Required: phrases like "must have", "3+ years of", or anything in the first few bullets.
- Nice to have: "preferred", "a plus", "bonus".
- Everything else: general phrases that describe the team rather than the role.
Your skills section should cover the first group wherever it is honestly true for you, and some of the second.
Step 2: use the employer's words
If the ad says "Microsoft Excel", don't only write "spreadsheets". If it says "Google Analytics 4", write that, not just "web analytics". Screening software and recruiters both look for the exact terms, and an abbreviation alone can be missed. Write it both ways once: "Search engine optimisation (SEO)".
Step 3: group them so they're quick to scan
A long comma-separated paragraph is hard to read. Group skills by type instead:
Data: SQL (PostgreSQL), Python (pandas), Excel (Power Query, pivot tables), Power BI
Tools: Jira, Git, Airflow
Languages: English (fluent), Hindi (native), Telugu (native)
For non-technical roles the groups might be "Accounting", "Software" and "Compliance", or "Sales", "CRM" and "Languages".
How many skills?
Usually 8 to 15. Fewer can look thin, especially for technical roles. Many more and the important ones get lost, and the reader starts to doubt that you know all of them well. Cut anything that every candidate has (MS Word, email, internet browsing) unless the job specifically asks for it.
Where the section goes
- Freshers and career changers: near the top, after the summary. Skills are your strongest evidence.
- Experienced candidates: after experience. Your roles do most of the work, and the skills section is a quick summary.
- Technical roles: either works, but keep it near the top half of page one so the reader sees the stack early.
Step 4: prove every important skill in a bullet
This is what separates a strong resume from a list of keywords. For each skill that the job really cares about, make sure at least one bullet shows you using it:
- Skill listed: SQL
- Bullet that proves it: "Wrote SQL reports on 2 million orders that cut the weekly sales review from three hours to 20 minutes."
If a skill is in your list but nowhere in your experience, either add a bullet that shows it or ask yourself whether it should be there.
Should you rate your skills?
Avoid star ratings and progress bars. "4 out of 5 in Java" means nothing to a reader, an ATS can't read the graphic, and rating yourself low on anything is self-defeating. If level matters, use words: proficient, working knowledge, fluent, native. For languages, these are standard and useful.
What if you're missing a skill the job asks for?
Don't claim it. If you've started learning it, say so honestly, for example "Tableau (completed course, building first dashboards)". Our guide on what to do about a missing skill covers the options in more detail.
Final check
Compare your skills section with the job ad one more time. Each required skill should be either on your resume or deliberately left off because you don't have it. Then run the free ATS check to see whether the section is read correctly.