Hard Skills: Definition + 100 Examples

1. What Are Hard Skills?

Hard skills involve specific knowledge or ability used to complete tasks. If you can reconcile an account, clean a messy dataset, cut a joint accurately, set up a paid campaign, document a process so somebody else can follow it, or read a drawing and produce the part it describes, those are hard skills. Each one names something you do rather than something you are like.

They come from a wide range of places, and the source does not change whether something counts:

• • Formal education, including school, college and university programmes
• • Workplace training, including onboarding and internal courses
• • Apprenticeships and structured on-the-job training
• • Supervised practice, where someone experienced checks your work
• • Certifications and assessed programmes
• • Short courses, including online courses
• • Self-study using documentation, books and practice material
• • Personal, volunteer or class projects that produce real output
• • Ordinary on-the-job experience accumulated over time

That point is worth stating plainly, because a lot of advice implies otherwise. A skill learned through self-study is not a lesser category of skill than one learned on a course, and a skill learned informally at work is not disqualified because nobody issued a certificate for it. What varies is how easily the skill can be evidenced, not whether it is real.

The reverse distinction matters just as much. A degree, certificate or licence is not identical to the skill it relates to. A CPA licence is a credential; accounting skill is the ability to do the work. A welding certification attests that specified requirements were met to a standard; welding ability is what happens at the bench. A course completion certificate records attendance and assessment, not proficiency.

None of that undermines credentials. In many fields a licence or certification is a genuine requirement, sometimes a legal one, and no amount of practical ability substitutes for it. The accurate framing is that credentials and skills are related but distinct: a credential can be required, can support your claim, and can be evidence — and it is still a different thing from the underlying ability.

2. Hard Skills Definition

Four characteristics make that definition usable in practice.

• Specific. A hard skill names something identifiable. “Variance analysis” is specific; “numbers” is not. Specificity is what allows another person to picture the work and ask a sensible question about it.
• Learnable and developable. Hard skills are acquired. That is true of soft skills too, so this characteristic does not separate the categories on its own — but it does rule out treating hard skills as innate talent.
• Demonstrable through work or tasks. A hard skill generally shows up in output: a document, a reconciled ledger, a weld, a query, a finished edit. Demonstrability is not the same as numerical measurement; some hard skills are judged by inspection or by an experienced reviewer rather than scored.
• Context-dependent. The same named skill means different things in different settings. “Scheduling” in a two-person clinic and “scheduling” on a construction programme share a word and little else.

A large amount of confusion comes from treating adjacent concepts as interchangeable. They are not:

Three distinctions in that table cause most of the trouble. Tool familiarity is not proficiency: having used an application is not the same as being able to produce competent work with it, and the gap is obvious to anyone who uses the tool daily. A qualification is not a skill: it evidences a programme of study, which may or may not map onto what an employer needs done. A certification does not automatically confer competence: it confirms that assessed requirements were met at a point in time.

A licence sits differently again. Where work is regulated, a licence may be legally required regardless of how practically skilled someone is. Practical ability does not create authorization, and lacking authorization does not mean lacking skill. Both statements are true at once, and career advice that ignores either one is unhelpful.

3. 100+ Hard Skills Examples

The list below contains 132 distinct hard skills grouped into 15 categories. They are deliberately different from one another rather than variations on the same entry, because a padded list is useless for the job it is meant to do: helping you recognize what you already have and see what a target role might expect.

Read it as a prompt, not as a menu to copy. A skill belongs on your own list only if you could truthfully describe using it.

Two cautions attach to the healthcare and trade entries in particular. Some of those activities require specific education, certification, licensing, authorization or supervision, and the requirements depend on jurisdiction and role. Learning about a clinical or regulated task online does not qualify anyone to perform it. The entries are listed here so you can recognize skills you have been properly trained to use, not as an invitation to claim them otherwise.

Languages are treated as one category rather than expanded into dozens of individual languages. Listing forty languages would inflate the count without telling you anything, and the useful content about language proficiency is in section 14.

4. Hard Skills vs. Soft Skills

Hard skills are specific task or domain abilities. Soft skills are behavioural, interpersonal and work-style abilities that shape how someone works with people, decisions and situations. That is the core of the distinction, and it is genuinely useful — as long as it is not pushed further than it can carry.

