Identify a hard skill you already use
If you need to describe a hard skill, start with a task you have actually completed—not a list of tools you have heard of. A hard skill is a specific, learnable ability used to do a task, often involving a tool, method, or body of technical knowledge. To show that you already use one, name the task, describe what you did, and point to a result or artifact someone can inspect. This guide focuses on finding one such skill in your existing work and making its evidence clear.
What counts as a hard skill?
Cambridge defines a skill as an ability to do an activity or job well, especially through practice. Its business definition describes skills as particular abilities developed through training and experience that are useful in work. Those definitions emphasize demonstrated ability, not simply familiarity with a subject. Cambridge Dictionary: “skill”
“Hard skill” is commonly used for abilities tied to specific tasks, tools, methods, or technical knowledge. Examples include writing SQL queries, using spreadsheet formulas, editing audio, operating a particular design tool, maintaining equipment, or preparing a budget in accounting software. The exact skill depends on the task: “Excel” is a tool name; “use spreadsheet formulas to reconcile monthly expenses” is a more specific ability.
A skill does not have to come from a job or formal course. Harvard FAS’s technology career guidance lists coursework and academic projects, hackathons, independent or open-source contributions, and internships as ways to develop technical skills. The useful test for your own experience is whether you can describe something you did with the skill and identify what came from your work. Harvard FAS: Technology, Data Analytics, Artificial Intelligence
How to find a skill you already use
Start with a recent project, assignment, volunteer responsibility, personal project, or routine task. Ask yourself: What did I make, analyze, organize, repair, or deliver? Then walk backward from the output to the actions that produced it. This often uncovers a skill that a broad label such as “communication” or “problem solving” would hide.
For example, suppose you organized sign-up information for a student event. “Organization” may describe the broader contribution. If you cleaned inconsistent entries, used spreadsheet filters to spot duplicates, and created a reliable attendance list, you can name the narrower skill: cleaning and checking spreadsheet data. You do not need to have used advanced software or held a specialized title for that task to count as evidence of practice.
Use these questions to narrow the description:
If you cannot answer the last two questions, the skill label may be too broad or based on exposure rather than use. You may still be learning it; describe your level accurately instead of presenting it as a capability you have already demonstrated.
Turn the skill into a clear example
A concise evidence statement can follow this pattern: I used [specific skill] to [task] by [actions], producing [result or artifact]. Include enough detail that a reader can picture your contribution. Do not inflate the scale or take credit for a team’s work.
For instance: “I used spreadsheet formulas to compare the event’s registration list with check-in records, flagged duplicate entries, and delivered a corrected attendance sheet to the organizers.” This statement identifies a skill, explains its use, and names an output. If you know a verified outcome, such as the corrected list being used for follow-up, you can add it. Do not invent a percentage, time saved, or impact to make the example sound stronger.
Evidence can take several forms, depending on the task and what you are allowed to share:
Evidence does not have to be a public portfolio. If you cannot share the original work, describe the context in general terms and explain your process. Avoid revealing personal, client, employer, or proprietary information.
Match the evidence to the reader’s question
For a résumé, use the skill name where it fits naturally and use a bullet to show how you applied it. A bare list such as “Excel, data analysis, communication” names capabilities but gives little context. A task-focused bullet makes the claim easier to understand: “Checked registration records with spreadsheet filters and formulas, then prepared a corrected attendance list.” Keep it factual and choose details that matter to the role or assignment you are discussing.
For an interview, prepare one example you can explain out loud. Harvard FAS’s interviewing guidance says candidates should know their résumé and be ready to discuss their experiences and skills in relation to a position. Its behavioral interview section describes questions that ask for a particular situation and the actions taken, with the result based on those actions. Harvard FAS: Interviewing
A practical way to organize your answer is: situation, task, action, result. Keep the context brief, spend most of the answer on what you did, and finish with the outcome you can support. If the outcome was a completed deliverable rather than a measured change, say that. If several people contributed, explain your part clearly.
Check that your claim is credible
Before using your example, check it against these points:
A small, clearly explained example is more useful than a grand claim without support. If you followed a tutorial to make a first project, for example, describe it as a guided project and explain which parts you completed. If you independently adapted the method, say what you changed and why. Precision helps a reader judge what you can do without requiring you to overstate your experience.
When your example reveals a learning gap
Sometimes the task you remember shows familiarity rather than a skill you can reliably apply. That is useful information. Identify the missing step: perhaps you can enter data but have not checked it for errors, or you can edit an image but have not exported it for a particular platform. Describe the current ability at that level. Then, if appropriate, choose a small task that lets you practice and produce a new piece of evidence.
The goal is not to relabel every activity as expertise. It is to make one real capability visible. Pick one task you have completed, name the specific ability it required, and explain the action and evidence in plain language. That gives a reader a concrete basis for understanding a hard skill you already use.
Sources and scope
The source pages support the definitions and communication principles above. The checklists and sample wording are editorial examples for ordinary situations, without a promised outcome.