Quick answer: Technical skills on a resume are the specialized, job-specific abilities you need to do the work: programming languages, software platforms, lab techniques, machinery, clinical procedures, or financial tools. List the 5–10 most relevant ones in a dedicated skills section, then prove them in your experience bullets with real results.
"Technical skills" sounds like it only applies to people who own three monitors and talk about Kubernetes at dinner. It doesn't. A nurse starting an IV, an accountant reconciling ledgers in NetSuite, an electrician reading a wiring diagram, and a marketer building a Google Ads campaign all use technical skills.
This guide explains what counts, gives you a technical skills list organized by field, and shows how to build a technical skills resume section that gets past applicant tracking systems and convinces the human reading it.
What Are Technical Skills?
Technical skills are the practical, learnable abilities needed to perform specialized tasks. They're a type of hard skill, usually tied to tools, technology, methods, machinery, science, or math.
What makes a skill "technical":
- It has to be learned, through school, training, certification, or on-the-job practice
- It's specific to a job or industry
- It can be tested or demonstrated: you can write the code, run the analysis, or operate the equipment
Compare that with soft skills like communication or adaptability, which describe how you work. (See our guide to soft skills for a resume for that side of the equation.) Most good resumes show both.
Technical skills vs. computer skills vs. IT skills
These terms overlap, which causes confusion:
- Computer skills are about using computers and software, from Excel to Photoshop. We cover those in depth, including hardware and software examples by level, in our guide to computer skills for a resume.
- IT skills are a subset focused on systems, networks, security, and support.
- Technical skills is the broadest term. It includes computer and IT skills, but also non-digital expertise like welding, phlebotomy, CNC machining, or surveying.
If your job uses a specialized tool or method that took real effort to learn, it's probably a technical skill.
Why Technical Skills Matter on a Resume
- They're often the first filter. Many job postings list required tools or methods, and recruiters check for them quickly.
- Applicant tracking systems scan for them. If the posting asks for "SQL" and your resume says "databases," the software may not connect the two.
- They show you can contribute quickly. A candidate who already knows the company's tools needs less training.
- They're concrete. Unlike "hardworking," a technical skill can be checked, which makes it more credible when backed by examples.
Technical Skills List: Examples by Field
Here are examples of technical skills grouped by industry. Use them as inspiration, but always match your list to the actual job posting.
Software development and engineering
- Programming languages: Python, JavaScript, TypeScript, Java, C#, Go
- Frameworks: React, Node.js, Django, Spring Boot
- Version control: Git, GitHub, GitLab
- Testing: unit testing, integration testing, test automation
- APIs: REST, GraphQL
- DevOps: CI/CD pipelines, Docker, Kubernetes
For full examples, see our software engineer resume guide.
Data and analytics
- SQL and database querying
- Python or R for analysis (pandas, NumPy)
- Data visualization: Tableau, Power BI, Looker
- Statistical analysis and A/B testing
- Spreadsheet modeling: pivot tables, advanced formulas
- Machine learning basics: regression, classification
Cloud, IT, and cybersecurity
- Cloud platforms: AWS, Microsoft Azure, Google Cloud
- Network administration: TCP/IP, DNS, VPNs, firewalls
- System administration: Windows Server, Linux
- Identity and access management
- Security monitoring and incident response
- Help desk ticketing: ServiceNow, Jira Service Management
Engineering and manufacturing
- CAD software: AutoCAD, SolidWorks, Revit
- Technical drawing and blueprint reading
- Quality control and inspection methods
- Lean manufacturing and Six Sigma
- PLC programming
- CNC machining and equipment calibration
Healthcare and clinical
- Patient assessment and vital signs
- IV insertion and phlebotomy
- Electronic health records: Epic, Cerner
- Medical coding: ICD-10, CPT
- Medication administration
- Lab techniques: specimen processing, PCR, microscopy
Finance and accounting
- Financial modeling and forecasting
- Accounting software: QuickBooks, NetSuite, SAP
- Advanced Excel: VLOOKUP/XLOOKUP, pivot tables, macros
- Reconciliation and month-end close
- Budgeting and variance analysis
- Tax preparation software
Marketing and digital
- SEO and keyword research
- Paid ads: Google Ads, Meta Ads Manager
- Web analytics: Google Analytics
- Email platforms: Mailchimp, HubSpot, Klaviyo
- CMS: WordPress, Webflow
- Marketing automation and CRM
Design and creative
- Adobe Creative Cloud: Photoshop, Illustrator, InDesign, Premiere Pro
- Figma and prototyping
- Video editing and motion graphics
- Typography and layout
- 3D modeling: Blender, Cinema 4D
Skilled trades and operations
- Electrical wiring and code compliance
- Welding: MIG, TIG, stick
- HVAC installation and repair
- Forklift and heavy equipment operation
- Inventory and warehouse management systems
- Preventive maintenance and diagnostics
Project and product management
- Agile and Scrum
- Project tools: Jira, Asana, Microsoft Project
- Budget tracking and resource planning
- Risk management
- Product analytics and roadmapping
How to Choose Which Technical Skills to List
You likely know more tools than your resume has room for. Here's how to decide:
- Start with the job posting. Highlight every tool, language, method, or certification it mentions. Those are your priority.
- Separate must-haves from nice-to-haves. Required skills you have go first. "Preferred" skills you have come next.
- Use the exact names. Write "Microsoft Power BI" or "Power BI" if that's what the posting says, not "BI tools." Include both the acronym and full name for key terms, like "Search Engine Optimization (SEO)."
- Drop the obvious. For a senior developer, "email" and "Microsoft Word" are taken for granted. They waste space.
- Drop the outdated. Software nobody uses anymore can make your skills look dated rather than deep.
- Only list what you can discuss. If you put it on paper, you can be asked about it. Listing a programming language you touched once in 2019 is how interviews get uncomfortable fast.
Most guides suggest featuring roughly 5–10 technical skills in your skills section. Technical roles may need more, which is where grouping helps.
How to List Technical Skills on a Resume
1. Create a technical skills section
For technical roles, a dedicated section near the top (after your summary) helps recruiters spot your stack immediately. Group related skills so the list is easy to scan:
Technical Skills
Languages: Python, SQL, JavaScript
Data & BI: Tableau, Power BI, Excel (advanced)
Cloud & Tools: AWS (S3, Redshift), Git, Airflow
Methods: A/B testing, regression analysis, data modeling
For non-technical roles, a simpler list works well:
Skills: Epic EHR, IV therapy, Wound care, Patient education, Medication administration, BLS and ACLS certified
Where should the section go? For technical roles, near the top. For most other roles, after your experience.
2. Prove them in your experience section
A skills list tells recruiters what you know. Your experience bullets show what you did with it. Combine the tool with an action and a result:
- Built automated Python scripts to clean weekly sales data, saving the analytics team about 6 hours per week
- Designed Tableau dashboards used by 12 regional managers to track inventory levels in real time
- Migrated 40 internal applications to AWS, reducing hosting costs and improving uptime
- Programmed and calibrated CNC machines for a new product line with zero rework on first production run
- Charted patient care in Epic for a 28-bed medical-surgical unit with consistently accurate documentation
(These are examples. Use your own real numbers.)
3. Mention your top skills in your summary
Pick the two or three technical skills most important for the role and work them into your opening lines:
Data analyst with 4 years of experience turning messy data into business decisions using SQL, Python, and Tableau. Built reporting systems that cut month-end reporting time in half.
See our guide on how to write a resume summary for more examples.
4. Back them up with certifications and projects
Certifications (like AWS Certified Cloud Practitioner, CompTIA Security+, or a PMP) and projects give recruiters independent proof. Students and career changers especially benefit from showing skills through personal or academic projects when they don't have work experience using them yet.
Should You Show Proficiency Levels?
Sometimes. Labels can help when you have a range of experience:
Python (advanced), R (intermediate), Go (familiar)
If you do, stick to simple words: familiar, intermediate, advanced, expert. Be honest. "Expert" is a big claim, and interviewers love testing big claims.
Avoid skill bars, star ratings, and percentage graphics. They look nice in a template preview, but they don't mean much (what is "80% Excel"?), and applicant tracking systems usually can't read them.
Technical Skills for Non-Technical Jobs
Even if your job isn't "technical," you almost certainly use technical skills. Look for:
- Software specific to your field: a property management system, a point-of-sale system, a CRM, scheduling software
- Methods and procedures: inventory control, compliance processes, bookkeeping
- Equipment: registers, medical devices, machinery, tools
- Data work: tracking metrics in spreadsheets, building reports
A retail manager who lists "Shopify POS, inventory forecasting, scheduling in When I Work, Excel reporting" looks far more capable than one who lists "computers."
Technical Skills for Students and Career Changers
If you're early in your career or switching fields, you may have the skills without the job title to match. That's fine. Recruiters care where you used a skill less than whether you can actually use it.
- Students: Pull technical skills from coursework, labs, capstone projects, hackathons, and internships. "Built a class inventory app in Python and SQLite" is real experience.
- Career changers: Look for tools that carry over. A teacher who managed grades in a learning management system and built spreadsheets for tracking progress has data and software skills a training or operations role might need.
- Both: Add a Projects section to prove skills you haven't used in a paid role yet, and link to a portfolio or GitHub if your field supports it.
Our career change resume guide shows how to frame transferable skills so they read as relevant, not random.
Common Technical Skills Mistakes
- Listing everything you've ever touched. Twenty-five tools with no context reads as filler, and it buries the ones that matter.
- Being vague. "Programming" or "Microsoft" tells the reader nothing. Name the language or application.
- Keyword stuffing. Repeating "Python" eleven times won't trick anyone. ATS software looks for relevant terms, but a human reads the resume next.
- Claiming skills you can't back up. Technical interviews, coding tests, and skills assessments exist for exactly this reason.
- Forgetting to update. Your tools change faster than your job titles. Review the section every time you apply.
For more on matching keywords without overdoing it, see our resume keywords optimization guide.
How to Build New Technical Skills
If a posting keeps asking for something you don't have yet:
- Take an online course or certification in the specific tool
- Practice on a real project, even a small personal one, so you have something to point to
- Volunteer to use it at work if your current job allows
- List it honestly once you've built it: under a "Currently learning" note, in a project, or in your skills section with an accurate level
Frequently Asked Questions
What are examples of technical skills?
Examples include programming languages (Python, JavaScript), data tools (SQL, Tableau), cloud platforms (AWS, Azure), design software (Figma, Adobe Photoshop), CAD software (AutoCAD), accounting software (QuickBooks), clinical skills (phlebotomy, EHR charting), and trade skills like welding or electrical wiring.
How many technical skills should I put on my resume?
Most resumes should feature about 5–10 technical skills that match the job. Highly technical roles may list more, grouped into categories so they stay easy to scan.
Where do technical skills go on a resume?
List them in a dedicated skills section, usually after your summary for technical roles. Then show the most important ones in action within your work experience bullets and mention your top two or three in your summary.
Are technical skills the same as hard skills?
Technical skills are a type of hard skill. All technical skills are hard skills, but some hard skills (like a foreign language or typing speed) aren't usually called technical.
Should I list technical skills for a non-technical job?
Yes. Nearly every job uses some specialized software, equipment, or procedure. Listing the specific ones you know, such as a POS system or CRM, makes you look more capable and helps you match ATS keywords.
How do I show my technical skill level on a resume?
Use simple labels like "intermediate" or "advanced" next to a skill, or let your experience bullets show depth through what you built or achieved. Avoid skill bars and star ratings, which are vague and not ATS-friendly.
What technical skills are most in demand?
It depends on the industry, but skills tied to data analysis, cloud computing, cybersecurity, and AI tools come up frequently in job postings. Check postings in your target field to see what employers ask for most.
Put Your Technical Skills to Work
Matching your technical skills to each job posting and turning them into results-driven bullets takes time. Our Resume Builder helps you organize a clean technical skills section, tailor it to each role, and write experience bullets that prove what you can do.