Three common claims about this comparison are wrong often enough to be worth naming. The first is that hard skills are measurable and soft skills are not: plenty of hard skills are judged qualitatively by an experienced reviewer, and plenty of soft skills are assessed systematically through structured interviews and references. The second is that hard skills are learned and soft skills are innate: both are developed. The third is that one category matters more than the other, which depends entirely on the role.

In real work the two run together. Here are pairings where a hard skill and a soft skill are doing different jobs on the same task:

Some labels span both categories depending on exactly what is being described. “Project management” is the clearest case: project scheduling, budget tracking and project software are hard skills, while leadership, negotiation and communication are soft skills, and the single phrase covers both. “Customer service” behaves similarly — operating the ticketing system is one kind of ability, de-escalating an angry caller is another.

It is also worth saying that this taxonomy is not universally standardized. Different employers, frameworks and writers draw the line in different places, and some avoid the hard/soft split entirely in favour of technical, behavioural and cognitive groupings. Treat the categories as a way of thinking clearly about your own abilities rather than as an official classification you must match.

For a deeper look at interpersonal and work-style abilities, see our guide to soft skills, with 100+ examples and practical ways to demonstrate them.

For how to present both sides on an application, our guide to skills for a resume covers the broader resume-skills question in detail.

5. Data and Analytics Hard Skills

Data skills have spread well beyond analyst job titles. Plenty of operations, administrative, finance and marketing roles now involve pulling records together, checking them and turning them into something a decision can be based on. The skills that recur are:

• • Spreadsheet analysis, including formulas, lookups and pivot tables
• • SQL and database querying
• • Data cleaning, including handling duplicates and inconsistent fields
• • Data validation and reconciliation between sources
• • Statistical analysis appropriate to the question being asked
• • Data visualization, choosing a chart that does not mislead
• • Dashboard creation and maintenance
• • Recurring reporting and report automation
• • Forecasting from historical patterns, with stated assumptions
• • A/B test analysis and interpreting results honestly

The most underrated of these is data cleaning. It is unglamorous, it takes most of the time on most analyses, and being genuinely good at it — spotting that two systems disagree before building anything on top of them — is a real differentiator worth stating on a resume.

Describing your level is where people go wrong. Avoid the beginner-to-expert ladder pinned to years, because years spent with a tool say very little about what you can do with it, and no universal timetable exists for reaching proficiency. A more honest progression describes what you can do unaided:

• Familiarity. You have used it and can follow an existing process with support or documentation.
• Routine independent use. You handle the ordinary cases yourself, including the usual problems, without needing someone to check the output.
• More complex application. You handle unusual cases, design the approach rather than following one, and can explain why you chose it.

If you are trying to work out which of these skills to build next, our career planning guide covers sequencing skill development against a target role.

6. Software, Programming and IT Skills

This group covers programming languages, web technologies, version control, APIs, databases, cloud platforms, systems administration, networking, cybersecurity practices and technical troubleshooting. The spread is wide, and the roles that use it range from software engineering through IT support to technical operations.

• • Programming in a specific language, such as Python, JavaScript, Java or C#
• • HTML and CSS for web output
• • Git and version control workflows
• • API integration and working with third-party services
• • Database design and querying
• • Cloud platform administration
• • System administration and configuration
• • Network configuration and diagnostics
• • Security practices such as access management and vulnerability assessment
• • Technical troubleshooting and incident handling

Listing a language name does not communicate proficiency, and everyone reviewing technical resumes knows it. The word “Python” on its own could mean a completed tutorial or eight years of production work. Specifying the context does the work instead:

Notice that the stronger version contains no invented numbers. There is a strong pull towards attaching a percentage to everything on a technical resume, and made-up figures are both dishonest and easy to puncture. If you genuinely know that a script replaced a manual process that took an afternoon each week, say that. If you do not know, describe the work without a metric; a precise description with no number beats a vague one with a fabricated number.

The same applies to breadth. A list of twenty technologies invites the interviewer to pick the one you know least. A shorter list you can discuss in depth is a stronger position to be in.

7. Finance and Accounting Skills

Finance and accounting skills are unusually well suited to precise description, because the tasks have names that mean the same thing across employers. That works in your favour: “month-end reconciliation” communicates something exact in a way that “financial acumen” does not.

