Technical Skills for Your Resume, by Field

Technical skills for a resume are the ones a hiring manager scans for first, because they translate directly into whether you can start without training. The mistake most people make is listing breadth where depth is what is being assessed.

Name the specific thing

Categories tell a reader nothing. Specifics remove a training cost.

Weak: Programming, databases, cloud Strong: Python, PostgreSQL, AWS (EC2, S3, Lambda)

The second version answers the question the first one raises. Where a platform has meaningfully distinct parts, naming them is worth the characters.

Stacks by field

Software engineering. Languages (Python, JavaScript, TypeScript, Go, Java) · Frameworks (React, Django, Spring, Node.js) · Data (PostgreSQL, Redis, MongoDB) · Infrastructure (Docker, Kubernetes, Terraform, AWS or GCP) · Practice (Git, CI/CD, unit testing, code review, system design)

Data and analytics. SQL · Python (pandas, NumPy) or R · Visualisation (Tableau, Power BI, Looker) · Warehousing (BigQuery, Snowflake, Redshift) · Statistics (regression, A/B testing, forecasting) · dbt · Airflow

Engineering and manufacturing. CAD (AutoCAD, SolidWorks, Revit) · FEA and simulation · GD&T · CNC programming · PLC and SCADA · Lean and Six Sigma methods · Materials testing · Technical drawing standards

Healthcare technical. Charting systems (Epic, Meditech, Cerner) · Diagnostic equipment operation · Telemetry · Infusion pumps · Point-of-care testing · Sterile processing · Coding standards (ICD, CPT)

Finance technical. Financial modelling · Valuation methods · SQL · Advanced Excel (Power Query, VBA) · ERP systems (SAP, NetSuite, Oracle) · Bloomberg or Refinitiv · Reconciliation and consolidation

IT and infrastructure. Networking (TCP/IP, DNS, VLANs, firewalls) · Windows Server and Active Directory · Linux administration · Virtualisation (VMware, Hyper-V) · Endpoint management · Backup and recovery · Ticketing systems

Laboratory and science. Assay development · Chromatography (HPLC, GC) · PCR and qPCR · Mass spectrometry · Cell culture · GLP and GMP practice · Statistical software (SPSS, Prism)

Depth signals belong in the bullets

A stack list establishes range. It cannot establish depth, and depth is what separates two candidates with the same list.

List: Kubernetes Depth: Migrated fourteen services to Kubernetes over two quarters and cut deployment time from a morning to under ten minutes.

The bullet does the work the list cannot. Pick your two or three most important technologies and make sure each appears inside an experience bullet with real scope attached.

Certifications go separately

Give them their own short section with the issuing body and the year:

Certifications AWS Solutions Architect Associate (Amazon, 2024) · CompTIA Security+ (2023) · Six Sigma Green Belt (ASQ, 2022)

Include the year even when it is not recent. A reader would rather see a date than wonder about one, and some certifications carry renewal cycles a hiring manager will check.

Versions and recency

Name a version only where it genuinely matters, which is less often than people assume. It matters for a platform with a hard migration between major versions; it rarely matters for a language.

Recency matters more. A stack that stops several years ago quietly signals when you last worked hands-on, so if you have kept current in a technology, make sure the experience bullet showing it is a recent one.

Related

For general software literacy rather than specialist stacks, see computer skills. For the rules behind the section, see the skills section guide, and for layout see formatting your skills section. For the hard versus soft distinction, see hard skills.

Our resume keyword scanner shows which of a posting’s named technologies are missing from your page.

Name the specific tool, prove two of them in bullets, and keep certifications separate. You can check your skills section against a real posting.