How to write the skills section of your resume (with examples)
Updated October 2026 · By the ClaudeCV Editorial Team
The skills section is small, but it can decide whether your resume passes both a human skim and an automated screening. Recruiters use it to check quickly whether you have the tools and abilities required. Done well, it works like an index of your strengths. Done badly, it is a long, vague list that says nothing. Here is how to get it right.
What the skills section is for
This section serves two purposes. First, it gives a quick overview so the recruiter can see, in seconds, that you match the main requirements. Second, it helps applicant tracking systems find keywords that appear in the job description. It should support the rest of your resume, not replace evidence in your experience section.
Hard skills vs soft skills
Hard skills are specific, teachable abilities such as programming languages, software, foreign languages, accounting methods, machine operation or clinical procedures. Soft skills are interpersonal and personal traits such as communication, leadership, adaptability and problem solving.
Hard skills are easy to verify and easy to search, so they usually deserve most of the space in the skills section. Soft skills are harder to prove with a single word, so it is better to demonstrate them in your bullet points through stories: "Led a team of six through a system migration, meeting the deadline with no downtime" says more than "leadership".
Find the right skills to list
1. Read the job description and highlight every skill, tool or qualification mentioned.
2. Compare with your own experience and pick the ones you honestly have.
3. Check similar job posts to see which terms appear repeatedly in your field.
4. Add specialist skills that set you apart, such as a niche tool or certification.
Never list a skill you cannot back up. If you are asked about it in an interview and cannot answer, it can cost you the job.
Organize by category
Grouping makes the section easy to scan. Examples:
- For a developer: Languages: JavaScript, Python, SQL | Frameworks: React, Node.js | Tools: Git, Docker, AWS
- For a marketer: Channels: SEO, email, paid social | Tools: Google Analytics, HubSpot, Canva
- For an accountant: Software: Excel, QuickBooks, SAP | Areas: reconciliation, reporting, tax preparation
Put the most relevant category first. Avoid long, unsorted lists of twenty items, which look padded.
Level of detail
Where it matters, add a level or context: "Spanish (fluent)", "Excel (advanced: pivot tables, lookups, macros)" or "Python (5 years, data analysis)". Avoid star ratings and progress bars; they are subjective and cannot be read by many screening systems.
Where to place it
For technical roles, a skills section near the top helps the reader see your fit quickly. For roles where achievements matter more, place it after your experience. In either case, keep it above the education section unless you are a recent graduate.
Keep it honest and current
Remove outdated tools that no longer matter, such as old software versions, and obvious skills like "Microsoft Word" for professional roles where they are assumed. Update the list every time you learn something new or start a new job.
Use the same wording as the job post
If the job description says "customer relationship management (CRM)", include both the phrase and the tool name, such as "CRM (Salesforce)". Spelling out abbreviations at least once helps recruiters and software recognize the term. Do not copy a whole list of requirements you do not meet.
Examples of weak vs strong skills lines
Weak: "Hard-working, team player, good communicator, fast learner, computer skills."
Strong: "Project management (Agile, Scrum) | Tools: Jira, Asana, Excel | Reporting: KPI dashboards, budget tracking | Languages: English (native), German (intermediate)."
The strong version is specific, searchable and gives the reader real information.
Common mistakes
- Listing too many skills with no priority
- Adding vague personality traits
- Including skills that are not relevant to the role
- Using graphics or bars that software cannot read
- Claiming expert level in everything
Example: rebuilding a skills section for one job
Suppose you are applying for an operations coordinator role. The job description mentions scheduling, vendor communication, inventory tracking, Excel, and Asana. Your first draft looks like this:
"Hard worker, good at multitasking, team player, computer skills, MS Office."
A better version:
- Operations: scheduling, vendor coordination, inventory tracking, purchase orders
- Tools: Excel (pivot tables, lookups), Asana, Google Workspace
- Communication: supplier negotiations, cross-team updates, report writing
- Languages: English (native), Spanish (conversational)
Each item can be discussed in an interview and matches the posting. Then your experience bullets show these skills in action, such as "Negotiated delivery schedules with six vendors, reducing late shipments by about a quarter".
A simple test for each skill
Ask three questions: Could I use this skill tomorrow if the job needed it? Can I give an example of using it? Is it relevant to the target role? If the answer to any is no, cut it or move it lower.
Keeping a living skills inventory
Keep a private document with all your skills, tools, projects and the dates you last used them. When you apply, choose the ones that fit. Refresh it every few months, and note skills you want to learn next so you can plan courses or projects.
Skills for different career stages
Early in your career, your skills section may carry more weight because you have fewer jobs to show, so it deserves careful thought and a few proof points such as coursework or projects. Mid-career professionals can shorten it and let achievements speak. Senior professionals often replace a long tool list with a compact line of areas of expertise, such as strategy, budgeting, team leadership and stakeholder management, since tools change while leadership skills stay relevant. Review your section each time you apply and adjust its length to fit your stage.
Final thoughts
Think of the skills section as a curated shelf, not a storage room. Choose the skills that matter for this specific job, organize them clearly, and support them with evidence elsewhere on the resume. That combination shows both breadth and proof, which is what recruiters want.
Related reading
- How to find and use resume keywords from a job description
- How to write a resume summary: formulas, examples and mistakes to avoid
- Data analyst resume guide: skills, projects and examples that recruiters look for
Pick a clean, ATS-friendly template and export a PDF in minutes.
Start building →