• • Bookkeeping and ledger maintenance
• • Account reconciliation
• • Financial statement preparation
• • Financial analysis and commentary
• • Budgeting and budget consolidation
• • Variance analysis against budget or forecast
• • Accounts payable processing
• • Accounts receivable and collections administration
• • Payroll processing
• • Cost accounting and allocation
• • Financial modeling
• • Tax return preparation, within your authorized scope

Some of these activities may require credentials, registration or authorization depending on the jurisdiction, the employer and what exactly is being signed off. This guide describes them as career skills; it does not advise on tax matters, and nothing here should be treated as tax or financial advice. Questions about what you are permitted to prepare or file belong with a qualified professional or the relevant authority.

The title distinction matters here more than almost anywhere else. Having strong bookkeeping skills does not make someone an accountant, and it certainly does not imply a CPA or equivalent designation. Those are protected or regulated descriptions in many places, and using them loosely on a resume is a serious error rather than a stylistic one. Describe the tasks you perform and list any credential you actually hold, exactly as you hold it.

8. Sales and Marketing Hard Skills

Sales and marketing are frequently described entirely in soft-skill terms, which undersells the technical and process side of both. Splitting them out makes the resume clearer and the interview easier.

No benchmark figures appear in this section on purpose. Typical conversion rates, quota attainment, open rates and cost-per-acquisition vary so widely by market, product, price point and channel that a general number would be invented rather than informative. If you have real figures from your own work and you are permitted to use them, they belong on your resume; borrowed industry averages do not.

9. Project Management and Operations Skills

Project and operations work is a good illustration of the hard/soft mix, because it is almost impossible to do either well using only one side.

• • Project scheduling and dependency tracking
• • Project management software administration
• • Budget tracking and cost reporting
• • Risk register maintenance and issue logs
• • Process mapping and process documentation
• • Inventory management systems
• • Procurement systems and purchase order handling
• • Quality-control procedures and inspection routines
• • Resource planning and capacity tracking
• • Workflow documentation and standard operating procedures

The soft components sit alongside them: leading without formal authority, keeping communication moving between functions that do not naturally talk, resolving conflict over priorities, and negotiating scope when the date will not move. A schedule that nobody has agreed to is a document, not a plan.

Two limits are worth stating clearly. Using project-management software is not the same as being a project manager; the tool is one component of a role that usually involves accountability for scope, budget and delivery. Coordinating projects does not automatically mean holding a project-management qualification, and where employers expect a specific certification, practical coordination experience does not substitute for it.

The practical consequence is to avoid title inflation. “Coordinated a five-workstream rollout across two sites, maintaining the schedule and risk log” describes real scope and survives questioning. “Project manager” applied to the same work, when that was not your role, does not.

10. Administrative and Business Skills

Administrative hard skills are routinely underdescribed, partly because the people who hold them are used to the work being invisible when it is done well. They are, however, highly specifiable.

• • Spreadsheet reporting and tracking
• • Records management and filing systems
• • Document formatting and templates
• • Calendar and diary management across time zones
• • Invoicing and expense processing
• • Data entry with accuracy checks
• • Business correspondence
• • Presentation software and deck production
• • Meeting documentation, agendas and minutes
• • Database and CRM record maintenance

“Microsoft Office” is usually too vague to be worth the line it occupies. It covers everything from typing a letter to building a financial model, so it tells a reader almost nothing. Naming the task is far stronger:

• • Excel pivot tables and lookup functions for reporting
• • PowerPoint presentation creation from raw content
• • Word document formatting, templates and styles
• • Outlook calendar coordination for multiple diaries

The same honesty rule applies as everywhere else: do not claim a level of proficiency you could not show. If your spreadsheet work is confident data entry and simple formulas, say that rather than implying modelling ability. Being accurately described at a lower level is a far better position than being hired against an inaccurate one.

11. Writing, Design and Creative Hard Skills

There is a nuance here that most skill lists miss. Creativity itself is usually described as a soft skill — a way of thinking rather than a procedure. But the production abilities that turn an idea into a finished artefact are hard skills, and they are learnable, teachable and demonstrable in exactly the usual way.

• • Copyediting to a style guide
• • Proofreading
• • Technical writing
• • Content editing and structural revision
• • Documentation writing
• • CMS publishing and content operations
• • Graphic design and layout
• • Photo editing, compositing and retouching
• • Video editing and assembly
• • Motion graphics
• • Illustration
• • Typography

