What to Put in the Skills Section of a Resume (and What to Cut)

A resume skills section should list the tools, methods and languages you can use now, grouped so a reader finds them in a few seconds, with each one backed by something in your experience. Eight to fifteen well chosen items beat forty. Skip adjectives about yourself and anything you could not discuss for five minutes. The section is a map to the evidence elsewhere on the page, not a place to hold evidence of its own.

This matters more than it seems. A skills list is the part of a resume that is easiest to inflate, so readers trust it least unless the rest of the page confirms it.

What belongs in it

Include skills that satisfy three tests:

1. The job needs them. Check the posting and keep the ones that match.
2. You use them, or have used them recently enough to work without relearning.
3. They appear somewhere else on the resume, in a bullet, a project or a qualification.

Typical content by role family:

Group, don't dump

A flat list of 30 words is hard to scan. Groups let a reader find what they need.

• Languages: Python, SQL, JavaScript
• Data tools: dbt, Airflow, Tableau
• Cloud: AWS (S3, Lambda, Redshift)

A line like this is checkable, since each item can be tied to a bullet. Naming the specific parts of a larger platform, as in the AWS line above, is more credible than the platform name alone.

Levels: use them with care

Rating bars and stars invite questions. What is four out of five in Excel? Rather than a rating, add a short qualifier where it helps: "Python (daily, 5 years)" or "German (conversational)". For languages, use a standard scale such as CEFR, for example B2, if the employer would know it.

Soft skills

"Excellent communicator" is a claim, not a skill, and everyone makes it. Show it through evidence: "Ran weekly client reviews for 14 accounts" shows communication, and "Trained six new hires" shows teaching. If you must list a soft skill, tie it to an activity. This applies to the summary as well; see resume summary examples.

What to cut

• Skills so basic for your field that listing them looks naive, such as email or typing for most office roles.
• Tools you used once, long ago.
• Skills with no evidence anywhere else.
• Obsolete tools that make your resume look dated, unless the job needs them.
• Anything you would not want an interviewer to ask about.

Matching the posting without stuffing

Where the posting uses a specific term for something you do, use that term once if it is accurate. If the posting says "stakeholder management" and your resume says "managed relationships with directors", it is fine to use their phrase in a bullet. Do not paste the posting's entire list into a hidden block of white text. Screening tools that read for meaning will not credit it, and readers who spot it will not trust the rest. See resume keywords in 2026 and ATS-friendly resumes for what still matters.

Example: before and after

Before: "Skills: communication, leadership, teamwork, Microsoft Office, problem solving, time management, hard-working, detail-oriented, fast learner."

After: "Tools: Excel (pivot tables, Power Query), Power BI, SQL (reporting queries). Methods: month-end close, variance analysis, budgeting. Systems: NetSuite, Sage."

The second version is shorter, specific and checkable, and each item can be backed by a bullet in the experience section. For the bullets, see resume bullet points.

How the section changes with seniority

Early career: the skills section carries more weight because experience is thin. List tools and methods you used in projects and internships, and tie each to a project in the body.

Mid-career: keep it short and focused on tools and methods the role needs. Your experience now provides most of the evidence.

Senior: lead with a short line of areas of expertise, such as "financial planning, controls, team leadership", then a line of systems. The depth shows in the experience section, so the skills block should not repeat it.

A ten minute check against the posting

1. Highlight every skill and tool the posting names.
2. Mark the ones you can claim accurately.
3. Make sure each marked item appears in your skills section or a bullet, using accurate wording.
4. For any main requirement you do not have, decide whether you have a close equivalent. If so, name it plainly: "Used Looker for dashboards; moving to Power BI".
5. Delete listed skills that the posting does not need and that carry no evidence.

This keeps the section honest and matched to the job, and it takes the sort of effort that targeting a resume calls for.

Skills for people changing field

If you are moving into a new field, you will have two kinds of skills: ones that transfer and ones you are still building. List both, and be plain about which is which. A line such as "Working knowledge: SQL (courses and two projects)" is credible and gives a reader something to ask about. Pairing it with "Strong: project planning, stakeholder reporting" shows where the strength lies. See career change resumes.