What are skills to put on a resume? A plain answer with the exceptions
Skills to put on a resume are the ones a job posting asks for that you can prove with a specific example: job-specific abilities, named tools, certifications, and a few working strengths. Put the posting's top matches first and leave off anything you could not explain in an interview. Career changes, licensed jobs, and thin work histories call for small adjustments to that rule.
By I start Monday team · Published November 1, 2026 · 6 min read
Put a skill on your resume when the job posting asks for it and you can point to a specific time you used it, whether at work, in school, or as a volunteer. For most people, that means job-specific abilities, named tools, certifications, and a few working strengths the posting calls out. Rule of thumb: if you could give a concrete example in an interview the moment someone asked, list it; if you couldn't, leave it off.
Exceptions that change what you list
Soft skills need different handling. A bare "team player" or "strong communicator" gives a recruiter nothing to check, so show those traits in your experience section, attached to something you did. For example: "Explained billing changes to upset customers by phone, then wrote the call script my team adopted." Keep a soft skill in the skills list only when the posting names it and a bullet backs it up. Our guide to resume bullet points that get read shows how to write that proof.
If a job calls for a license or certification, give it its own line near the top of the resume, with the exact credential name and its current status. To confirm what the job requires, check the posting and, for licensed work, the licensing body itself.
Career changers and people returning after time away face a narrower version of the same problem: their proof exists, but it sits in a different context. If you are moving fields, use the new field's words wherever they honestly describe your work, as covered in writing a CV for a career change. If you have been out of work, list skills you kept current through courses, volunteering, or freelance projects, and explain the employment gap separately. The table below gives the quick call for each common situation.
| Situation | What to do |
|---|---|
| Changing careers | Lead with skills both fields share, worded in the new field's terms. |
| Long career in one industry | Replace internal jargon and retired systems with terms current postings use. |
| Little paid experience | Draw proof from coursework, projects, volunteering, and part-time jobs. |
| Posting names a skill you lack | Leave it off and show the closest related skill you can prove. |
| Still learning a skill | List it with your honest level and where you are learning it. |
Why the proof test works
A skills list is a set of claims, and a hiring process may test them: a recruiter may compare them to the posting, and an interviewer may ask what you did with them. Our practical judgment is that a skill you cannot back up when asked is better left off.
The posting matters because it tells you what this employer wants for this job. Write a skill the way the posting writes it when that wording is accurate. Keep the section in plain text using these ATS-friendly formatting basics. When a posting is thin on detail, look up the occupation in O*NET OnLine, or look for its profile in the Occupational Outlook Handbook from the Bureau of Labor Statistics.
CHECK YOUR MATCH
Pick the 5 skills the posting lists first or repeats most. Count how many you can back with a specific task or result from your last 3 roles, adding courses and projects if you have fewer roles. Divide that count by 5. At 3 of 5 (0.6) or higher, apply and lead your skills section with those matches. At 2 of 5 (0.4) or lower, look for a closer role or build a missing skill first. These cutoffs are a practical judgment for your own planning, and a skill the posting marks as required can rule a job out whatever the score.
Worked example: support rep to customer success
This candidate and posting are made up to show the method. A support representative is applying for a customer success coordinator job. The posting's 5 core skills are Salesforce, customer onboarding, renewal tracking, written communication, and Excel reporting. Checking their last 3 roles gives this result:
- Salesforce: logged and escalated customer cases in it every day. Proven.
- Customer onboarding: ran setup calls for new business customers. Proven.
- Written communication: wrote help articles from recurring customer questions. Proven.
- Excel reporting: built a weekly report on ticket volume. Proven.
- Renewal tracking: never owned it. Unproven.
In this made-up example, that is 4 of 5, or 0.8, which clears the 3-of-5 cutoff above, a practical judgment for planning rather than a sourced standard. The skills line reads: "Salesforce, customer onboarding, Excel reporting, help center writing." Renewal tracking stays off, because the candidate could not describe doing it. The closest honest proof goes in a bullet: "Flagged accounts at risk of canceling and passed them to the account manager with notes from recent tickets."
This example only shows the method. Another posting may have a different top 5, so redo the count and reorder the list for each application. Tailoring your resume to the job description walks through the rest of that edit.
Try it
Use your skill count on your next application. Start on I start Monday
Frequently asked questions
How many skills should I put on a resume?
As a practical judgment rather than a sourced rule, aim for six to ten entries, so the list stays short and each entry can still have proof behind it. Put the posting's top matches first, and cut anything you would struggle to discuss in an interview.
Should I have a separate skills section on my resume?
As a practical judgment rather than a sourced rule, a short labeled skills section is usually worth having, because it lets a reader confirm your match quickly. Place it near the top when you are changing careers or your job titles hide your abilities. Place it after your experience when your recent titles already show the fit. Either way, your bullets should back it up.
Should I list common software like Microsoft Word or email?
As a practical judgment, leave basic tools off unless the posting names them. Name the specific programs a job relies on, such as Excel or Salesforce, and state your level if it helps. Advanced functions deserve a mention when the role needs them, for example pivot tables for reporting work.
More on Resume
- Hours Worked on a Resume: When to Include Them
- High school resume template: rewrite yours line by line
- Network administrator resume examples: rewrite yours line by line, with before and after