How to Write the Skills Section of Your Resume (With Examples)
The skills section is the most misunderstood part of a resume. Most people treat it as a junk drawer for buzzwords, or decorate it with star ratings that prove nothing. Done right, it is a fast, scannable proof that you fit the job, and it is one of the first places an applicant tracking system (ATS) hunts for keywords. This guide shows you exactly what to list, how to group and order it, how many skills to include, where to place it, and the quiet mistakes that sink otherwise strong resumes.
Hard skills vs soft skills, and why the difference decides everything
Hard skills are specific, teachable, and provable: Python, financial modeling, SQL, AutoCAD, GST filing, Salesforce, Tableau, spoken Mandarin. You either have them or you don't, and an interviewer can test them. Soft skills are behavioral traits: communication, leadership, problem-solving, adaptability, teamwork.
Here is what most people get wrong. Your skills section should be built almost entirely from hard skills. Soft skills belong in your work experience, where you can prove them, not in a list where anyone can claim them. "Leadership" sitting in a skills box is just a word. "Led a 6-person team to ship a feature two weeks ahead of schedule" in your experience section is evidence a recruiter can believe.
Recruiters have read "strong communicator" and "team player" thousands of times, so those phrases carry no weight on their own. The skills section is where you signal concrete capability and feed the ATS the exact terms it scans for. Keep the soft skills for the bullets that back them up with a result.
Rule of thumb: if a skill can be tested in an interview, it belongs in the skills section. If it can only be shown through a story, it belongs in your experience.
Choose skills by mirroring the job description
The single most effective move is to read the job description and mirror its exact language. If the posting says "data visualization," don't write "making charts." If it asks for "stakeholder management," use that phrase, not "working with people." Keyword matching is usually literal, so the wording has to line up.
Do this for every application. Open the job post, highlight every tool, technology, methodology, and named skill, then map those against what you genuinely have. The overlap becomes your skills section. Skills the job never mentions are lower priority; skills the job wants and you possess should move to the top.
One caution: only list skills you can defend in an interview. Mirroring means matching real ability to the right words, not lying. If you write "advanced Excel" but freeze on a VLOOKUP, the keyword only got you into the room to be exposed in it.
If you are applying to several similar roles, build one master list of everything you can do, then trim and reorder it per application. MantraCV's live ATS score flags keywords from the job description that are missing from your resume, so you can close the gaps before a human ever sees it.
Tailor per job. A generic skills section you never change is the fastest way to score low on keyword match.
Group your skills into clear, labelled categories
A flat, comma-separated wall of 30 skills is hard to scan and signals no judgment about what matters. Grouping shows you understand your own field and lets a recruiter find what they need in seconds.
Pick categories that fit your role. A developer might use Languages, Frameworks, Databases, Cloud & Tools. A marketer: Channels, Analytics, Tools, Content. An accountant: Accounting, Compliance, Software, Reporting. Put the most job-relevant category first, even if it isn't your personal favorite.
Keep each category to a tight, relevant set instead of dumping everything you have ever touched. Within a group, lead with the strongest, most in-demand skills. A clean grouped layout also stays ATS-safe, because the keywords are still plain text, just organized for the human reading them.
- Lead with the category the job cares about most, not alphabetically and not by your comfort level.
- Aim for roughly 3 to 5 categories; beyond that it starts to read as noise.
- Use real category names (Languages, Cloud, Analytics), never vague ones (Other, Misc, Strengths).
How many skills to list, and where to place the section
For most people, 8 to 15 skills is the sweet spot, spread across your categories. Enough to show range, few enough that each one earns its place. A list of 40 skills doesn't read as capable, it reads as unfocused, and it dilutes the keywords that actually matter.
Placement depends on who you are. Freshers, students, and career changers should put the skills section high, right under the summary, because skills are your strongest card when your work history is thin or in a different field. For experienced professionals, work experience is the headline, so skills usually sit just below it, or in a compact band near the top when the role is heavily technical.
One ATS note that trips up good candidates: avoid multi-column layouts and text boxes for your skills. Many parsers read straight across the full width of the page and scramble two-column content, or skip text trapped inside a box entirely. A single-column layout, like the ATS-safe templates in MantraCV, stays readable for both the software and the human.
Tech and data roles can run a slightly longer skills section because the tooling list is genuinely long. A nurse or a copywriter should keep it tight.
State proficiency in words, not graphics
You will sometimes want to show level, and that is fair, especially for languages and a few headline tools. Do it in plain words a recruiter and a parser both understand: "Advanced," "Proficient," "Working knowledge," or for languages "Native," "Fluent," "Conversational." These map to shared, well-understood meanings.
A simple, honest format is to add the level in parentheses only where it adds information: "Python (advanced), SQL (advanced), R (working knowledge)." Don't tag every single skill, or the section turns into a wall of qualifiers; reserve it for the few where level genuinely changes how a recruiter reads you.
Resist the urge to inflate. "Expert" should mean you could teach it; "native fluency" should mean exactly that. The fastest way to lose a recruiter's trust is a level claim that collapses in the first five minutes of a technical screen.
For spoken languages, the CEFR-style words (native, fluent, conversational, basic) read more credibly than vague labels like "good."
What NOT to do: skill bars, rating dots, and fluff
Skip the visual ratings. Progress bars, star ratings, and five-dot scales look modern but they are a trap. They are meaningless, because your "4 out of 5" in Python tells a recruiter nothing without a shared scale. ATS software cannot read a graphic, so the skill behind the bar may not register at all. And rating yourself below full marks invites doubt, while rating everything at full marks invites disbelief.
Cut the fluff words too. "Hardworking," "motivated," "detail-oriented," "go-getter," "synergy," and "thinks outside the box" are filler that nearly every resume carries and no recruiter trusts. They occupy space a real keyword could have used.
Don't list the obvious either. "Microsoft Word," "email," and "internet research" are assumed in 2026, and listing them can make you look out of touch. Never invent proficiency you lack; "expert" in a tool you opened twice will collapse the moment it is tested.
- No skill bars, percentages, dots, or star ratings.
- No generic personality adjectives masquerading as skills.
- No basic computer literacy that everyone is assumed to have.
- No skills you couldn't demonstrate if asked to right now.
Example skills sections for four roles
Here is what tight, grouped, ATS-friendly skills sections look like in practice. Each is built around its target role, uses plain text and real categories, and carries no ratings. Adapt the wording to match the exact job posting you are answering.
Software Developer (3 years):
Languages: Python, JavaScript, TypeScript, SQL | Frameworks: React, Node.js, Django | Databases: PostgreSQL, MongoDB, Redis | Cloud & Tools: AWS, Docker, Git, CI/CD, Jira
Digital Marketing Specialist:
Channels: SEO, Google Ads, Meta Ads, Email Marketing | Analytics: Google Analytics 4, Search Console, A/B testing | Tools: HubSpot, Mailchimp, Semrush, Canva | Content: Copywriting, landing-page optimization
Fresher / Final-year Engineering Student:
Technical: Java, C++, SQL, HTML/CSS | Tools: Git, VS Code, MySQL Workbench | Coursework: Data Structures, DBMS, Operating Systems | Languages: English (fluent), Hindi (native)
Accountant (mid-career, India):
Accounting: Accounts payable/receivable, reconciliation, month-end close | Compliance: GST, TDS, income-tax filing, statutory audit support | Software: Tally ERP 9, SAP FICO, Excel (advanced) | Reporting: MIS reports, cash-flow forecasting
Notice none of these list "communication" or "teamwork." Those live in the experience bullets, where they can be proven with a result.
Key takeaways
- Build your skills section from hard, testable skills; prove soft skills in your experience bullets with results, not in a list.
- Mirror the exact wording of each job description so your keywords match what the ATS scans for, and tailor it per application.
- Group 8 to 15 skills into 3 to 5 clearly labelled categories, leading with what the job values most.
- Place skills high for freshers and career changers, below experience for seasoned professionals, always in a single-column layout.
- Show level in plain words where it helps; never use skill bars, rating dots, fluff adjectives, or obvious basics like Microsoft Word.
Put this into practice
Build an ATS-safe resume with live scoring guiding every line. Free to build — export to PDF or DOCX.
Frequently asked questions
Should I put soft skills in my resume skills section?
Mostly no. Soft skills like communication and leadership are easy to claim and impossible to verify in a list, so recruiters discount them. Prove them instead in your work experience with concrete examples, such as a bullet showing you led a team or resolved a client conflict. Reserve the skills section for hard, testable skills and the keywords the job actually asks for.
How many skills should I list on a resume?
For most roles, 8 to 15 is ideal, organized into 3 to 5 categories. That is enough to show range without diluting your strongest keywords. Highly technical roles like software or data can run a bit longer because the genuine tooling list is large, while clinical or creative roles should stay tight and selective.
Are skill bars and rating dots a bad idea?
Yes. They look polished but mean nothing without a shared scale, and most applicant tracking systems cannot read graphics, so the skill may not register at all. Rate everything as expert and you look unbelievable; rate honestly and you plant doubt. List skills as plain text and let the interview verify your level.
Where should the skills section go on my resume?
It depends on your experience. Freshers, students, and career changers should place skills high, right under the summary, because skills are their strongest selling point. Experienced professionals should put work experience first and skills just below it. In every case, keep it in a single-column layout so the ATS can parse it cleanly.
How do I know which skills to include for a specific job?
Read the job description and highlight every tool, technology, and named skill, then list the ones you genuinely have using the posting's exact wording. That overlap is your tailored skills section. Tools like MantraCV's live ATS score show which job keywords are still missing, so you can close the gap before you apply.