Creative resumes suffer more than most from listing tools where skills belong. “Photoshop” is a tool. “Photo compositing and retouching using Photoshop” describes a skill, names the tool, and tells the reader what you actually produce. The second version also survives the follow-up question, because there is something specific to talk about.

Creative fields also have the advantage that evidence is usually easy to show. A portfolio of work you are permitted to display settles most of the proficiency question before anyone has to ask about it.

12. Engineering, Manufacturing and Trade Skills

Engineering, manufacturing and the skilled trades contain some of the most clearly defined hard skills of any field, because the output either meets the specification or does not.

• • CAD modeling
• • Technical drawing and drafting
• • Blueprint and schematic reading
• • Measurement, calibration and inspection
• • Engineering calculations
• • Simulation software
• • Test procedure execution and recording
• • Machining
• • CNC operation and setup
• • Welding
• • Metal fabrication
• • Electrical installation work
• • Plumbing installation work
• • Carpentry
• • Equipment maintenance and fault finding

A serious caution applies to this whole group. Many trade and engineering activities carry jurisdiction-specific licensing, certification, safety, apprenticeship or supervision requirements, and those requirements exist because the work can injure people when it is done by someone untrained or unauthorized. Nothing in this guide should be read as suggesting that you carry out regulated or hazardous work without the proper training and authorization.

This section is therefore a career-skills overview only. It deliberately contains no procedural instruction: no settings, no techniques, no steps for performing any of these activities. Its purpose is to help you name and evidence skills you have already been trained to use, and to recognize what a target role may require.

On a resume, these skills pair naturally with the standards, materials and equipment you have worked to, and with your credentials listed separately and exactly as held. If you are considering moving between trades or into a related field, our guide on how to change careers covers the process side of that move.

13. Healthcare and Research Hard Skills

Healthcare skills need the most careful wording of any category on this page, because the gap between a skill and the authorization to use it is widest here.

Several of the healthcare activities above require regulated education, certification, licensure, authorization or supervision, and the specific requirements depend on the jurisdiction, the setting and the role. Scope of practice is a legal matter, not a matter of confidence or self-assessment. This guide does not teach clinical procedures and contains no clinical instruction of any kind; it describes these items only as career skills that trained and authorized people may hold.

Research skills are less restricted, but they carry their own limit. Being able to design a survey, run an analysis or manage references does not qualify someone for regulated clinical research responsibilities, which involve protocol, consent, safety and ethical obligations governed separately. Describing research skills accurately means describing the studies or projects you worked on and the part you actually played in them.

14. Language Skills

Language proficiency is a hard skill when the work uses it. It is learnable, specific, demonstrable and often directly relevant to the job — and it is also one of the most frequently overclaimed items on a resume, usually without intent to mislead.

The confusion comes from treating “speaks Spanish” as a single fact. In work terms it is several different abilities, and you may have some and not others:

• Conversational. Comfortable in everyday exchanges and informal situations.
• Professional working. Able to handle work discussions, including subject-specific vocabulary.
• Written. Able to produce correspondence or documents to a professional standard.
• Reading. Able to read and understand work material, which can outstrip speaking ability.
• Interpreting. Rendering spoken language in real time, a distinct trained skill.
• Translating. Producing accurate written translations, also a distinct trained skill.

Speaking a language is not the same as being able to interpret or translate professionally. Both involve specialized technique, subject knowledge and accuracy obligations, and in legal, medical and official contexts they may require specific credentials. Offering to interpret in a setting like that, on the strength of being bilingual, can create real problems for the people involved.

On a resume, describe the ability in terms of the work you can do in that language: “Spanish — handled customer calls and written correspondence”, or “French — read technical documentation; limited spoken use”. If you hold a formal language qualification or test result, state it as the qualification it is. Avoid inventing proficiency labels that look official but are not.

15. How to Identify Your Hard Skills

Most people underestimate their hard skills, because familiar tasks stop registering as skills at all. This eight-step framework works from what you do rather than from a list you recognize.

1. 1. List the tasks you can actually perform, in plain language, without using job titles.
2. 2. List the tools, software and equipment you use, and how regularly you use them.
3. 3. Identify the methods and processes you know, such as reconciliation, testing or intake procedures.
4. 4. Identify the domain knowledge you apply, such as regulations, product knowledge or terminology.
5. 5. Review projects you have completed and note what you personally produced.
6. 6. Review education, training and credentials separately, without confusing a credential with a skill.
7. 7. Compare that list against the requirements in real job postings you are targeting.
8. 8. Keep only the skills you could truthfully demonstrate if asked to.

