Hard Skills for a Resume: Examples for 8 Job Types

Good hard skills for a resume are the tools, methods, and job-specific abilities you can demonstrate through actual work. SQL, financial modeling, usability testing, and CAD can all belong on a resume. Which ones belong on yours depends on the role and what you have done.

Below are 32 examples across eight job types. Each pairs a skill with a situation where you might use it and a resume bullet showing the work. Start with your job type, then adapt the examples to your own evidence.

What counts as a hard skill?

A hard skill is a learned ability used to perform a specific task, such as writing a SQL query, building a financial model, or producing a technical drawing. A tool name can help identify it, but the useful detail is what you can do with that tool.

Soft skills describe how you work with people or approach problems. For example, communication is a soft skill; writing an API specification is a specific technical task that can also demonstrate communication. A bullet can show both without turning your skills section into a list of personality traits.

This guide is an example library. For the full process of choosing terms from a particular posting, use our resume skill keywords guide.

Find hard skills for your job type

Job type	Examples to look for below
Software engineering	Programming, APIs, version control, automated testing
Data analysis	SQL, data cleaning, spreadsheets, dashboards
Product management	Requirements, prioritization, product metrics, experiment design
UX and product design	Prototyping, usability testing, information architecture, accessibility checks
Digital marketing	SEO, analytics, paid search, email segmentation
Finance and financial analysis	Modeling, variance analysis, financial statements, valuation
Project coordination	Scheduling, budget tracking, process mapping, risk tracking
Mechanical engineering	CAD, drawings, simulation, physical testing

All bullets below are fictional teaching examples. The projects, numbers, and deliverables are invented to show how a skill can appear in context. Use the structure, then replace the details with work you actually did. The skills and additional directions are options, not requirements for every role.

Choose which skills to include first

Use the posting's own required and preferred labels to choose among skills you can demonstrate. A skill's appearance in this guide does not determine its priority for your application.

Situation	What to do on your resume	Example
Required in the posting, supported by your work	Put it where it is easy to find, then show the relevant work in a bullet.	The posting requires SQL; include SQL and the query project you can explain.
Preferred in the posting, supported by your work	Include it when it adds relevant detail and fits the available space.	Power BI is preferred; include a dashboard you built after covering the required skills.
Mentioned in the posting, not supported by your work	Leave it out for now. If your notes are incomplete, confirm the experience before adding it.	Do not add Python just because you used Excel or saw Python in the posting.

Keep required and preferred distinct. An unsupported required skill is a gap to assess; renaming another skill does not fill it. For the full selection workflow, use the resume skill keywords guide linked above.

Software engineering

Choose skills that match the kind of software you build. A backend project, a mobile application, and an embedded system will need different evidence. O*NET's software developer profile includes development, testing, documentation, and modifying existing systems; the examples here illustrate parts of that work.

Hard skill	When you might use it	Fictional resume bullet
Programming in Python	Turning a recurring file-processing task into a script.	Wrote a Python script to validate incoming CSV files, flag missing fields, and produce an error report for a class research project.
REST API development	Letting an application create, retrieve, or update records.	Built REST endpoints for a student project tracker, adding input validation and documenting request and response formats for the frontend team.
Git version control	Keeping changes separate and reviewing code with teammates.	Used Git branches and pull requests to integrate changes for a four-person course project and resolve conflicting edits before release.
Unit testing	Checking expected behavior and edge cases after code changes.	Added unit tests for a booking service's date validation and cancellation rules, including invalid inputs and boundary dates.

Other directions: Frontend work may call for HTML/CSS, JavaScript or TypeScript, and a framework such as React. Backend work may involve SQL, server-side frameworks, or cloud deployment. Mobile work may use Swift or Kotlin. Choose the branch that matches your target role and projects.

Data analysis

Data skills become clearer when you name the question, the data, and the output. The O*NET business intelligence analyst profile covers reporting, dashboards, and analysis; the examples below show how those tasks can become resume evidence.

Hard skill	When you might use it	Fictional resume bullet
SQL joins and aggregation	Combining related tables to answer a reporting question.	Joined transaction and product tables in SQL to summarize monthly bookstore sales by category and identify records missing product classifications.
Data cleaning with pandas	Making inconsistent source files usable for analysis.	Cleaned survey exports with pandas, standardized response labels, and documented duplicate-handling rules before the team analyzed the results.
Excel PivotTables and lookups	Reconciling records or summarizing a recurring report.	Used Excel PivotTables and XLOOKUP to reconcile event registrations with payment records and flag unmatched entries for the student treasurer.
Dashboard development	Giving a team a repeatable view of its metrics.	Built a Power BI dashboard showing weekly support volume and response-time trends, with filters by issue type and a written metric definition.

Other directions: BI reporting may involve Tableau or data modeling; quantitative analysis may use statistics, R, or forecasting; data pipeline work may involve ETL and warehouse queries. Use the posting to distinguish reporting, analysis, and engineering work rather than treating them as one skill set.

Product management

