How to list skills on a resume.

1. Hard skills vs soft skills

A hard skill is a specific ability you can be tested on: "Python", "photoshop", "SQL", "financial modelling", "Spanish", "forklift operation", "grant writing". You either can do these or you can't, and a manager can verify them in an interview, a test, or a work sample.

A soft skill is a behaviour: "communication", "teamwork", "leadership", "adaptability". These are real and important, but they cannot be meaningfully listed, because everyone claims them. Nobody writes "poor communication skills" on a resume.

List hard skills. Demonstrate soft skills through evidence.

2. Which skills to include

The skills section should contain the tools, technologies, languages, methods, and specific capabilities that are:

• Relevant to the job you're applying for.
• Genuine — you can actually use them.
• Distinct — they add information beyond your job titles.

Read the job description and pull out the specific technical requirements. If a posting names "Tableau", "R", and "A/B testing", and you genuinely have experience with those, they should appear in your skills section. If you don't, don't add them.

For a general professional, an example skills section might be:

Tools & software: Excel (advanced), SQL, Tableau, Salesforce, Slack
Methods: A/B testing, cohort analysis, user interviews
Languages: English (native), French (professional working proficiency)

3. Order matters

List your strongest, most job-relevant skills first. Not alphabetically. A reader scanning your skills section spends about two seconds on it — the first three items will actually be read, the rest will be skimmed.

If a job requires SQL and you're strong in it, SQL should be first. If a job requires Python but you're more comfortable with JavaScript, Python should be listed (because it's required) but not first (because it's not your strongest). Order isn't about honesty — it's about relevance and strength.

4. Group skills by type

A single comma-separated list is hard to scan. Grouping makes the section readable:

Languages: JavaScript, TypeScript, Python
Frameworks & libraries: React, Express, Django
Tools: Git, Docker, VS Code, Postman
Databases: PostgreSQL, MongoDB

Grouping also helps a hiring manager match your skills to the job description faster. If they need a Python developer and see the "Languages" line, they can find "Python" in one glance.

Don't overdo it — three to five groups is usually enough. More groups than that and the section becomes longer than your experience section.

5. Honesty rule

A skill on your resume is a claim that you can perform the task. If you list "SQL" and an interviewer asks you to write a simple join, you need to be able to do it. If you can't, you've lost credibility on every other line of your resume.

This doesn't mean you can only list things you're expert in. It means you should distinguish between levels. Options for honesty:

• Only list what you're confident in — clean but limits you.
• Use qualifiers — "familiar with X", "working knowledge of Y", "advanced in Z".
• Show recent learning — if you've just learned something, mention it in a project description rather than in the main skills list.

A "familiar with" item that appears in a project bullet is more credible than the same word appearing alone in a skills list.

6. Where soft skills belong

Soft skills are real. But listing them next to "Python" and "SQL" doesn't add credibility. Instead, demonstrate them through evidence in your bullets:

• Communication → "Presented quarterly results to a non-technical leadership team of 12."
• Leadership → "Mentored two junior developers through their first production releases."
• Adaptability → "Picked up the team's TypeScript codebase in three weeks and shipped a feature in week four."
• Problem-solving → "Diagnosed and fixed a race condition affecting 0.8% of orders."

Each of these bullets communicates the soft skill much better than the word itself would. If you want to reference "communication skills" on your resume, put the evidence in a bullet and remove the word.

7. Final checklist

• Does every listed skill actually belong to you?
• Are the skills grouped by type or ordered by relevance?
• Have you matched at least the five most important skills to the job description?
• Have you removed "team player", "detail-oriented", "hard working", and similar?
• Can you defend any skill on the list if asked in an interview?