The sixth step is the one people skip. Credentials feel like the strongest part of the list, so they get folded in with skills — and then the skills section describes what you studied rather than what you can do. Keep the two lists apart, and let each do its own job.

Eight illustrative conversions, all fictional, showing how an ordinary task becomes a named skill with evidence attached:

These examples are written as patterns to follow, not as achievements to borrow. The point of the exercise is to produce your own rows from your own work; a table filled with someone else’s examples is worse than an empty one.

HARD SKILLS IDENTIFICATION WORKSHEET

Convert experience into skills using:
TASK -> POSSIBLE HARD SKILL -> EVIDENCE -> TARGET RELEVANCE

TASK:
POSSIBLE HARD SKILL:
EVIDENCE:
TARGET RELEVANCE:

TASK:
POSSIBLE HARD SKILL:
EVIDENCE:
TARGET RELEVANCE:

TASK:
POSSIBLE HARD SKILL:
EVIDENCE:
TARGET RELEVANCE:

RULES
- Describe the task before naming the skill.
- Do not name a skill you could not demonstrate.
- Keep credentials in a separate list from skills.
- State the scope you actually had, not the scope of the role you want.

16. Hard Skills for a Resume

Hard skills appear in three places on a resume, and each does something different. Repeating the same list in all three wastes the space.

The governing principle is that evidence beats keyword dumping. A long skills list containing everything you have ever touched reads as filler, and it dilutes the items that matter. A shorter list, each entry of which is visible somewhere in your experience section doing real work, reads as a person who knows what they can do.

No percentage appears in that example, and none is needed. Do not fabricate figures to make a bullet look stronger — an invented improvement is the easiest thing in the world to ask a follow-up question about, and the answer is always worse than the honest version would have been.

Using terminology from the job description is sensible where it accurately describes what you do. If a posting says “variance analysis” and that is the work you perform, use their phrase. What does not work is copying requirements you cannot defend: the posting is a wish list, not a template for your history, and matching it word for word in an interview you cannot support costs you the role anyway.

HARD SKILLS ON A RESUME - TEMPLATE

SKILLS
Data: [skill], [skill], [skill]
Tools: [tool-based skill], [tool-based skill]
Methods: [process or method], [process or method]
Languages: [language and proficiency context]

EXPERIENCE BULLETS (evidence, not repetition)
- [Did what] using [tool or method] to [purpose], [frequency or scope].
- Maintained [system or record set], including [specific task you performed].
- Produced [output] from [inputs], checking [what you validated].

EXAMPLE
Weak:   Excel
Better: Built monthly Excel reports using PivotTables and lookup functions to
        reconcile operational records.

RULES
- Only list what you could be asked to do in an interview.
- Use the employer's terminology only where it accurately describes your skill.
- Do not invent numbers.

This section deliberately stays narrow — hard skills specifically. For the broader question of which skills belong on a resume overall, including soft skills, computer skills and job-specific examples, see our guide to skills for a resume. For how the skills sit inside a finished document, see resume examples and resume summary examples.

Hard Skills Examples for Students

Students often assume they have no hard skills because they have no full-time job history. That is a mistake: hard skills come from tasks, and coursework, labs, projects and part-time work all produce tasks. The question is how to describe them honestly.

• • Spreadsheet analysis, including formulas and pivot tables
• • Presentation creation and delivery materials
• • Academic and source research
• • Citation management
• • Statistical software used in coursework
• • Coding in a language taught or self-studied
• • CAD, where studied on a technical course
• • Laboratory techniques, where trained and supervised
• • Foreign-language proficiency
• • Video editing
• • Graphic design
• • Data visualization
• • Technical or report writing
• • CMS publishing, for example a student publication

The experience behind them can come from any of these sources:

• • Classes and assessed coursework
• • Laboratory and practical sessions, where supervised
• • Course projects and dissertations
• • Internships and placements
• • Part-time and vacation work
• • Student organizations and societies
• • Volunteering
• • Personal projects built outside study

The rule that keeps this honest is simple: describe classroom and project work as classroom and project work. It is legitimate, relevant evidence, and it does not need to be disguised as employment. Presenting a class assignment as a professional engagement is a misrepresentation, and reviewers spot it quickly because the details never quite fit.