For product roles, name a method or deliverable rather than listing "strategy" alone. Atlassian's product management guide describes customer needs, priorities, and product direction; your bullet should identify the part you personally handled.

Hard skill	When you might use it	Fictional resume bullet
Requirements writing	Making a proposed feature specific enough to discuss and build.	Drafted requirements and acceptance criteria for a campus app's saved-search feature, documenting empty states and error cases for design and engineering review.
Feature prioritization	Comparing possible work against a consistent set of assumptions.	Applied a reach, impact, confidence, and effort scoring model to compare six feature proposals and documented assumptions for the team's planning discussion.
Product metric definition	Agreeing on what an event or success measure actually means.	Defined activation events for a course project, specifying which actions counted, the measurement window, and exclusions before dashboard implementation.
Experiment design	Planning how a team would compare alternatives and interpret results.	Wrote an experiment plan for an onboarding flow, including the hypothesis, primary metric, guardrail metrics, and criteria for interpreting the test.

Keep the project stage visible: requirements drafted, experiment planned, or feature launched.

UX and product design

Design evidence can be a prototype, a study, an information structure, or a documented evaluation. The O*NET digital interface designer profile includes interface design, user research, testing, and accessibility considerations.

Hard skill	When you might use it	Fictional resume bullet
Interactive prototyping in Figma	Showing how a user moves through a proposed flow.	Created a Figma prototype for a student appointment-booking flow, including confirmation, rescheduling, and error states for a design critique.
Moderated usability testing	Observing where users struggle with a specific task.	Ran five usability sessions on a library search prototype, recorded task-completion issues, and grouped findings into navigation and labeling changes.
Information architecture	Organizing content so users can find what they need.	Used a card-sorting exercise to reorganize a student services website and produced a revised sitemap with proposed navigation labels.
Accessibility evaluation	Checking specific interface behaviors against relevant requirements.	Checked keyboard navigation and color contrast on a course website, documented issues, and annotated proposed changes for the development team.

For accessibility work, name the checks performed and their scope rather than claiming whole-product compliance.

Digital marketing

Marketing hard skills include research, measurement, and campaign implementation. O*NET's search marketing profile includes these activities. Choose examples that fit your channel and actual access to campaign tools or data.

Hard skill	When you might use it	Fictional resume bullet
SEO keyword and intent research	Deciding which questions a page should answer.	Grouped search queries by intent for a student publication and mapped each topic to an existing page or a proposed article brief.
Web analytics reporting	Reviewing how visitors reach a site and use key pages.	Built a Google Analytics 4 report comparing campaign-tagged landing pages and documented the difference between visits, form starts, and completed forms.
Paid search campaign setup	Organizing ads and measuring a campaign against its brief.	Set up Google Ads campaign drafts with themed ad groups, negative keywords, and tracking parameters for review by the marketing lead.
Email segmentation and quality assurance	Matching an email to the intended audience and checking its setup.	Created audience segments for a campus newsletter and checked links, audience exclusions, and test sends before the editor approved distribution.

Other directions: CRM and lifecycle roles may involve Salesforce or HubSpot, segmentation, and automation workflows. Content roles may emphasize CMS publishing and on-page SEO; paid-media roles may emphasize campaign structure, budget pacing, and attribution analysis.

Finance and financial analysis

Show the model, comparison, or financial question you worked on. The O*NET financial analyst profile includes financial analysis, modeling, forecasting, and valuation. A classroom model can demonstrate a method when the project is labeled accurately.

Hard skill	When you might use it	Fictional resume bullet
Financial modeling in Excel	Connecting assumptions to projected financial statements.	Built an Excel three-statement model for a class case study, linking revenue assumptions, working capital, and cash flow across the forecast.
Budget variance analysis	Explaining differences between a plan and actual spending.	Compared monthly expenses with the student organization's budget and prepared a variance summary identifying timing differences and unplanned purchases.
Financial statement analysis	Understanding a company's financial position from reported information.	Analyzed three years of public financial statements for a course report, comparing margins, liquidity, and cash generation across two companies.
Valuation and sensitivity analysis	Exploring how a valuation changes when assumptions change.	Built a discounted cash flow model for a finance project and tested how discount-rate and growth assumptions changed the estimated valuation.

Label coursework, case competitions, and simulated portfolios clearly.

Project coordination

For project or operations coordination roles, make planning methods visible through the documents you maintained. O*NET's project management specialist profile includes schedules, costs, deliverables, and project reporting.

Hard skill	When you might use it	Fictional resume bullet
Schedule and dependency tracking	Showing which tasks rely on others before work can proceed.	Maintained a project schedule for a campus conference, tracking dependencies between venue confirmation, registration setup, and speaker communications.
Budget tracking in Excel	Comparing committed and actual costs with an approved plan.	Reconciled vendor invoices with an Excel event budget and flagged costs awaiting approval in a weekly update to the project lead.
Process mapping	Documenting steps, decisions, and handoffs in a workflow.	Mapped a volunteer onboarding process, identified duplicate information requests, and drafted a revised handoff checklist for the program coordinator.
Risk and issue tracking	Separating possible problems from issues already affecting delivery.	Maintained a project risk and issue log with owners, next actions, and review dates, escalating unresolved venue and equipment dependencies to the lead.

