Skills to Put on a Resume in 2026 (With Examples)

The skills section is where resumes go generic: a row of Microsoft Office, communication and teamwork that matches every applicant and therefore none. Deciding which skills to put on a resume is a matching exercise, not a memory dump, and the matching is against one specific posting rather than your whole history. This guide covers the hard-soft split, the 8 to 12 rule, field-by-field lists and a full skills bank, plus what to cut and how to prove what stays.

Hard skills, soft skills, and which the section is for

Hard skills are verifiable: software, languages, methods, certifications, machinery. Soft skills are dispositions: communication, adaptability, judgment. The US Department of Labor's O*NET skills taxonomy catalogs both across every occupation it tracks, which makes it a useful sanity check when you are unsure what a field calls a thing. Employer surveys keep ranking the mix highly, too; WorldatWork's 2026 skills outlook puts AI literacy and data fluency beside adaptability and communication at the top of the want lists.

The section itself, though, is a hard-skills instrument. A recruiter scans it for tool and method matches in seconds, and software scans it for strings. Soft skills claimed there are unfalsifiable and universally claimed, which is why they convince nobody; the evidence for them lives in the experience bullets, where the section-by-section writing rules already demand numbers. The division of labor is clean: the list answers can you operate the tools, the bullets answer what happened when you did.

Mirror the posting, in its own words

Build the list from the job ad, not from your full inventory. The process is 3 highlighter passes: every tool and platform the posting names, every method and credential, and every phrase it repeats, because repetition is the employer scoring their own priorities. Keep what you honestly have, write it in the ad's exact phrasing, and drop the rest, because the software reading the file first matches strings, not synonyms. An AI gap-check speeds the collection, and writing a resume with AI covers the prompt that does it without inventing skills you lack.

When you lack a required skill

A posting's must-have you do not have gets one of two honest treatments. If you own its close neighbor, list the neighbor truthfully (Mixpanel rather than the requested Amplitude) and let the bullets show depth; screeners understand tool families, and adjacent fluency is a real answer. If you have nothing near it, the skills section stays silent and the cover letter or application question carries the plan: what you have used instead, and how fast you have picked up siblings before. What never works is listing the missing skill on faith, because it is the first thing the interview will reach for.

Reading the posting like a parser: a worked case

Here is the whole method on one compressed posting. The excerpt below is the kind of paragraph every job ad contains; the card after it is the skills section it produces.

Seven entries, every one a string from the ad, in the ad's priority order, each defensible in an interview. The budget figure and the monthly presenting do not go in the skills list; they go in the experience bullets as numbers, which is the split the whole page runs on. Run the same 2-step read on any posting and the section writes itself in under 10 minutes, which is the entire point: the employer already drafted your skills section, and your job is honest selection.

The 8 to 12 rule, and where skills actually go

The skills section

8 to 12 entries, ordered by the posting's priorities, hard skills only. Below 8 the section looks thin; past 12 it reads as a keyword dump and buries the matches that matter. One line each, no ratings bars, no percentages. Group only when the role genuinely spans domains, a technical cluster and a tooling cluster, and keep each group inside the same 8 to 12 total.

Skills inside the bullets

Soft skills convert to achievements: leadership becomes led a 6-person team through a system migration with zero downtime, and communication becomes presented monthly numbers to leadership for 2 years. Illinois' career center resume guidance teaches the same conversion: claims in the list, proof in the bullets.

Levels without lying

Qualify where honesty needs it: SQL (intermediate) or Spanish (conversational) beats an unqualified claim that an interview dismantles. Parenthetical qualifiers also parse cleanly, unlike ratings bars, so honesty costs nothing mechanically. A usable scale: basic means you have done it with help, intermediate means you do it alone routinely, advanced means others come to you. If a level would embarrass you live, the skill is not ready for the page; if you would bet a probation period on it, list it plain.

Skills by field: what earns a line in 2026

The lists below are starting inventories, not scripts: the posting in front of you always overrides them. Two patterns hold across fields, though. Named systems beat category words, so Epic beats EHR software and Salesforce beats CRM experience wherever the ad allows it. And version or spec matters when the ad includes it, because the string with the number is the one their search runs.

The skills bank, family by family

A broader inventory to prompt your own audit. Nothing below goes on a resume because it is listed here; a line is earned only when the posting cares and you can back it live.

Read it as a memory jogger with the posting beside it: most people under-claim tools they use weekly and over-claim traits they cannot evidence, and the bank is built to reverse both. The systems you administer, the reports you own and the processes you documented all count as skills, even when your job title never mentioned them.

Transferable skills for career changers

