Technical skills are the tools, languages, systems and certified methods you can operate: SQL, Epic charting, AWS, QuickBooks. Recruiters scan for them in a dedicated section, and screening software matches them word for word against the posting. Tell the generator your role and stack, and it writes the section grouped the way recruiters read it.
Technical skills are the specific, learnable abilities you use to operate tools and systems: programming languages, software platforms, lab or clinical procedures, certified methods. On a resume they live in a dedicated section of 8 to 15 skills, grouped by theme, because recruiters scan that section first to decide whether the rest of the page is worth reading.
The category matters because the words get matched literally. A hiring manager searching applications for "Terraform" or "Epic" finds the resumes that contain those exact terms. That makes technical skills different from soft skills like communication or leadership: a soft skill claimed in a list carries no information, but a technical skill is a searchable, checkable fact. List the technical ones; prove the soft ones inside your experience bullets, where they can carry numbers.
Where does the section go? For technical roles (engineering, data, IT), directly below your summary, because the stack is the first qualification screened. For every other role, after your experience section: your work history is the headline and the skills list is the index.
Six sections in the format the generator produces: grouped, specific, capped. Take the one closest to your role as a starting point, then cut anything you could not discuss in an interview and add the tools you actually run. If your role is not here, the generator above builds the standard stack for any job title.
LanguagesPython, TypeScript, SQL, Go
Frameworks and librariesReact, Node.js, Django
Cloud and DevOpsAWS (Lambda, S3), Docker, Kubernetes, Terraform, GitHub Actions
PracticesREST API design, test automation, CI/CD
LanguagesSQL, Python (pandas, NumPy)
Analytics and BITableau, Power BI, Google BigQuery, Excel (pivot tables, Power Query)
MethodsA/B testing, cohort analysis, KPI dashboard design
Search and paid mediasearch engine optimization (SEO), Google Ads, paid social (Meta, LinkedIn)
PlatformsHubSpot, Salesforce, Google Analytics 4 (GA4)
Content and emailemail automation, A/B testing, landing page optimization
Clinicalpatient assessment, medication administration, IV insertion, telemetry monitoring, wound care
SystemsEpic EHR charting, barcode medication scanning
CertificationsBLS, ACLS
SystemsQuickBooks, SAP, NetSuite, Excel (advanced formulas, macros)
ReportingGAAP financial reporting, month-end close, variance analysis
Complianceaccounts payable and receivable, audit preparation, tax filing support
SystemsWindows Server, Active Directory, Microsoft 365 administration, macOS
ToolsJira Service Management, remote desktop support, PowerShell scripting
NetworkingTCP/IP, VPN configuration, hardware troubleshooting
"Excel" on a resume tells a recruiter almost nothing, because everyone lists it. "Excel (pivot tables, VLOOKUP, Power Query)" tells them exactly which conversations you can hold. The parenthetical is the cheapest credibility upgrade on a resume: it converts a checkbox into evidence, and it matches more specific searches too, since plenty of postings ask for "pivot tables" by name.
Use it sparingly. Two or three parentheticals across the section signal depth; one on every line reads as padding. Spend them on the skills the posting cares most about.
Screening software and searching recruiters share one behavior: they look for the posting's own terms. If the job asks for "search engine optimization" and your resume says "organic growth," you have the skill and still miss the match. So when you are applying to a specific job, the posting's vocabulary wins: use its exact wording for every skill you honestly have, and spell out any abbreviation once, "search engine optimization (SEO)", so you match whichever form gets searched.
Read the posting's qualifications the way the employer wrote them: required skills are gates, preferred skills are tiebreakers. Your section should cover every required technical skill you genuinely have, in the posting's words, before it spends lines on anything else. That is exactly what the generator does when you paste a job description, and what Targeted Resume measures across your whole resume: a Relevancy Score that weights required skills above preferred ones, with every matched and missing term listed.
One honest boundary: matching means translating your real skills into the posting's vocabulary, never adding skills you do not have. Every line in the section is an interview question you are inviting. If the true answer to "walk me through how you have used it" is a weekend tutorial, the line costs you credibility everywhere else on the page. A shorter list you can defend beats a longer one you cannot.
Every slot in the section either adds evidence or dilutes it. These five show up constantly, and each one costs more than it adds. Hover them to see what a recruiter reads.
Technical skills: Microsoft WordAssumed by default for any office job. Listing it spends a slot to signal a thin toolkit., typingFiller unless the posting asks for it (transcription and data entry roles ask; almost nothing else does)., emailNot a skill anyone screens for. If you administer email systems, say the system: Microsoft 365, Google Workspace., social mediaToo vague to match any search. Name the platforms and tools you run: Meta Ads Manager, TikTok, Hootsuite., AIA field, not a skill. Name what you operate: prompt-based workflows in specific tools, scikit-learn, LLM API integration.
The pattern behind all five: they are either universal (so they carry no signal) or categories (so they match no search). Replace each with the most specific true version of itself, or spend the slot on a skill the posting actually names.
What are technical skills for a resume?
The specific, learnable abilities you use to operate tools and systems: programming languages, software platforms, clinical or lab procedures, certified methods. Examples: SQL, AWS, Epic EHR charting, QuickBooks, Google Ads, PLC programming. They differ from soft skills (communication, leadership) in that they are searchable and checkable, which is why they get their own section on the resume.
How do I list technical skills on my resume?
In a dedicated section of 8 to 15 skills, grouped by theme with short conventional labels (Languages, Systems, Certifications), using the exact wording of the job posting for any skill it names. Put the section directly below your summary for technical roles, or after your experience section for everything else. The generator on this page writes it in that format from your job title and stack.
How many technical skills should I put on my resume?
8 to 15, grouped. Fewer looks thin for a technical role; past fifteen the list reads as padding and buries the skills that matter. The cap forces the right editing question: which skills would you be glad to get an interview question about? Those stay. You can reference more tools inside your experience bullets, where each arrives with context.
What technical skills can I list without work experience?
Anything you can demonstrate, whatever the source: coursework, certifications, personal projects, volunteer work. A student who built a project in React can list React. The test is defense, not employment: if an interviewer says "walk me through how you used it" and you have a real answer, it belongs. Pair listed skills with a project section that shows them in use.
Are certifications technical skills?
They are proof of technical skills, and they belong in the section, usually as their own group (Certifications: AWS Solutions Architect, CompTIA A+, BLS, ACLS). A certification the posting names is one of the strongest exact-match keywords a resume can carry, because it is binary: you either hold it or you do not.
Should technical skills match the job description?
Yes, in the posting's own words, for every skill you honestly have. Required skills are gates and preferred skills are tiebreakers, so cover the required ones first. Spell out abbreviations once, like "search engine optimization (SEO)", to match both forms. Matching means translating your real skills into the posting's vocabulary, never adding skills you do not have.
Is this technical skills generator free?
Yes. Enter your job title, optionally your stack and the job description, and it writes a grouped technical skills section free: 3 to 5 groups, 8 to 15 skills, with the posting's wording when you paste one. The output is yours to copy, prune, and paste into your resume.
Upload your resume for a free review: keyword and skills coverage, ATS parse checks, and line-by-line feedback from 30+ recruiter checks, in about 30 seconds.
Get my free resume review »