Technical Skills for a Resume: Examples by Field
Technical (hard) skills by field, how to choose the ones that matter for a role, how to group and describe levels, and how to prove them with achievements.
Key takeaways
- Technical skills are specific, teachable abilities and tools that an employer can test.
- List the ones the target role asks for and you can use well, grouped by type.
- Describe levels in words or credentials, not bars or percentages.
- Prove the most important ones in achievement bullets; that is where they carry weight.
Technical skills, also called hard skills, are the specific abilities and tools a job requires: a programming language, an accounting system, a design tool, a data method. They are easier to verify than soft skills, which is why recruiters search for them and why employers often test them. This guide gives examples by field and shows how to present them well.
For the broader picture, including soft skills and remote skills, see skills to put on a resume.
Technical skills vs soft skills
| Technical (hard) skills | Soft skills | |
|---|---|---|
| What they are | Specific, teachable abilities and tools | How you work with people and problems |
| Examples | SQL, Excel, Figma, Salesforce, bookkeeping, Spanish | Communication, leadership, adaptability |
| How they are checked | Tests, certifications, work samples | Interviews, references, examples |
| Where on the resume | Skills section and bullets | Bullets and summary only, as evidence |
Examples by field
Software engineering
Programming languages (Python, TypeScript, Java, Go), frameworks (React, Django, Spring), databases (PostgreSQL, MongoDB), cloud platforms (AWS, Azure, Google Cloud), testing, version control (Git), CI/CD, containerisation (Docker, Kubernetes), API design.
Data and analytics
SQL, spreadsheets (advanced Excel or Google Sheets), Python or R, BI tools (Power BI, Tableau, Looker), statistics, data cleaning, A/B testing, data warehouses (BigQuery, Snowflake).
Marketing
Web analytics (Google Analytics), search engine optimisation, paid search and social platforms, email and marketing automation (HubSpot, Mailchimp), content management systems, copywriting, basic design tools.
Sales and customer success
CRM software (Salesforce, HubSpot), pipeline management, sales engagement tools, product demonstrations, forecasting, contract negotiation, help-desk software (Zendesk, Intercom) for support roles.
Finance and accounting
Accounting software (Xero, QuickBooks, SAP), financial modelling, budgeting and forecasting, financial reporting standards, reconciliations, tax compliance, advanced spreadsheets.
Design
Design and prototyping tools (Figma, Adobe Creative Suite), user research methods, usability testing, design systems, accessibility standards, basic HTML and CSS.
Administration and operations
Office suites (Microsoft 365, Google Workspace), project tools (Asana, Jira, Trello), scheduling and booking systems, data entry with accuracy, process documentation, basic bookkeeping.
IT support and security
Operating systems, networking basics, device management, ticketing systems, identity and access management, security monitoring tools, scripting (PowerShell, Bash).
Human resources and recruiting
Applicant tracking systems (Greenhouse, Workday), HR information systems, payroll software, employment law basics for your country, interview scheduling tools, people analytics.
Logistics and supply chain
Warehouse and transport management systems, ERP software (SAP, Oracle), inventory planning, demand forecasting, import and export documentation.
Writing and content
Content management systems (WordPress and similar), SEO tools, style guides, editing and proofreading, basic HTML, documentation tools.
How employers test technical skills
Technical skills are the part of your resume most likely to be checked directly:
- Practical tests: a coding exercise, a spreadsheet task, a design brief or a writing test.
- Technical interviews: questions about how you used a tool and why you made certain choices.
- Certifications: some roles require named credentials before an interview.
- Portfolios and work samples: common for design, writing and engineering.
List only what you can demonstrate under those conditions. It is better to show fewer skills strongly than many weakly.
Keep your skills current
Tools change quickly. Review your list every few months: add tools you now use regularly, remove ones you no longer use, and check that names match current versions and how employers write them. If a listing names a newer version of a tool you know, say how your experience transfers.
How to choose which to list
- Collect several listings for your target role and note the technical skills that repeat.
- Keep the ones you can use well enough to be tested on.
- Put the role’s most important skills first.
- Drop outdated tools and basics everyone has, unless the listing asks for them.
Use the employer’s exact names for tools; see resume keywords.
How to format a technical skills section
Group skills by type so the section is easy to scan:
Skills
Languages: Python, SQL, TypeScript
Data and BI: pandas, dbt, Looker, BigQuery
Tools: Git, Docker, Airflow
Spoken languages: English (fluent), Portuguese (native)
Technical roles may list more tools than others, but keep the list to what you would discuss confidently in an interview.
Describing skill levels
Avoid bars, stars and percentages. Instead:
- use plain words sparingly: "advanced", "working knowledge", "basic", and only when you can justify them;
- name certifications with issuer and year;
- let achievements show depth: "Designed the data model for…" shows more than "SQL (expert)".
Prove them in your bullets
A skill that appears inside an achievement is far more convincing than the same skill in a list. Compare:
- List: "Power BI".
- Bullet: "Built the monthly finance dashboard in Power BI, replacing a manual report and saving the team about a day each month."
Make sure your three or four most important technical skills appear in bullets like this. See how to write resume achievements.
Skills from courses and projects
If you learned a skill through a course or personal project, list it, and add a project that shows it in use. "Python (pandas): analysed a public housing dataset and published a written report" is much stronger than a certificate name alone. Early-career candidates can use a Projects section; see an entry-level resume.
Questions people ask
Should I list Microsoft Office or Google Workspace?
Only when the role relies on them, and then be specific: "advanced Excel (pivot tables, lookups, macros)" says something; "Microsoft Office" on its own usually does not.
Do non-technical roles need a technical skills section?
Most roles use some specific tools: a CRM for sales, a help desk for support, a booking system for administration. Listing the ones the employer uses shows you can start quickly.
Should I include tools I used years ago?
Only if they are still relevant and you could use them again with little refreshing. Otherwise leave them out.
Next steps
Rebuild your skills section with grouped, role-relevant technical skills, then check that the most important ones appear in your bullets. For the rest of the document, see how to write a resume. To see which skills employers in your field ask for right now, browse current openings.