The second version is shorter, more specific and immediately believable. It also gives an interviewer something real to ask about, which the inflated title does not. If you are still deciding what to aim at, the career aptitude test and our guide on how to choose a career may help you narrow the target before you build skills towards it.

STUDENT HARD SKILLS - EXAMPLE WORDING

SKILLS
Excel (PivotTables, lookups), Python (coursework projects), academic research,
citation management, technical writing, Spanish (professional written)

PROJECT / COURSEWORK
- Used Excel PivotTables to analyse a class project dataset of survey responses
  and produced the summary tables used in the final report.
- Wrote and edited a 6,000-word research report, including sourcing and
  managing references.

RULES
- Describe coursework as coursework and projects as projects.
- Do not imply a job title you did not hold.
- Do not describe unpaid or class work as employment.

How to Develop Hard Skills

Developing a hard skill is mostly a matter of choosing one and practising the real task, rather than collecting material about it. This eight-step approach keeps that focus.

1. 1. Identify one target skill, named specifically rather than as a broad field.
2. 2. Find out what competent use of it looks like in the context you are aiming at.
3. 3. Choose a learning route that matches the skill, including a regulated route where one is required.
4. 4. Practise the actual task, not only the theory behind it.
5. 5. Build evidence as you go: a document, a repository, a portfolio piece, a completed job.
6. 6. Get feedback from someone who can judge the work, where that is available to you.
7. 7. Increase complexity gradually rather than jumping to the hardest version.
8. 8. Keep the skill current where the tools, standards or regulations change.

The available learning routes vary by skill, and the right one depends on the field rather than on general preference:

• • Formal education
• • Apprenticeships
• • Workplace training
• • Short courses and online courses
• • Supervised practice
• • Projects that produce real output
• • Self-study
• • Certifications, where they are genuinely expected in the field

Three distinctions are worth repeating, because the learning market is built on blurring them. A course is not competence: it is an input. A certificate is not proficiency: it records that something was completed or assessed. A credential is not the skill itself: it is a statement about you, and the skill is what you can do. All three can be worthwhile and all three can be required — none of them substitute for being able to perform the task.

Where a skill is regulated or hazardous, the route is not a free choice. Trade, clinical and safety-critical work requires properly approved training and authorization, and self-teaching is not an acceptable substitute for it. Plan those skills through the recognized route for your jurisdiction.

To turn this into something scheduled rather than aspirational, our professional development plan guide covers structuring skill development over a defined period.

HARD SKILL DEVELOPMENT PLAN

TARGET SKILL:
WHY IT MATTERS FOR MY TARGET ROLE:

WHAT COMPETENT USE LOOKS LIKE IN THAT CONTEXT:
-
-

LEARNING ROUTE (education / apprenticeship / training / course /
supervised practice / project / self-study / certification):
-

REGULATED OR HAZARDOUS? IF YES, REQUIRED APPROVED ROUTE:
-

PRACTICE TASKS (the real task, not only theory)
1.
2.
3.

EVIDENCE I WILL PRODUCE
-
-

FEEDBACK SOURCE
-

HOW I WILL INCREASE COMPLEXITY
-

HOW I WILL KEEP IT CURRENT
-

How to Prove a Hard Skill

A claimed skill and an evidenced skill are treated very differently, and the difference costs nothing to close if you have kept anything from your work. Useful evidence can include:

• • Work examples, where you are permitted to share them
• • A portfolio assembled from work you may show
• • A completed project, including personal or study projects
• • A code repository
• • A writing sample
• • A design sample
• • Documented output such as a report, procedure or model you produced
• • An assessment or practical test
• • A relevant credential, licence or certification
• • A practical interview task
• • References who can confirm the responsibilities you held
• • Quantified results, but only where they are real and you are allowed to cite them

There is a hard limit on what you may show. Never share confidential employer data, proprietary code, private customer information, protected health information, trade secrets or restricted documents in order to demonstrate a skill. Doing so can breach contracts, professional obligations and in some cases the law, and it tells a prospective employer that you would do the same with their material. Where the actual work cannot be shown, recreate a comparable example with invented data, or describe the work without exposing it.

