Resume skills guide

Why the skills section matters so much

Two reasons.

First, applicant tracking systems index your skills. When a recruiter searches for “React” or “stakeholder management” or “SQL”, the search queries the parsed text of every application. A skills section with the right words in plain text is the most reliable way to appear in that search.

Second, recruiters skim skills sections first. A busy recruiter evaluating your resume might spend fifteen seconds on the top third and then scan section headings. A well-grouped skills section gives them something specific to remember about you in that scan.

Hard skills vs soft skills

The distinction is useful but not absolute. In practice:

• Hard skills are specific, teachable capabilities that can be verified — programming languages, software, tools, methodologies, certifications. These are what the ATS searches for.
• Soft skills are behavioural capabilities that are demonstrated through work — communication, leadership, collaboration, problem-solving, adaptability. These are almost never searched for by keyword because they are too generic.

Both belong on your resume, but they belong in different places. Hard skills belong in a dedicated skills section where they can be scanned and parsed. Soft skills belong inside your experience bullets, where they are demonstrated rather than claimed.

The weak version claims soft skills nobody can verify. The strong version lists hard skills grouped by category, plus one or two practices that are specific to the field. A recruiter reading the strong version knows in five seconds what technology stack the candidate works in.

Grouping is the whole trick

A flat list of thirty skills is unreadable. The same thirty skills grouped into five categories of six is easy to scan and easy to parse. Grouping also lets the reader evaluate you at the right level: they can see that Python is under “Languages” and Postgres is under “Data”, which tells them you understand the difference.

Groups that work well by discipline:

Software engineering

• Languages
• Frameworks and libraries
• Data stores
• Infrastructure and tooling
• Practices

Product and design

• Design tools
• Research methods
• Technical skills
• Craft practices

Marketing

• Channels
• Analytics tools
• Content formats
• CRM and automation

Finance and business

• Analysis and modelling
• Software
• Reporting and standards
• Regulatory knowledge

Academic and research

• Methods
• Analysis tools
• Laboratory techniques
• Programming and statistics

What level to claim

Level labels (Expert, Advanced, Intermediate, Beginner) are useful when used honestly and harmful when inflated. Here is a simple test:

• Expert: you can teach this to a colleague, you know its failure modes and you have fixed them in production or equivalent real-world conditions.
• Advanced: you use it regularly without help and can solve unusual problems with it.
• Intermediate: you can use it for standard tasks and find documentation for the rest.
• Beginner: you have used it, but not enough to be productive without close reference.

The best test is the interview: can you talk about a real project using this skill for two or three minutes? If yes, the label is probably right. If no, downgrade it.

Many Advoke CV templates do not display levels at all. That is deliberate — a clean list of skills, honestly grouped, is usually more persuasive than a list of levels that invites scrutiny.

Match the job advert's vocabulary

This is the single highest-value change you can make to your skills section. Read the job advert carefully and note the exact words it uses. Then use the same words in your skills list for the things you genuinely have.

Common cases where this matters:

• Stakeholder management vs “working with stakeholders” vs “client communication”. Pick the advert's phrase.
• Product management vs “product owner” vs “product lead”. These mean slightly different things in different companies; use the advert's wording.
• JavaScript vs “JS”. Write out the full name.
• Postgres vs “PostgreSQL”. Use the full name — the ATS may not recognise the abbreviation.
• CI/CD vs “continuous integration” vs “continuous delivery”. Include the phrase the advert uses.
• Machine learning vs “ML” vs “deep learning”. Be specific.

Do not change what you claim — change the words you use to describe it. If you have managed stakeholders in a real project, and the advert says “stakeholder management”, write “stakeholder management”. You are not lying; you are matching vocabulary.

How many skills to list

Between twelve and twenty-five, grouped into three to five categories. Fewer than twelve looks thin; more than thirty looks padded and makes the section unreadable.

Prioritise in this order:

1. Skills named in the job advert that you genuinely have.
2. Skills that are core to the role.
3. Skills that differentiate you from other applicants.
4. Skills that demonstrate breadth, if you have room.

Where to put the skills section

For most roles, the skills section goes after experience and before education. Three exceptions:

• Technical roles: move skills above experience. Hiring managers want to verify the stack before reading the story.
• Students and graduates: skills can go above experience if the skills are strong and the experience is thin.
• Career changers: consider a “Relevant skills” block near the top that pulls forward the skills from your old career that transfer to the new one.

Skills that should not appear on a resume

Every one of these appears on thousands of resumes and helps nobody:

• Microsoft Word, Excel or PowerPoint. Expected in any office role; if you have advanced Excel (VLOOKUP, pivot tables, macros), say so specifically.
• Email. Everyone can use email.
• “Typing” or “data entry” unless the role is literally about that.
• “Team player”, “hard worker”, “detail-oriented” and other unverifiable soft-skill cliches.
• Operating systems you “know”. Everyone knows Windows and macOS.
• Social media as a skill unless your role is social media.
• Any skill you cannot talk about in an interview.

Special case: languages

Spoken languages belong in their own section, not in the skills section. Use the CEFR scale (A1–C2) if you want to be precise, or use the common labels: Native, Fluent, Advanced, Intermediate, Basic.

For most roles in most countries, list only languages you can conduct a business conversation in. If you studied Spanish for two years in school and cannot hold a conversation, leave it off. Being asked to demonstrate a language in an interview is a common outcome of listing it.

The bottom line

Your skills section is your keyword surface for ATS searches and your quickest signal to a human reader. Group it, keep it honest, match the advert's vocabulary and cut everything you cannot be interviewed on. That is the entire job.