By Peter Miller · Published September 27, 2026 · Last updated: September 27, 2026
9 min read
Most skills cheat sheets online read like vocabulary dumps. You don't need another generic list of "communication" and "teamwork" dressed up as technical skills. You'll need tool names that match tonight's posting and proof lines a recruiter can find in six seconds.
Myth: stuff the Skills section with every platform you've touched and the ATS will score you high. Reality: parsers map the block, then humans search Experience for the same string. No matching bullet, no trust. Before you rewrite, check your resume for free against the job description. If Python is in Skills but nowhere under your last role, you're not done.
Below: 150+ tools grouped by industry, five before-and-after proof rewrites, and a copy-paste bullet skeleton. Open the posting. Highlight required tools. Mirror them in Skills and in one dated bullet each.
Quick Wins
- Pull five required tools from the posting into Skills and one proof bullet each.
- Spell software names exactly as the employer lists them.
- Run a free ATS check on the same PDF you will submit.
What counts as proof in screening
The Skills list does not get you screened in. The bullet that repeats the skill does. Upload parsers read a plain header and comma-separated tools. Recruiters open the PDF and ctrl-f the posting keywords inside Experience. Same tool in both places wins. Tool only in Skills reads like a keyword dump.
Hard skills are teachable and testable: software, equipment, methods, licenses, languages used at work. Soft skills matter later in interviews. On paper, lead with what the posting names in the requirements block.
Format rules that keep tools readable in Workday and Greenhouse live in Workday resume format that parses cleanly . Single column. Plain text Skills header. Month Year dates on every role. Save the two-column Canva layout for LinkedIn, not the upload.
Placement and checklist detail for the Skills block itself sits in how to list skills on a resume . This page is the examples and proof layer. Read both when you're rebuilding from a posting tonight.
150+ hard skills examples by industry
Copy tool names that match your background and the posting. Do not paste the whole industry list. Recruiters smell unfocused files. Eight to fifteen defensible tools beat forty aspirational ones.
Technology and software
Python · JavaScript · TypeScript · React · Node.js · SQL · PostgreSQL · MongoDB · AWS · Azure · Docker · Kubernetes · Git · CI/CD · REST APIs · GraphQL · Linux shell · Terraform · Jira · Figma (handoff)
Data and analytics
Excel (PivotTables, XLOOKUP) · Google Sheets · SQL · Python (pandas) · R · Tableau · Power BI · Looker · Snowflake · BigQuery · dbt · ETL pipelines · A/B testing · Google Analytics 4 · Mixpanel
Healthcare and clinical
Epic · Cerner · MEDITECH · eMAR · ventilator management · IV therapy · wound care · ACLS · BLS · phlebotomy · sterilization · HIPAA documentation · patient triage · telemetry · ICD-10 coding · medical billing (CPT)
Finance and accounting
GAAP · SOX controls · month-end close · accounts payable · accounts receivable · general ledger · QuickBooks · NetSuite · SAP · Oracle Financials · financial modeling · variance analysis · audit prep · tax provision · Excel macros
Marketing and sales
Google Ads · Meta Ads · SEO · SEM · HubSpot · Marketo · Salesforce CRM · outreach sequences · pipeline forecasting · contract negotiation · SPIN selling · trade show lead capture · Canva · Adobe Creative Cloud · Mailchimp
Operations and supply chain
Six Sigma · Lean · Kaizen · WMS · TMS · inventory cycle counts · demand planning · S&OP · ISO 9001 · OSHA recordkeeping · forklift operation · pallet jack · RF scanning · SAP MM · NetSuite inventory
Engineering (mechanical, civil, electrical)
AutoCAD · SolidWorks · Revit · MATLAB · ANSYS · PLC programming · HVAC design · structural load calculations · GD&T · CNC programming · PCB layout · Arc Flash analysis · PE stamp coordination · Bluebeam · Primavera P6
Trades and construction
OSHA 10 · OSHA 30 · blueprint reading · electrical wiring (NEC) · conduit bending · welding (MIG/TIG) · HVAC install · plumbing rough-in · carpentry framing · drywall · tile · excavation · scissor lift · boom lift · site safety audits
Customer service and support
Zendesk · Salesforce Service Cloud · Freshdesk · Intercom · phone queue management · chat support · SLA adherence · CSAT surveys · knowledge base authoring · escalation tiers · WFM adherence · bilingual support (specify language)
Creative and design
Adobe Photoshop · Illustrator · InDesign · Premiere Pro · After Effects · Figma · Sketch · UX wireframing · brand guidelines · typography · color correction · photo retouching · motion graphics · HTML/CSS basics · accessibility (WCAG)
That is 140+ named tools, methods, and certifications across eleven fields. Your file should name the subset you can defend on a call, not the whole grid.
Proof bullets: five before-and-after rewrites
I've screened stacks of these in Workday and Greenhouse, and the file that wins lists the tool once in Skills, then proves it in the first eight words of a dated bullet under the right employer.
Swap your details. Keep tool names spelled exactly like the posting. Numbers below are résumé illustrations, not market claims.
Software engineer: Python and React
Before: Skills: Python, React, AWS, Docker. Experience: Built features for the web app.
After: Skills: Python · React · AWS · Docker · PostgreSQL · Git. Experience: Rebuilt checkout API in Python and React on AWS, cutting failed payments 11% in Q3 for 40k weekly orders.
Marketing coordinator: HubSpot and GA4
Before: Skills: HubSpot, Google Analytics, social media. Experience: Managed campaigns and tracked results.
After: Skills: HubSpot · GA4 · Google Ads · Canva. Experience: Ran HubSpot nurture flows and GA4 event tagging for three product launches, lifting MQL-to-SQL rate from 18% to 24% in two quarters.
Registered nurse: Epic and eMAR
Before: Skills: Epic, patient care, teamwork. Experience: Provided excellent nursing care on a busy unit.
After: Skills: Epic · eMAR · ACLS · wound care · telemetry. Experience: Managed Epic eMAR and telemetry for 1:4 assignments on a 32-bed med-surg unit, precepted four orientees on bar-code med admin.
Warehouse supervisor: WMS and forklift
Before: Skills: leadership, WMS, forklift. Experience: Supervised warehouse team and hit KPIs.
After: Skills: Manhattan WMS · RF scanning · forklift · OSHA recordkeeping · Lean. Experience: Led 22 pickers on Manhattan WMS with RF scanning, held mis-pick rate under 0.4% through two peak seasons.
Financial analyst: Excel and Power BI
Before: Skills: Excel, Power BI, financial analysis. Experience: Prepared reports for leadership.
After: Skills: Excel (macros) · Power BI · NetSuite · GAAP · variance analysis. Experience: Built Power BI variance packs from NetSuite GL feeds in Excel, delivered board-ready summaries every Month-end close within two business days.
Notice the pattern: tool in the first clause, scope in the middle, outcome at the end. Soft skills show up as the work, not as adjectives floating alone.
Copy-paste proof skeleton
Paste under your current job. Replace bracketed fields. Repeat for each posting keyword you listed in Skills.
Proof bullet skeleton
[Primary tool from posting] + [task you owned] + [scope: team size, volume, module, unit] + [outcome: time saved, error cut, revenue, compliance window].
Example fill: Salesforce reporting for 12 reps, rebuilt pipeline dashboard, cut weekly forecast prep from 6 hours to 90 minutes.
Skills line mirror: Salesforce · SOQL reports · pipeline forecasting
Match tools before you upload
Highlight required tools in the posting. Add them to Skills. Rewrite one bullet per tool under the job where you used it. Then run a free ATS check on the same PDF you will submit. If the checker finds a keyword only in Skills, you still owe a proof bullet.
When the posting is a stretch but you want a sanity check on fit, score your job match before you spend an hour tailoring. This won't turn a missing license into a qualification. It stops you from uploading a generic Skills dump to a specialist req.
If the role asks for a cover letter, generate a cover letter that matches the same job title and dates on your resume before you upload.
Pick tools and prove them tonight
Named tools are only useful when they match the posting and show up twice: once in Skills, once in a dated bullet with scope. Grab eight to fifteen items from the lists above, rewrite five proof lines using the before-and-after pattern, and drop anything you cannot defend on a call.
Open the job description. Highlight required platforms. Paste the proof skeleton under your current role. Parse the file before you hit submit.
For interview follow-through once the resume lands, pair this with how to answer where you see yourself in five years without sounding scripted. Different stage, same rule: specifics beat generic lists.
Frequently asked questions
Hard skills are teachable tools, methods, and platforms: Python, Epic, GAAP reconciliation, forklift operation, Salesforce reporting. List eight to fifteen that match the posting, then repeat each high-priority tool in an Experience bullet with scope and an outcome. The list helps parsers map keywords. The bullet is what a recruiter trusts on a phone screen.
Aim for eight to fifteen relevant hard skills for most corporate roles. Specialists can go narrower. Generalist IC roles can go slightly wider if every item is defensible on a call. If a skill only lives in the Skills block and never appears under a job, cut it or add a proof bullet before you upload.
Use a plain-text Skills or Technical Skills header in the main column for US corporate uploads. Put the same posting keywords inside Experience bullets under Month Year job rows. Do not hide tools in a sidebar, icon row, or proficiency bar. Workday and Greenhouse read the main column first.
Keep the Skills block mostly hard: software, equipment, methods, certifications, languages at professional level. Soft skills belong in bullets when the posting names them, such as cross-functional communication proved by a stakeholder outcome. Mixing soft adjectives into a Technical Skills list reads like padding and does not help ctrl-f screening.
Use scope the role actually had: ticket volume handled, modules configured, beds covered, SKUs managed, reports delivered on cadence. Numbers inside a sample bullet illustrate format, not industry statistics. If you lack a metric, name the tool, the task, and the audience: built Looker dashboards for four product leads, weekly refresh.