A useful skills section is selective, relevant, and supported by evidence. It helps the reader identify tools and capabilities quickly, but it should not replace examples in your experience, projects, or education.
Start with the work, not a generic list
Review the job posting and separate its requirements into tools, methods, knowledge, communication, and operational responsibilities. Match those requirements against work you have actually completed. Prioritize the overlap.
Hard skills
Hard skills are specific capabilities that can often be taught, practiced, or assessed. Examples include:
- Spreadsheet reporting and data cleanup.
- Bookkeeping software and invoice processing.
- JavaScript, SQL, version control, or API integration.
- Inventory control, scheduling, or point-of-sale systems.
- Graphic design tools and production workflows.
- Languages with an honest proficiency description.
Interpersonal and organizational skills
Communication, teamwork, judgment, and organization can be valuable, but labels alone are weak evidence. Demonstrate them through a situation.
Label only: Strong communication.
Evidence: Explained account requirements to customers by phone and documented next steps for the service team.
Examples by job family
Administrative roles
Scheduling, document control, spreadsheet tracking, calendar coordination, customer communication, and records maintenance.
Customer service
Case documentation, conflict de-escalation, product guidance, follow-up, ticketing systems, and written communication.
Sales
Lead qualification, needs discovery, CRM updates, proposal preparation, pipeline follow-up, and account support.
Technology
Programming languages, frameworks, testing, debugging, cloud platforms, source control, documentation, and accessible interface development.
Only include examples that reflect your own background and the target role.
Create a skills inventory
Before selecting skills for one resume, create a private inventory. Group items by software, equipment, methods, languages, industry knowledge, communication, and organization. Next to each item, record where you used it and what you were able to complete.
This inventory is not the final skills section. It is a source you can filter for different applications. Remove items you cannot explain or that no longer reflect your current ability.
Distinguish exposure from working ability
Seeing a tool in a course is different from using it independently. Use honest language when that distinction matters. You might describe “coursework using SQL queries” instead of presenting SQL as an advanced professional skill. In an interview, be ready to explain the tasks you completed without help.
Demonstrate skills across sections
A skills list helps scanning, but the strongest capabilities should also appear in context:
- Summary: highlight one or two capabilities central to the role.
- Experience: connect skills to responsibilities and outcomes.
- Projects: show tools, decisions, deliverables, and collaboration.
- Education: add relevant coursework or applied assignments when useful.
Write interpersonal skills as actions
Instead of listing “leadership,” explain that you trained new team members, coordinated a schedule, or facilitated a project handoff. Instead of “problem-solving,” describe the issue you investigated and the change you made. Evidence makes a broad capability meaningful.
Update skills when the target changes
A sales resume and an operations resume may use different selections from the same background. Reorder and remove skills based on the job, but keep terminology consistent with your actual use. Do not rename a basic capability to imply a more advanced one.
Examples of precise skill descriptions
- Spreadsheets: pivot tables, lookup functions, data validation, and recurring reports.
- Customer support: case documentation, email support, escalation, and follow-up.
- Web development: semantic HTML, responsive CSS, JavaScript, Git, and accessibility testing.
- Project coordination: schedules, action items, status updates, and dependency tracking.
These descriptions are examples of specificity, not a list to copy.
Where to place skills
Use a dedicated skills section for quick scanning, then demonstrate the most important capabilities in experience or project bullets. A key skill may also appear in the professional summary when it is central to your fit.
Use precise proficiency language
Avoid stars, bars, and percentages. When a level matters, describe what you can do: “Excel: pivot tables, lookup functions, and monthly reporting” is more useful than “Excel: 90%.” For languages, use a consistent description you can explain.
Skills and ATS terminology
Applicant tracking systems vary. Use recognizable terms from the posting when they match your experience, but preserve natural sentences and standard section headings. Read the ATS optimization guide for limitations and formatting advice.
Skills section checklist
- Every listed skill is relevant to the target role.
- You can explain when and how you used it.
- Important skills also appear in evidence-based bullets.
- Terms are specific rather than broad personality claims.
- No unsupported rating bars or invented proficiency levels appear.
Explore additional structures in the resume phrase library, then organize the final list in the resume builder.
Frequently asked questions
How many skills should I list on a resume?
List a focused set that is relevant to the role and supported by your experience. Quality and evidence matter more than reaching a fixed number.
What is the difference between hard and soft skills?
Hard skills are job-specific tools, methods, or technical capabilities. Soft skills describe how you communicate, organize, collaborate, or make decisions.
Should I use skill bars or percentages?
Usually no. A percentage has no shared standard. Use clear labels and demonstrate important skills through experience or projects.
Can I copy skills from the job posting?
Use a term only when it accurately describes a capability you possess. Do not copy requirements that you cannot support.