What Skills to Put on a Resume

By Aaron Cao · Updated

What Skills to Put on a Resume
Put the skills the job description asks for that you genuinely have: a core of hard skills, tools, languages, methods, certifications, plus two or three soft skills you can prove with a story. Tailor the list for each application and cut filler like hard worker.

Put the skills the job description asks for that you genuinely have: a core of hard skills, tools, languages, methods, certifications, plus two or three soft skills you can prove with a story. Tailor the list for each application and cut filler like hard worker.

How do you choose which skills to list?

Staring at an empty skills section, it is tempting to list everything you have ever touched, and that instinct is exactly backwards. This section gives you a selection method that produces a short list recruiters actually scan for. The method starts outside your resume entirely.

Open the job description and pull out every named skill: tools, languages, methods, certifications. Mark the ones you genuinely have, and use the posting's exact wording for those, since recruiters and applicant tracking systems both search for the terms the posting used. That matched set is the spine of your section. Then add two or three skills the posting did not name but the role obviously rewards, which is where you show judgment rather than keyword matching.

Repeat this per application. A tailored list of 10 to 12 beats a fixed list of 30 every time, and the free resume builder keeps the section structured so swapping skills per application takes minutes.

Which hard skills belong on a resume?

Hard skills are the named, testable ones, and they do most of the section's work. What that means by field:

  • Software engineering: languages, frameworks, cloud platforms, databases, testing and CI tooling.
  • Data roles: SQL, Python or R, a BI tool, experimentation methods, pipeline or warehouse tooling.
  • Marketing: analytics platforms, paid channels, SEO tooling, email and automation platforms, copy testing.
  • Operations and admin: ERP or CRM systems, scheduling and procurement tools, process documentation.
  • Healthcare: EHR systems, clinical procedures within your scope, compliance frameworks, certifications.

Certifications and licenses count as hard skills and often matter more than tools, since they are verifiable at a glance. Order the list by relevance to the posting, not by how proud you are of each item; the reader gives the section a few seconds at most.

Which soft skills are worth listing?

Soft skills have a credibility problem: anyone can type communication, so the word alone proves nothing. The test for listing one is whether a bullet somewhere in your experience section backs it up. Stakeholder communication earns its place when a bullet shows you presenting analysis to leadership; prioritization earns its place when a bullet shows you cutting scope to hit a date.

Two or three proven soft skills beat a row of clichés. Aaron Cao, the founder of SubcueAI, made this pairing explicit in the resume builder's design: the skills section sits beside your experience bullets rather than in isolation, precisely because a claimed skill with no supporting bullet reads as filler to an experienced reviewer.

Skip the self-descriptions that cannot be proven on paper at all: hard worker, team player, detail-oriented, fast learner. They spend space and add zero signal.

What skills should you leave off?

Cutting is where the section gets its power. Leave off baseline office skills that the role assumes, email, web browsing, basic word processing, unless a posting explicitly names them. Leave off tools you touched once and could not discuss for two minutes. Leave off anything dated enough to invite doubt rather than interest, and anything irrelevant to the posting in front of you.

The interview is the enforcement mechanism: everything you list is an invitation for a question, and one wobbly answer about a listed skill damages the credible rest of the list. A useful final pass is to imagine being asked about each item and cutting the ones you would rather not be asked about.

How to present whatever survives, section placement, grouping, and formatting, is covered across the resumes and CVs hub, along with how your finished resume feeds SubcueAI's live interview assistant.

FAQ

How many skills should you put on a resume?

10 to 12 is a strong target for most roles. Enough to cover the posting's requirements plus a few judgment picks, short enough that every item is deliberate and defensible in an interview.

Should skills match the job description word for word?

For skills you genuinely have, yes, use the posting's exact wording. Recruiters and applicant tracking systems search for those terms. Never add a skill you lack just because the posting names it; the interview exposes that immediately.

Do you need a skills section if your bullets already show skills?

Yes, keep both. The section is the scannable index a recruiter reads in seconds, and the bullets are the proof. They do different jobs, and the pairing is what makes each skill credible.

Should you put soft skills on a resume at all?

List two or three that your experience bullets can prove, like stakeholder communication backed by a presentation bullet. Skip unprovable self-descriptions like hard worker or team player; they read as filler.

Related questions

← More on Resumes & CVs