Two readers, two speeds

Your skills section gets read twice, by two different kinds of readers, at two very different speeds. A search or filtering step (human-run or automated) scans it in a fraction of a second, looking for specific matching terms. A hiring manager who's already interested reads it more slowly, sizing up not just whether the skills are present but whether the list feels credible and relevant. A skills section built only for the fast pass looks like keyword soup to the second reader. One built only for the slow pass might bury the specific terms the fast pass is searching for. This guide builds one that works for both.

Step 1: Pull the raw list from your actual experience

Before organizing anything, write down every skill, tool, technique, and area of knowledge you've genuinely used in a professional context, without filtering yet. Go role by role through your work history and ask, for each one: what tools did I use daily? What processes did I follow? What did I get specifically good at that a coworker without my experience wouldn't have? Don't worry about length or relevance yet — overproduce first.

Step 2: Cut anything you can't discuss for two minutes

Go back through your raw list and remove anything you couldn't comfortably talk through if an interviewer asked a follow-up question about it. This is the most important filtering step and the one people skip most often under pressure to look more qualified. A skills section is a set of claims, and every claim on it should be one you can defend in real time, in a live conversation, without hedging.

Step 3: Match against the specific job posting

For whichever job you're actually applying to, go through the posting and note which of your remaining skills show up in it — matched or nearly matched in wording — and which posting-listed skills you have that you hadn't thought to list. This is where your skills section gets tailored per application rather than staying static.

If you're not sure how to phrase a skill you know you have but keep describing awkwardly, browsing Craftume's Skills Library by role or category is a fast way to find the standard, recognizable term for something you've been circling around in your own words.

Step 4: Group by category, not one flat list

A wall of twenty-five comma-separated skills is hard to scan quickly, whether the reader is software doing a keyword search or a person skimming visually. Group into two or three clear categories relevant to your field, for example:

  • Technical/Tools: the software, platforms, or systems you use directly
  • Core Competencies: processes and methods you're skilled in (e.g., "Budget Forecasting," "Inventory Management," "Curriculum Design")
  • Certifications/Credentials: anything formally earned, listed separately so it's easy to spot

Not every field needs all three categories — a skilled trade might split into "Certifications" and "Equipment/Systems"; an office role might split into "Software" and "Process/Operations." Pick categories that reflect how your own field actually talks about skills.

Step 5: Order by relevance, not alphabetically

Within each category, lead with the skills most relevant to the specific job you're applying for, not alphabetical order (which is neutral but wastes your most valuable real estate — the first item a reader's eye lands on — on whatever starts with "A"). A fast skim disproportionately weighs whatever's first; put your strongest match there on purpose.

Step 6: Be careful with soft skills

Skills like "communication," "teamwork," and "leadership" aren't wrong to include, but a skills section made up mostly of them is weak, because they're unverifiable claims with nothing attached. If you want to include a soft skill, either pair it with something concrete elsewhere on the resume that demonstrates it (a bullet point showing leadership in action, for instance) or keep the skills section itself focused mostly on hard, checkable skills, and let soft skills show up implicitly through your achievement bullets instead.

Step 7: Cut outdated or over-obvious entries

Two categories are safe to remove in most cases: technology or tools that are genuinely obsolete in your field (a version of software several generations old, unless the posting specifically asks for legacy system experience), and skills so universally assumed for the role that listing them adds nothing ("basic computer skills" for an office job, "customer service" for a retail role where it's inherent to the job itself). Space in a skills section is limited — spend it on what differentiates you, not what's assumed of anyone in the role.

Step 8: Cross-check against your bullet points

Your skills section and your experience bullets should reinforce each other, not exist in isolation. If you list "Data Analysis" as a skill, at least one bullet point somewhere on the resume should show that skill in action with a specific example — otherwise the listed skill reads as a bare claim with no supporting evidence anywhere else on the page. If you have a strong skill demonstrated nowhere in your bullets, that's a sign to either add a bullet about it or reconsider listing it prominently.

A finished example

For a marketing coordinator applying to a demand-generation-focused role:

Technical/Tools: HubSpot, Google Analytics, Meta Ads Manager, Canva Core Competencies: Email Campaign Management, A/B Testing, Lead Scoring, Content Calendar Planning Certifications: HubSpot Inbound Marketing Certified

Compare that to a flat, unsorted line — "Marketing, Social Media, Communication, Team Player, HubSpot, Analytics, Creative, Hardworking, Canva, Email" — and the difference in how fast and how credibly each one reads is immediate.

FAQ

How many skills should be on a resume? Somewhere around 8–15 total across all categories is a reasonable range for most resumes — enough to cover real breadth without diluting into an unfocused list.

Should I list a skill I'm still learning but not yet proficient in? Only with an honest qualifier if you include it at all (e.g., under a separate "Currently Learning" note, or left off the main list entirely) — listing it flatly alongside skills you're fully proficient in overstates it.

Do skill proficiency levels (like star ratings or bars) help or hurt? They're subjective and unverifiable, and on some resume formats they can render as an image rather than text (a parsing risk covered in the companion formatting guide) — a plain text list is usually the safer, more credible choice.

Should technical and soft skills be mixed together in one list? Better to separate them if you include both, since they serve different purposes and reading them mixed together makes the section harder to scan for either kind of information.

How often should I update my skills section? Any time you apply to a meaningfully different type of role, and at least once every six months to a year even if you're not actively job hunting, so it doesn't quietly go stale.