Identify whether you maintained the plan, coordinated a workstream, or owned delivery.

Mechanical engineering

Use the tools and engineering methods you can explain through a design, drawing, calculation, or test. O*NET's mechanical engineer profile covers design work, technical documentation, and evaluating equipment or prototypes.

Hard skill	When you might use it	Fictional resume bullet
CAD modeling in SolidWorks	Turning a component concept into an editable part or assembly.	Modeled a mounting bracket and assembly in SolidWorks for a capstone project, revising clearances after the team's fit review.
Technical drawing preparation	Communicating dimensions and manufacturing details.	Produced dimensioned drawings for a prototype housing, specifying material and hole locations and updating revisions after feedback from the campus machine shop.
Finite element analysis	Examining a model's response under stated assumptions.	Compared bracket stress and displacement in a finite element model under a specified static load and documented material, mesh, and boundary-condition assumptions.
Test planning and data analysis	Checking a prototype against defined test conditions.	Wrote a bench-test procedure for a student pump prototype, logged pressure and flow measurements, and compared results with the team's design targets.

For simulations and bench tests, state the assumptions and validation scope. A classroom simulation is not a safety certification.

Worked example: build a data analyst resume section

This separate example uses a fictional job posting and fictional project notes. It shows how to choose a short skills list and connect it to two bullets, using the same evidence throughout.

Start with the posting and project facts

The posting: An entry-level data analyst role requires SQL and Excel. Power BI and Python are preferred.

The candidate's project notes:

• Completed a course project using six months of public library loan records.
• Used SQL to join loan records with a branch reference table and summarize loans by branch and month.
• Used Excel PivotTables to cross-check the monthly totals against the source export.
• Built a Power BI dashboard with branch and month filters to display the circulation data.
• Did not use Python or measure time savings, revenue, or other business outcomes.

Choose the skills the facts support

SQL and Excel go first because the posting requires them and the notes support them. Power BI adds a supported preferred skill. Python stays out: being preferred does not create evidence that the candidate used it.

The resume section can then read:

The skills section makes the tools easy to scan; the project entry shows what the candidate did with them. No claim of time saved is needed because the notes establish the work and deliverables, not a measured business result.

Turn a skill into a bullet you can support

Use a simple structure: action + skill or method + specific work + supported result or deliverable. A result can be useful, but it does not have to be a percentage improvement.

For example, "Excel" in a skills section can become "Used Excel PivotTables to reconcile event registrations with payment records and flag unmatched entries for the student treasurer." The work and output explain what the skill means.

Before using a bullet, check four things:

1. The skill: Did you actually use that tool or method? Keep similar tools separate unless you have experience with both.
2. Your contribution: Does the verb match your role? Drafting, testing, supporting, and leading describe different responsibilities.
3. The evidence: Can you explain the work through an artifact, a specific example, or a technical discussion without sharing confidential information?
4. The result: Is every number or outcome real? If you did not measure a result, describe the deliverable rather than inventing one.

Put the skill name and the evidence in the right places

Use a skills section for a compact list of relevant capabilities. Use experience or project bullets to show the important ones in action. You do not need a separate bullet for every item in the list.

The worked example above shows the two sections together. For decisions about length and trimming, see how many skills to list on a resume.

In Simplify Resume Builder, you can edit your skills and bullets, keep different resume versions, and compare keywords with a target job description. Building, scoring, keyword matching, and exporting are free; AI rewriting and job-specific AI tailoring are part of Simplify+.

A missing-keyword suggestion is something to check against your background. Add it only if it accurately describes your experience. A score does not establish whether you meet an employer's requirements or predict an interview.

Common questions

What are good hard skills to put on a resume?

Choose skills that are relevant to the job and supported by work you can explain. Examples include SQL for querying data, CAD for modeling parts, or financial modeling for analyzing assumptions. Your target role determines which examples are useful; the tables above are starting points, not a checklist to copy.

Is Excel a hard skill?

Yes, when you can describe the work you do with it. "Excel: PivotTables and XLOOKUP" is more specific than "Microsoft Office." A bullet about reconciling records or building a model gives the reader evidence of how you used it. Do not claim advanced proficiency from a task that only involved basic data entry.

Can I list skills learned through coursework or personal projects?

Yes, if you can demonstrate them. Label the class or project, describe your own contribution, and keep the scope accurate. Completing a tutorial gives you less evidence than adapting the method to a problem you can explain, but you do not need paid work for every skill on your resume.

Do all hard-skill bullets need numbers?

No. A specific tool, task, and deliverable can demonstrate the skill without a metric. Include a number when it is accurate and adds useful context, such as the size of a dataset or the scope of a project. Do not invent time savings, revenue, or percentage improvements to make a bullet look stronger.