Credentials belong in the evidence list, with a qualification attached. A certification or licence can support your claim and may be a requirement for the role, but it is not automatic proof of every practical capability someone might associate with it. Two people holding the same credential can differ substantially in what they can do, which is exactly why practical tasks and portfolios are so common in hiring.

Quantified results are persuasive when they are real and you are permitted to cite them. If you do not have a number, or you cannot verify the one you remember, describe the scope instead: what you handled, how often, and what standard it had to meet.

Hard Skills vs. Transferable Skills

These two terms are often used as if they were alternatives, which they are not. They answer different questions about the same ability.

A hard skill describes the type or nature of an ability: specific, learnable, task- or domain-oriented. A transferable skill describes whether an ability applies across contexts. One is about what kind of thing the skill is; the other is about where it can be used. Because they are different axes, the categories overlap: a hard skill can be transferable or not, and a transferable skill can be hard or soft.

The practical use of this distinction appears when you change direction. Sorting your hard skills by how far they travel tells you which parts of your experience you can carry into a different sector and which are tied to where you learned them. That is a different exercise from listing them, and it is covered in depth in our guide to transferable skills, which includes its own examples, mapping method and worksheet rather than repeating what is on this page.

Hard Skills Worksheet

A sixteen-part worksheet for assembling your own hard-skills inventory against a specific target role. It does not score you, match you to occupations or produce a result — it organizes what you know so you can see the gaps. Credentials stay in their own section throughout, separate from skills.

1. 1. Target role
2. 2. Recurring job requirements
3. 3. Tasks I can perform
4. 4. Software and tools
5. 5. Equipment
6. 6. Methods and processes
7. 7. Domain knowledge
8. 8. Training and education
9. 9. Credentials
10. 10. Projects
11. 11. Evidence
12. 12. Proficiency context
13. 13. Relevant hard skills
14. 14. Gaps
15. 15. Next skill to develop
16. 16. Resume evidence

HARD SKILLS WORKSHEET

Keep credentials and skills in separate sections. There is no score.

1. TARGET ROLE
-

2. RECURRING JOB REQUIREMENTS (from 3-5 real postings)
-
-
-

3. TASKS I CAN PERFORM
-
-
-

4. SOFTWARE / TOOLS I USE
-
-

5. EQUIPMENT I OPERATE
-
-

6. METHODS / PROCESSES I KNOW
-
-

7. DOMAIN KNOWLEDGE I APPLY
-
-

8. TRAINING / EDUCATION
-
-

9. CREDENTIALS (kept separate from skills)
-
-

10. PROJECTS I HAVE COMPLETED
-
-

11. EVIDENCE I COULD SHOW
-
-

12. PROFICIENCY CONTEXT (what I do independently vs. with support)
-
-

13. RELEVANT HARD SKILLS FOR THE TARGET ROLE
-
-
-

14. GAPS BETWEEN MY LIST AND THE REQUIREMENTS
-
-

15. NEXT SKILL TO DEVELOP
-

16. RESUME EVIDENCE (one truthful bullet per relevant skill)
-
-
-

Copy it into any document or notes app. There is no file to download and nothing to sign up for.

Common Hard Skills Mistakes

Fourteen errors that recur, most of them variations on claiming more than can be supported.

1. 1. Listing software you cannot actually use beyond opening it.
2. 2. Treating exposure to a tool as proficiency with it.
3. 3. Keyword stuffing a skills section to get past filters.
4. 4. Copying every requirement from a job description into your resume.
5. 5. Using vague umbrella terms such as Microsoft Office instead of the actual tasks.
6. 6. Claiming credentials you do not hold.
7. 7. Treating a certification as identical to competence in the work.
8. 8. Treating course completion as proof of proficiency.
9. 9. Inflating a title to match the skills you used.
10. 10. Overstating your proficiency level in a way you cannot defend in an interview.
11. 11. Listing outdated skills with no context about when or how you used them.
12. 12. Filling space with skills that are irrelevant to the target role.
13. 13. Inventing metrics to make a skill sound more impressive.
14. 14. Ignoring licensing, authorization and safety requirements attached to regulated work.

Three of these deserve emphasis. Ignoring licensing and safety requirements is not a resume problem but a real-world one, with consequences beyond a failed application. Title inflation is the fastest way to lose credibility for the accurate parts of your history. And overstating proficiency tends to be discovered at the worst possible moment — either in a practical exercise or, worse, after you have started the job.

Frequently Asked Questions