Evidence-First Resume Skills Guide
Skills to Put on a Resume: 120 Examples and ATS Tips
Choose role-relevant hard and soft skills, confirm every claim against real evidence, and place your strongest capabilities where employers and resume systems can understand them.
Published
Start with relevance and evidence
What skills belong on a resume?
The best skills for your resume are not the longest or most impressive list. They are the capabilities that matter to the target role and that you can support with real work, education, training, volunteering, or project evidence.
A dedicated skills section helps readers locate important information quickly. It should not replace evidence. Important skills become more credible when your experience or projects show how you used them.
Hard skills
Specific tools, systems, methods, languages, procedures, or technical capabilities learned through work, education, training, or projects.
Examples include SQL, Excel, bookkeeping, route planning, Salesforce, JavaScript, inventory control, and data visualization.
Soft skills
Ways you communicate, organize, solve problems, collaborate, adapt, or lead. These often need context to become credible.
Examples include active listening, prioritization, teamwork, conflict resolution, adaptability, and attention to detail.
Transferable skills
Capabilities developed in one setting that may be relevant in another, provided you explain the real context and do not overstate equivalence.
Examples include customer communication, record keeping, training, analysis, scheduling, research, and project coordination.
ResumeClimb Truth Match method
Confirm a skill before you claim it
Compare each job-description skill with your evidence. A related concept can reveal a learning path, but it does not prove the exact tool, method, credential, or responsibility.
Confirmed
You used the exact skill in paid work, an internship, education, volunteering, training, or a project—and can explain where and how.
Action: List it using accurate terminology and reinforce it with context elsewhere in the resume when relevant.
Related
You have adjacent experience, but it does not yet prove the exact tool, method, credential, or level requested by the employer.
Action: Keep the skill you actually used. Investigate the relationship, but do not convert related evidence into an exact claim.
Not Confirmed
The job description requests the skill, but you cannot identify evidence that you learned or used it.
Action: Leave it out. A missing requirement is more honest than an unsupported claim that may fail during screening or an interview.
How to choose resume skills step by step
- 1
Extract skills from the job description
Mark named tools, software, methods, languages, procedures, credentials, responsibilities, and repeated capabilities. Keep the employer's exact wording for comparison.
- 2
Build your own evidence inventory
Review work, internships, coursework, projects, volunteering, certifications, and training. Record where you used each skill and what you produced or supported.
- 3
Classify every possible match
Separate direct confirmation from related experience and unconfirmed requirements. Similar concepts are not automatically interchangeable.
- 4
Prioritize relevance and specificity
Choose the supported skills most important to this role. Prefer exact tools and methods over broad labels when the specific wording is accurate.
- 5
Place each skill where it has value
Use a concise skills section for scanning, then reinforce important capabilities in experience, projects, education, or certifications with truthful context.
- 6
Remove unsupported or decorative claims
Delete skills copied only from the job ad, vague traits without evidence, outdated tools that are not relevant, and proficiency ratings you cannot defend.
Categorized idea library
120 skills to put on a resume
These are examples to evaluate—not a list to copy. Use only skills that match the target job and your real evidence. Licenses, credentials, regulated procedures, equipment, and authority levels require particular care.
Tools, systems, and procedures
Administrative and business operations
Name the software or process only when you used it. Replace a broad phrase such as office skills with the specific supported capabilities.
- Microsoft Excel
- Microsoft Word
- Google Workspace
- Calendar management
- Data entry
- Records management
- Document control
- Invoice processing
- Travel coordination
- Vendor coordination
Customer, account, and revenue workflows
Customer service and sales
Separate the platform from the capability. For example, Salesforce is a tool; account management and pipeline management describe work performed.
- CRM software
- Salesforce
- Zendesk
- POS systems
- Customer support
- Complaint resolution
- Lead qualification
- Pipeline management
- Consultative selling
- Account management
Planning, delivery, and stakeholder methods
Project and product work
Do not claim a formal method or ownership level merely because you participated in a project. Describe your actual role and scope.
- Project planning
- Risk management
- Stakeholder communication
- Requirements gathering
- Agile
- Scrum
- Jira
- Resource coordination
- Budget tracking
- Process mapping
Analysis tools and reporting capabilities
Data and analytics
List tools separately when useful, then use project or experience bullets to show the data, analysis, output, or decision supported.
- SQL
- Python
- R
- Tableau
- Power BI
- Data cleaning
- Data visualization
- Statistical analysis
- Dashboard development
- Reporting automation
Languages, frameworks, databases, and practices
Software and web development
Use exact technology names and reinforce the strongest ones with a real application, feature, API, test, database, or deployment example.
- JavaScript
- TypeScript
- React
- Node.js
- REST APIs
- Git
- Automated testing
- PostgreSQL
- HTML and CSS
- CI/CD
Infrastructure, support, and security capabilities
IT, cloud, and cybersecurity
Related deployment or support work does not prove a specific cloud platform, container tool, security function, or administrative level.
- Technical support
- Windows administration
- Linux
- Computer networking
- AWS
- Microsoft Azure
- Docker
- Kubernetes
- Identity and access management
- Incident response
Financial processes, systems, and standards
Finance and accounting
Distinguish supporting a process from owning it. List standards, regulated work, and professional credentials only when they accurately apply.
- Financial reporting
- Bookkeeping
- Accounts payable
- Accounts receivable
- Budgeting
- Forecasting
- Variance analysis
- Account reconciliation
- QuickBooks
- GAAP
Campaign, audience, and communication skills
Marketing and content
Name the channel, platform, content type, or analysis performed. Do not imply strategy ownership when your role was limited to execution or support.
- Search engine optimization
- Google Analytics
- Content strategy
- Email marketing
- Social media management
- Market research
- Campaign reporting
- Copywriting
- A/B testing
- CRM segmentation
Movement, inventory, safety, and quality processes
Logistics, warehouse, and operations
Keep licenses, equipment operation, safety records, and authority levels exact. Routine exposure does not equal certification or independent operation.
- Inventory management
- Order fulfillment
- Shipping and receiving
- Route planning
- Warehouse management systems
- Forklift operation
- Quality inspection
- Safety procedures
- Procurement
- Supply chain coordination
Care, records, coordination, and outreach
Healthcare and community support
Clinical procedures, regulated access, compliance knowledge, and credentials must match your real training, authorization, and work setting.
- Patient scheduling
- Electronic health records
- Medical terminology
- Vital signs
- Care coordination
- Case documentation
- HIPAA compliance
- Community outreach
- Crisis support
- Health education
Team, training, and change responsibilities
Leadership and people operations
Show whether you led, supervised, trained, facilitated, or supported. These words represent different levels of responsibility.
- Team supervision
- Employee onboarding
- Training delivery
- Performance coaching
- Conflict resolution
- Staff scheduling
- Workload prioritization
- Cross-functional collaboration
- Change management
- Meeting facilitation
Communication, thinking, and work habits
Transferable interpersonal skills
Soft skills become more credible when an experience or project bullet shows the situation, action, and useful outcome.
- Written communication
- Verbal communication
- Active listening
- Problem-solving
- Attention to detail
- Time management
- Adaptability
- Teamwork
- Critical thinking
- Relationship building
Where to put skills on your resume
A skill can appear in more than one section when each use adds useful context. Avoid repeating the same keyword mechanically.
Dedicated skills section
Provide a concise, scannable inventory of the most relevant supported technical, procedural, language, or domain skills.
Example structure
Data: SQL, Excel, Power BI | Reporting: Dashboard development, data cleaning, variance analysis
Experience bullets
Show how an important skill was used within a responsibility, project, decision, deliverable, or supported outcome.
Example structure
Built Power BI dashboards from cleaned operational data to give department leads a consistent weekly reporting view.
Projects section
Provide context for skills learned or applied through academic, personal, freelance, volunteer, or professional projects.
Example structure
Inventory dashboard project — Cleaned sample data in Python and created an interactive Tableau dashboard for category and stock analysis.
Summary or profile
Highlight only a small number of the strongest role-relevant capabilities that are confirmed elsewhere in the resume.
Example structure
Data analyst experienced in SQL, Excel, dashboard reporting, and translating operational questions into clear findings.
Education and certifications
Identify relevant coursework, training, licenses, or credentials accurately without presenting study as professional experience.
Example structure
Coursework: Database Systems, Statistics, Data Visualization | Certification: [exact official credential name]
Turn a skill claim into evidence
A skills section names capabilities. Experience and project bullets show how those capabilities were applied. Use the stronger wording only when every detail is true for you.
Microsoft Excel
Vague claim
Excellent Excel skills
Stronger when supported
Maintained monthly expense trackers in Excel using formulas, filters, and pivot tables.
Why: The stronger version identifies the work, features used, and output without assigning an unsupported rating.
Customer service
Vague claim
Strong customer service skills
Stronger when supported
Resolved billing and account inquiries across phone and email and documented follow-up actions in the CRM.
Why: The evidence names the issue types, channels, and documentation process.
Project management
Vague claim
Project management expert
Stronger when supported
Coordinated schedules, action items, risk updates, and stakeholder communication for a cross-functional system rollout.
Why: The wording shows supported project activities without inventing expertise, certification, budget ownership, or team authority.
Communication
Vague claim
Excellent communication
Stronger when supported
Prepared weekly status summaries and explained open issues and next steps to technical and operations stakeholders.
Why: The stronger bullet demonstrates the audience, communication type, and purpose.
Leadership
Vague claim
Natural leader and team player
Stronger when supported
Trained new team members on service procedures and assisted colleagues with complex customer cases.
Why: Training and peer support are observable. Use supervised or managed only if those responsibilities were real.
Skills advice by career stage
Entry-level or no paid experience
Use skills confirmed by coursework, projects, volunteering, student organizations, caregiving, community work, or training. Label the source honestly and show what you created, analyzed, organized, or supported.
Career change
Identify transferable capabilities from your previous field, then separate them from new skills developed through verified training or projects. Do not rename past work to imitate the target role.
Experienced candidate
Prioritize current and role-relevant capabilities. Remove basic or outdated items that take attention away from stronger evidence, unless the job specifically requires them.
Candidate with many tools
Group related tools under clear labels such as Data, Development, Design, or Operations. Keep the list focused and prove the most important skills through selected accomplishments.
Building your first resume?
If you have little or no paid work experience, use the dedicated guide to identify skills from coursework, projects, volunteering, clubs, and personal work without overstating your background.
See skills for a resume with no experience →How to make a skills section ATS-friendly
- Use a conventional heading such as Skills or Technical Skills.
- Keep essential skill text selectable instead of placing it only inside images or decorative graphics.
- Use the employer's terminology when it accurately matches your evidence.
- Spell out an unfamiliar abbreviation when clarity would help, then include the abbreviation in parentheses.
- Group related capabilities under clear labels when the list is long.
- Avoid tables, rating bars, icons, and text boxes when they create parsing or reading problems.
- Follow the employer's file-type and application instructions.
- Remember that ATS products and employer configurations vary; no formatting or keyword tactic guarantees selection.
Resume skills mistakes to avoid
Copying every keyword from the job description
The employer's requirements are not evidence about you. Add only the skills you can support and explain.
Treating related tools as identical
Using one CRM, cloud platform, programming framework, or analytics tool may help you learn another, but it does not prove exact experience with it.
Listing only broad soft skills
A long list of communication, teamwork, leadership, and problem-solving claims offers little context. Demonstrate the strongest ones in bullets.
Using stars, bars, or percentages
A self-rating such as 90% Excel or four stars for leadership has no shared standard. Name the functions, tasks, or level of responsibility instead.
Hiding important skills in graphics
Keep essential text selectable and readable in a conventional section. Decorative charts, icons, and text boxes may create parsing or accessibility problems.
Claiming credentials or regulated abilities
Never list a license, certification, clinical procedure, security clearance, equipment authorization, or compliance responsibility unless it is accurate and current where required.
Final truth and relevance review
Resume skills checklist
- I compared the resume with one specific job description.
- Every listed skill is supported by work, education, training, volunteering, or project evidence.
- Related experience was not converted into an unsupported exact skill.
- Unconfirmed employer requirements were left out.
- The most relevant hard skills appear in a clear, conventional section.
- Important skills are reinforced with context in experience or project bullets.
- Soft skills are demonstrated rather than presented only as adjectives.
- Tool names, methods, credentials, and licenses are spelled accurately.
- I removed rating bars, stars, and arbitrary proficiency percentages.
- I avoided repeating a keyword only to increase frequency.
- The skills section is focused and does not replace evidence elsewhere.
- I can explain when, where, and how I used every skill during an interview.
References and further reading
These resources offer additional perspectives on selecting and demonstrating skills. Adapt all advice to your evidence, location, field, and the employer's instructions.
Indeed: Skills to Put on a Resume
Reviews skill selection, hard and soft skills, placement, and adaptable examples.
MIT CAPD: Writing About Skills
Explains how experience statements can demonstrate skills through context, action, and results.
Harvard: Creating a Strong Resume
Emphasizes relevant strengths and tailoring the resume to the type of position being pursued.
Frequently asked questions
What skills should I put on my resume?
Choose skills that are relevant to the target job and supported by your real work, education, training, volunteering, or projects. Prioritize specific tools, methods, procedures, languages, and domain capabilities, then demonstrate important interpersonal skills through context.
How many skills should I list on a resume?
There is no universal number that fits every candidate. Use a focused list that covers the strongest relevant capabilities without becoming a keyword dump. The available space, role, experience level, and number of genuinely supported skills should guide the final length.
What is the difference between hard and soft skills?
Hard skills are specific technical, procedural, language, tool, or domain capabilities. Soft skills describe how you communicate, collaborate, organize, adapt, think, or lead. Both can matter, but soft skills usually become more credible when demonstrated in an experience or project example.
Should I copy skills from the job description?
Use the employer's exact terminology only when it accurately matches your evidence. Do not add a requested skill, platform, credential, responsibility, or level merely because it appears in the job description.
Where should skills go on a resume?
A dedicated skills section can provide a quick inventory. Reinforce important skills in experience and project bullets, and include a small number in the summary when they are central to the target role. Relevant coursework and credentials can appear in education or certification sections.
Should I rate my skill level with stars or percentages?
Usually no. Stars, bars, and percentages are subjective and difficult to interpret. Describe the tool functions, type of work, context, responsibility, or output instead. Use an official proficiency framework only when it is relevant and accurately assessed.
Can I list skills learned through a course or personal project?
Yes. Identify the source honestly and show what you practiced or built. Do not present coursework, tutorials, or personal projects as paid professional experience, and do not imply mastery beyond what the evidence supports.
Do ATS tools require an exact keyword match?
Applicant tracking systems and employer workflows vary. Clear terminology can help a reader or system identify relevant information, but an exact phrase is not permission to make an unsupported claim. Use accurate job-relevant language naturally and follow the employer's application instructions.
Compare your supported skills with one target job
ResumeClimb Truth Match separates confirmed wording, related evidence, and requirements that were not found. Keep only the skills that accurately represent your background.
Open the Free ATS Resume Checker