How to List Skills on a Resume Recruiters Take Seriously

← All career resources

A skills section is one of the easiest parts of a resume to get right, and also one of the most commonly wasted. Vague entries like 'communication' or 'teamwork' add nothing a recruiter can actually verify or act on. Specific, provable skills do real work — both for ATS scanning and for the human being reading the resume afterwards. Think of the section as a quick-reference index rather than a personality profile — its job is to let a busy reader confirm, in a glance, that you have the tools the role requires.

The two kinds of skills worth listing

• Hard skills: tools, software, languages, certifications, technical methods — SQL, SAP, PMP, Mandarin fluency
• Domain skills: things specific to your function — financial modelling, campaign management, contract negotiation

What to leave out

Soft skills belong in your bullet points, demonstrated through concrete results, not listed as standalone unverifiable claims. 'Strong leadership skills' as a bullet point proves nothing on its own; 'led a team of 12 across two markets' proves the same underlying point with actual evidence attached. If a skill isn't something you could speak to confidently and specifically in an interview, it probably shouldn't be on the list at all. A quick self-test: for every skill you're tempted to list, imagine an interviewer asking 'tell me about a time you used that' — if nothing concrete comes to mind immediately, leave it off.

How to organise the section

Group skills logically — technical tools, methodologies, languages — rather than presenting them as one long, unstructured list that's hard to scan quickly. Order them by relevance to the specific role you're applying for, putting the skills named directly in the job posting near the top where they'll be seen first. Aim for 8 to 12 skills total; beyond that, the section starts to look padded rather than genuinely curated.

If you're applying to multiple, meaningfully different roles, it's worth maintaining two or three versions of your skills section rather than one master list you never adjust. A candidate applying to both a data analyst role and a project management role, for instance, should reorder and even swap out entries between the two versions so each one leads with what that specific employer actually cares about.

Proficiency levels are usually unnecessary

Star ratings or percentage bars next to each skill look precise but rarely mean anything consistent to a reader, since '80% proficient in Excel' has no shared definition across candidates. If a skill genuinely needs a proficiency qualifier, use plain language instead — 'conversational Mandarin' or 'advanced Excel, including pivot tables and macros' communicates more than a bar chart ever will.

A skills section should read like evidence, not like a word cloud generated from every job you've ever wanted.

The practical takeaway

Every skill you list should meet two tests: you can prove it with a concrete example, and it's genuinely relevant to the role you want next. Cut anything that fails either test, and use the space you free up for skills the job posting specifically asked for by name.