What Skills to Put on a Resume (Hard vs Soft Skills)
· 5 min read
Put 8–12 specific, job-relevant hard skills in your skills section (tools, technologies, languages, and certifications the posting actually asks for) and prove your soft skills through accomplishment bullets instead of listing them. The skills section exists to pass keyword screening and give recruiters a fast capability snapshot, so every entry should be concrete, verifiable, and matched to the job.
What's the difference between hard and soft skills?
Hard skills are teachable, measurable abilities: software, programming languages, spoken languages, certifications, methodologies. You either can build a pivot table or you can't. Soft skills are interpersonal and behavioral: communication, leadership, adaptability, problem-solving. Both matter to employers, but they belong in different places on your resume.
| Hard skills | Soft skills | |
|---|---|---|
| Examples | SQL, Figma, Spanish, CPA, forklift certification | Leadership, communication, teamwork |
| Verifiable? | Yes: tests, certificates, work samples | Only through evidence and stories |
| Where they go | Skills section (and bullets) | Accomplishment bullets, summary |
| Screened by software? | Yes, as keywords | Rarely |
The single biggest skills-section mistake is filling it with soft skills. "Team player · Detail-oriented · Hard-working" tells a recruiter nothing, because everyone claims them and nothing on the list can be checked.
How do I match skills to the job posting?
Start from the posting, not from memory. Highlight every skill, tool, and qualification it mentions, then list the ones you genuinely have, using the posting's exact wording. If the job says "spreadsheet modeling in Excel," write "Excel (financial modeling)," not "office software." Applicant tracking systems and skimming recruiters both search for the posting's terms, so mirroring the language matters; our guide to tailoring your resume to a job description walks through the full process.
Two practical rules:
- Order by relevance, not alphabet. Put the posting's must-haves first, where a 7.4-second skim will catch them; that's the average length of a recruiter's first look, per The Ladders' 2018 eye-tracking study.
- Re-rank for every application. Your skill list is real; its ordering is marketing.
How many skills should I list?
Aim for 8 to 12. Fewer than six looks thin; more than fifteen reads as padding and dilutes the ones that matter. If you're tempted to list twenty, you're listing things you've merely touched. Cut to the ones you could discuss comfortably in an interview.
Career offices consistently push the same principle: relevance over volume. MIT's Career Advising & Professional Development resume guidance emphasizes selecting content for the specific audience, and Stanford Career Education frames the resume as a targeted marketing document, not an inventory.
How should I group my skills?
Grouping turns a wall of commas into something scannable. Three to four labeled lines work for almost every field:
Languages & frameworks: Python, TypeScript, React, SQL Tools & platforms: Git, Docker, AWS, Jira Domain: A/B testing, REST API design, data pipelines Languages: English (native), German (B2)
The category labels do double duty: they help recruiters navigate, and they show you understand how your field organizes its skills. Common groupings by category type:
- Languages / Tools / Domain (engineering and data roles)
- Technical / Certifications / Languages (healthcare, trades, finance)
- Software / Marketing channels / Analytics (marketing roles)
Keep the section compact. The skills list is there to support your experience section, not replace it. For where the section belongs on the page, see our guide to resume sections.
How do I show soft skills without listing them?
You prove them. A soft skill on a list is a claim; a soft skill inside an accomplishment is evidence. Take the skill you want to convey and write the bullet that demonstrates it:
Claim: Leadership Evidence: Led a 5-person support team through a ticketing-system migration; kept response times under SLA throughout and trained the team on the new workflow in two weeks.
Claim: Communication Evidence: Wrote the onboarding guide now used by all 40 new hires; cut time-to-first-contribution from three weeks to one.
Claim: Problem-solving Evidence: Diagnosed a recurring billing error affecting 200+ accounts; documented the root cause and worked with engineering to eliminate it.
If a posting explicitly names a soft skill ("strong cross-functional communication"), echo the phrase once in your summary or a bullet, then back it with a result. Our guides to resume bullet points and resume action verbs cover the mechanics.
Should I rate my skill levels?
Usually not. Skill bars, star ratings, and percentages ("JavaScript — 80%") hurt more than they help: the scale is meaningless (80% of what?), the graphics confuse applicant tracking systems, and a self-assigned "60%" just invites doubt.
Proficiency labels help in exactly two cases:
- Spoken languages, where standardized levels exist and matter: "French (fluent)," "Japanese (JLPT N2)," "Spanish (conversational)."
- A genuine expert/working split the job cares about: "Expert: Python, SQL · Working knowledge: R, Scala" is honest tiering that sets interview expectations correctly.
Everything else: list the skill plainly and let your experience bullets establish depth. And never list a skill you'd fail a basic interview question on; skills sections are treated as fair game for technical screens.
Which skills do recruiters ignore?
Some entries actively cheapen the list around them. Cut these:
- Baseline computer literacy: "Microsoft Word," "email," "internet research," "typing," "Windows"
- Job-description restatements: "customer service" on a customer service resume (show it in bullets instead)
- Personality adjectives: "hard-working," "motivated," "passionate," "detail-oriented"
- Obsolete or irrelevant tech that dates you without helping you
- Hobbies disguised as skills, unless genuinely relevant to the role
The test for every entry: would a recruiter for this specific job search for this term? If not, it's taking up space that a real keyword could use. This overlaps heavily with the classic blunders in our common resume mistakes guide.
Example skills sections by industry
Software engineering: Python, TypeScript, React, PostgreSQL, AWS, Docker, CI/CD, REST APIs
Marketing: SEO/SEM, Google Analytics 4, HubSpot, email automation, paid social (Meta, LinkedIn), copywriting, A/B testing
Nursing / healthcare: RN license (state), BLS/ACLS certified, Epic EHR, IV therapy, patient triage, medication administration
Finance / accounting: Financial modeling, Excel (advanced), QuickBooks, GAAP, variance analysis, SQL, CPA (in progress)
Administrative: Calendar and travel management, Google Workspace, expense reporting, event coordination, CRM data entry (Salesforce)
Each list is short, concrete, and searchable; that's exactly what both the software screen and the human skim reward. If you're unsure whether your formatting will survive automated screening, run through is my resume ATS-friendly? before you apply.
Build your resume the easy way
cvbyte is a free resume builder that runs entirely in your browser: no sign-up, no upload, and your data never leaves your device. Pick from ten ATS-friendly templates, see your resume typeset live as you type, and download a crisp PDF in one click. Start building your resume now. It takes about ten minutes.