A changer's skills section leans on the overlap between fields: the tools and methods that travel. Budget ownership, stakeholder reporting, CRM fluency, scheduling at scale, training and onboarding, process documentation, vendor negotiation, data cleanup: every one of these exists in most industries, and each can carry a number from the old field into the new one. The move is to name them in the TARGET field's vocabulary, taken from the posting, then prove them with old-field figures in the bullets.

Same facts, translated shelf. The translation is legitimate exactly as long as the number behind it survives the move unchanged; the moment a figure grows in translation, it stops being a bridge and becomes a claim you will defend to someone who knows the target field better than you do.

AI skills in 2026: name the tool and the result

AI literacy has moved from novelty to expectation in a large share of postings, and it goes on the resume like any other hard skill: as a tool plus a use, never as the bare phrase AI skills. Prompt-drafting reports in Claude, automated ticket triage with Zendesk AI, built a GPT-based FAQ bot that deflected 1,200 tickets a year: each names a system and a result. The skill list carries the tool names the posting uses; the bullets carry what the tools produced.

The honesty bar stays where it always was. Having asked a chatbot questions is not a resume skill; having changed a workflow with one is. Lines that currently earn interviews look like: prompt-based reporting workflows (Claude, ChatGPT), AI-assisted ticket triage (Zendesk AI), transcript summarization pipelines, image-generation tooling for social content (with the brand's named stack), and AI QA review of outbound copy. Each names a system a hiring manager can picture in their own shop.

Skills for a first resume

With no roles to mine, the skills section leans on coursework, projects and tools: the lab techniques, software and languages from classes, the platforms behind a student org's newsletter, the point-of-sale system from a summer job. The same mirroring rule applies, since entry-level postings name concrete tools too, and the same proof rule applies: every listed skill should trace to a project or class you can talk about for 2 minutes. Padding with aspirational skills reads instantly at this level, because there is no history to hide behind. A short projects section directly under skills gives each claim its evidence one scroll later, which is the strongest structure a first resume has available.

The skills section at three career stages

Entry level: tools and coursework carry it, 8 entries is plenty, and a projects section underneath supplies the proof. The parenthetical qualifier does honest work here: Python (coursework + 2 projects) is a stronger claim than bare Python.

Mid-career: the full 8 to 12, mirrored per posting, with the generic early-career entries retired. This is the stage where the section works hardest, because searches and skims both run on it, and where pruning matters most, because a decade of tools accumulates faster than a page's patience.

Senior and management: the section shrinks toward systems-plus-scope: the platforms you still genuinely operate, plus the management machinery (budget ownership, forecasting, hiring). Listing hands-on tools you have not touched in 5 years invites the one interview question with no good answer, and the freed lines are worth more as one extra team-level achievement anyway.

A 15-minute skills audit, start to finish

The whole method compresses into one repeatable pass per application:

1. Paste the posting into a doc and highlight every named tool, method, credential and repeated phrase (3 minutes).
2. Strike the highlights you cannot honestly claim; what remains is the candidate list (2 minutes).
3. Order the survivors by the posting's own emphasis, first-mentioned and repeated items first (2 minutes).
4. Trim to 8 to 12, moving anything soft into a bullet with a number instead (3 minutes).
5. Add honest qualifiers where levels vary, and spell out certifications both ways (2 minutes).
6. Read the finished list as an interviewer: any line you would dread defending comes out (3 minutes).

Run it fresh for each application rather than editing the last version, because leftover skills from the previous posting are how orphan entries accumulate. The master resume keeps the full inventory; each sent copy carries only that ad's survivors, and after a dozen applications the audit itself drops to 10 minutes because the inventory stops surprising you.

Be ready to prove any line in 2 minutes

Every skills entry is a standing invitation to the question tell me about a time you used this, so the honest close of a skills audit is rehearsal, not writing. For each listed skill, have one 2-minute story with the same three beats as a good bullet: the situation's scale, what you did with the tool, what changed. A skill with a ready story survives any interviewer; a skill without one should either gather its story from your history or leave the page. This is also the practical difference between listing SQL after a weekend course and listing it after a year of weekly queries: the list line looks identical, and the 2 minutes do not.

What to cut

Three cuts cover most bloat. Implied skills: email, Word and internet research are assumed at every desk job, and typing speed retired from resumes a generation ago. Dead skills: software nobody has shipped on in a decade, unless the posting names it, in which case it is suddenly a differentiator. And orphan skills: anything real that this particular job will never use, the photography on an accounting application, which is inventory, not argument. A useful final test is to read the list as the interviewer will: every line is a question they may ask, so a line you would dread being asked about has already answered itself off the page. The freed lines go to the summary's proof numbers, where summaries by role and level show what earns the space; the skills the ad wants, the ranked and tested resume builders will happily suggest, but the honest pruning stays your job.