Hard skills for a resume: what counts, and how to list them so they get matched.
Hard skills are the teachable, checkable abilities a job runs on: a programming language, a clinical procedure, a machine you can operate, a method of accounting. They are what job postings often list first and what screening software looks for by name.
List the hard skills the posting names that you have really used, in the posting's exact wording, grouped by type (software, methods, equipment, languages). Then show the important ones at work in your bullets, with the scale and result. Leave off anything you could not use on your first day, and never add a tool just because the posting mentions it.
How to choose and list hard skills
- Pull every named skill from the posting. Software, systems, procedures, equipment, certifications and methods. Note which ones appear in the requirements and which are 'nice to have'.
- Keep only what you have used. Mark each skill you have used for real work, study or a project. Drop the rest, however tempting.
- Use the posting's spelling. If the posting says 'Microsoft Excel' and 'pivot tables', use those words rather than a nickname or abbreviation.
- Group the list. Short labelled lines such as Software, Methods, Equipment and Languages are easier to scan than one long row.
- Prove the top three in bullets. Show where you used each one, on what, and what it produced.
- Add level only when it helps. For languages or tools with clear levels, say how well you use them. Avoid star ratings or bars.
Illustrative examples to adapt
Illustrative: every name, employer, school, date and number in these samples is fictional or a bracketed placeholder. Replace each bracket with your own true details; never copy a result you did not achieve.
Grouped hard-skills section
When to use: The skills block of a resume for a technical or specialised role.
[Your name] [City, State] · [email] · [LinkedIn URL] TECHNICAL SKILLS Software: [tool from the posting], [second tool], [third tool] Methods: [method or procedure you have used], [second method] Equipment: [equipment you operate] Languages: [language], [level]
Hard skill proven in a bullet
When to use: An experience bullet that shows a named skill at work.
Built [what you built: report, model, part, schedule] in [the tool or method the posting names] for [who used it], which [result you can prove: hours saved, errors found, output delivered on time].
Project line for a skill learned outside work
When to use: When the skill comes from a course or personal project.
[Project name], [Month Year]: used [the hard skill] to [what you made or analysed]; [where it can be seen: link, portfolio, report].
Disclosure: TryHired makes HIRED, a paid job-search program, so we have a conflict of interest when we mention it. Every sample on this page is free to use without buying anything.
Is it a hard skill, and where does it go?
| Example | Hard skill? | Where it belongs |
|---|---|---|
| A software tool you use weekly | Yes | Skills section and at least one bullet. |
| A procedure you are trained and authorised to perform | Yes | Skills or certifications, plus a bullet. |
| 'Proficient in computers' | Too vague | Replace with the specific programs you use. |
| A language you speak | Yes | A languages line with your level. |
| A tool you watched a tutorial about | Not yet | Leave it off until you have used it on real work. |
| Problem solving | No, it is a soft skill | Show it inside a bullet instead. |
How jobs rate technical skills
Data O*NET 31.0 skill importance, 1 to 5. Counts are occupations rated 3.5 or higher; the jobs shown are TryHired career pages with the highest rating for each skill.
| O*NET skill | Occupations rated 3.5 or higher | Jobs on TryHired rated highest (importance) |
|---|---|---|
| Programming | 14 of 910 | Computer Programmer (4.8), Web Developer (4.1), Software Engineer (4.0) |
| Troubleshooting | 39 of 910 | Aircraft Mechanic (4.5), Diesel Mechanic (4.0), Electrician (4.0) |
| Quality Control Analysis | 32 of 910 | Quality Control Analyst (4.0), Aircraft Mechanic (3.8), Avionics Technician (3.8) |
| Equipment Maintenance | 25 of 910 | Aircraft Mechanic (4.9), Elevator Mechanic (4.0), Wind Turbine Technician (4.0) |
| Operations Analysis | 17 of 910 | Architect (4.1), Aerospace Engineer (3.9), Automotive Engineer (3.8) |
| Mathematics | 69 of 910 | Mathematician (5.0), Statistician (4.9), Biostatistician (4.6) |
These ratings describe what each job asks for. They are not evidence about you: prove a skill with something you did.
The same line, rewritten
Illustrative example with placeholders.
| Version | Example |
|---|---|
| Weak | Computer skills: proficient in Microsoft Office and various software programs. |
| Strong | Software: [spreadsheet tool the posting names] (lookups, pivot tables, charts), [second tool]; built a weekly [report] used by [who], which [result you can prove]. |
Why it matters: The weak line names nothing a reader can match. The strong version uses specific tool and feature names, and points to a piece of work that shows them in use.
Before you send it
- Every hard skill listed is one you have actually used.
- Spelling and naming match the posting.
- Skills are grouped under short labels.
- The three most important skills also appear in experience or project bullets.
- No rating bars, stars or percentages that a parser cannot read.
- Outdated tools no longer used in your field are removed.
Mistakes to avoid
- Copying every tool from the posting into your skills list, including ones you have never used.
- Writing 'proficient in' before everything instead of showing use in a bullet.
- Listing basic tools the role takes for granted ahead of the specialised ones it asks for.
- Using skill bars or self-ratings that mean nothing to a reader.
- Hiding hard skills in a sidebar or text box that some systems read out of order.
Build yours
Questions people ask
What is the difference between hard and soft skills?
Which hard skills should I put on my resume?
How many hard skills should I list?
Should I include skills I am still learning?
How this page is built
Written by Maid Dizdarevic, a career coach and 8x LinkedIn Top Voice. Advice is labelled as advice. Every sample uses a fictional person marked '(illustrative)' or a 'Your name' placeholder, and every employer, school, date and result is a bracketed placeholder for your own true details. Skill ratings come from O*NET 31.0: they describe what each occupation asks for, not what any reader has done.
- What a specific employer screens for: always read the posting.
- Your results: we never invent numbers, and you should never copy a result you did not achieve.
- Outcomes: no resume, letter, profile or program can promise an interview or a job.
- TryHired editorial guidance by Maid Dizdarevic, career coach, Nov 4, 2026.
- O*NET 31.0 Database, U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under the CC BY 4.0 license. TryHired selected, ranked and combined the data; O*NET is not responsible for these pages.