Skills to put on a resume
Put the hard skills the job description explicitly names — tools, technologies, certifications, methods — using the posting's exact wording, plus two or three differentiators you can prove. List eight to twelve in a dedicated skills section and demonstrate the rest, including soft skills, inside quantified experience bullets.
How do you choose which skills to list?
Start from the job description, not from yourself. Extract every tool, method, and certification it mentions; that is the keyword set recruiters and ATS searches are built on (see how ATS screening works). Keep the ones true of you, in the employer's wording. Then add a small number of differentiators — adjacent skills that set you apart for this role. Everything else is cut or moved into bullets.
Hard skills examples by role
- Software engineer: Python, TypeScript, React, PostgreSQL, AWS, Docker, CI/CD, system design.
- Data analyst: SQL, Excel, Python (pandas), Tableau or Power BI, A/B testing, data modeling.
- Digital marketer: SEO, Google Ads, GA4, email automation, copywriting, funnel analysis.
- Registered nurse: patient assessment, IV therapy, EHR (Epic), medication administration, triage, BLS/ACLS.
- Project manager: Agile/Scrum, Jira, stakeholder management, budgeting, risk tracking, roadmapping.
- Accountant: GAAP, reconciliations, Tally or QuickBooks, financial reporting, GST/TDS (India), audit support.
Where do skills go on the resume?
Three placements, working together: a scannable skills section (the keyword anchor), woven into experience bullets as evidence ("built ETL pipelines in Python/Airflow"), and the two or three most role-defining ones in the summary. This redundancy is deliberate — sections get parsed, bullets get read.
Common skills-section mistakes
- Listing soft-skill adjectives ("motivated", "team player") instead of capabilities.
- Synonym drift — writing "JS" when the posting says "JavaScript"; literal matching matters.
- Skill bars, star ratings, icon clouds — unreadable to parsers, meaningless to recruiters.
- One static list for every application instead of re-tailoring per posting.
Frequently asked questions
How many skills should I list on a resume?
Eight to twelve in the skills section, all relevant to the target role. A longer list dilutes the strong signals and reads as padding. Skills beyond the section belong demonstrated inside experience bullets, not enumerated.
Should I include soft skills on a resume?
Sparingly, and shown rather than claimed. 'Leadership' as a list item is noise; 'led a 6-person team through a zero-downtime migration' is evidence. Reserve list space for hard skills the job description names; let bullets carry the soft skills.
What's the difference between hard and soft skills?
Hard skills are teachable, testable capabilities — Python, financial modeling, Figma, a nursing certification. Soft skills are working behaviors — communication, prioritization, teamwork. ATS keyword searches run almost entirely on hard skills, which is why they anchor the skills section.
Should I rate my skill levels (bars, percentages)?
No. Skill bars and percentages are graphics an ATS cannot read and recruiters cannot calibrate — '80% Python' has no agreed meaning. If proficiency matters, state it in words ('advanced', '5 years') or prove it with a bullet.