Resume Skills Section: Skill Lists for 12 Jobs, Plus How to Format Them

Updated August 17, 2026 · 15 min read

A resume skills section should list 8-15 hard skills (software, tools, certifications, methodologies) grouped into 2-4 labeled clusters and ordered by relevance to the posting. Soft skills belong in experience bullets, demonstrated at scale. Never use skill bars: parsers cannot read graphics.

The skills section is the most mechanically important and most commonly botched part of a resume. Mechanically important because it's built for exact-match database searches: when a recruiter filters 400 candidates by 'QuickBooks' or 'phlebotomy', this section decides whether you exist in the results. Commonly botched because people fill it with unverifiable adjectives, decorative skill bars, and software nobody filters on.

This guide covers the rules first (what belongs, what doesn't, how to group and format), then gives you working skill lists for 12 common jobs: the hard skills recruiters filter on, the soft skills worth proving in bullets, and the exact keyword forms tracking systems match. Use your job's list as a starting inventory, keep only what you genuinely have, and order it against the posting in front of you.

What's the difference between hard skills and soft skills?

Hard skills are specific, learnable, verifiable capabilities: software, tools, languages, methodologies, certifications, equipment, technical procedures. They're what recruiters filter on, because 'knows Excel pivot tables' is binary in a way 'good communicator' is not. The skills section exists for them.

Soft skills like leadership, communication, and adaptability are real and employers want them, but a self-assessed list of them convinces no one. 'Leadership' as a line item is a claim; 'led a 6-person crew through a hospital wing build-out, zero recordable incidents' is proof. Soft skills belong inside experience bullets, demonstrated at a specific scale, where they're checkable.

The practical split: your skills section is a tight list of hard skills; your bullets carry the soft skills implicitly. The one exception is genuinely screenable human capabilities with a hard edge: spoken languages with proficiency levels ('Spanish, professional fluency') earn a place in the section because recruiters filter on them like hard skills.

What earns a spot on the list?

Every listed skill should pass three tests: you could discuss it in an interview tomorrow, someone hiring for your target role might search for it, and it isn't assumed at your level. Applying those tests:

  • Include: the tools and platforms your target postings name (CRM, EHR, WMS, design suites, programming languages), methodologies with currency (Agile, Lean, GAAP), equipment and procedures for hands-on fields, and licenses or certifications if they don't have their own section.
  • Cut skills that are table stakes. 'Microsoft Word', 'email', and 'internet research' on an experienced professional's resume signal a padded list, and they dilute the skills that matter.
  • Cut the obsolete. Software nobody's deployed in a decade dates you worse than an old graduation year.
  • Cut vague virtues. 'Problem-solving', 'multitasking', 'work ethic': these are soft-skill adjectives wearing a list format; move the evidence into bullets.
  • Aim for 8-15 entries. Fewer looks thin; many more reads as indiscriminate. Depth signals come from bullets, not list length.

How should you format the skills section?

A flat alphabetical pile of fifteen skills makes the reader do the sorting. Group instead, with two to four labeled clusters that match how your field thinks: a nurse might use 'Clinical' and 'Systems'; an accountant 'Accounting' and 'Software'; a developer 'Languages', 'Frameworks', and 'Infrastructure'. Group labels also parse as context, which helps both the database and the skimmer.

Within groups, order by relevance to the target posting, not alphabet and not personal pride. The skill their job description names in the first requirements line goes first in your list. This ordering is re-done per application; it's one of the five moves in the fifteen-minute tailoring routine.

Write each skill in the form recruiters search: exact product names ('Salesforce', not 'CRM software'), and both spelled-out and abbreviated forms once each across the resume for terms that have both ('electronic health records (EHR)'). The mechanics of matching are covered in the resume keywords guide.

Two before-and-after rewrites show the difference the formatting makes:

Before and after: an administrative resume

Before: 'Skills: Microsoft Office, communication, organization, multitasking, teamwork, fast learner, typing, customer service, scheduling.' Nine entries, three of them searchable, none of them specific. A recruiter filtering on 'Concur' or 'multi-line phones' finds nothing.

After: 'Office systems: Microsoft 365 (Excel, Outlook, Teams), Concur, DocuSign, Calendly. Operations: executive calendar management, domestic and international travel booking, expense reporting, meeting minutes. Front office: multi-line phone systems, visitor management, vendor coordination.' Twelve entries in three labeled groups, every one filterable, and the soft skills moved to bullets where they can carry numbers.

Before and after: a warehouse resume

Before: 'Skills: hardworking, reliable, forklift, teamwork, lifting, attention to detail, warehouse experience.' The only searchable term is 'forklift', and it's buried between adjectives.

After: 'Equipment: sit-down and stand-up forklift (certified), electric pallet jack, RF scanners. Systems: SAP EWM, Manhattan WMS, cycle counting. Compliance: OSHA 10, hazmat handling awareness, lockout-tagout trained.' Ten entries, three groups, and the certifications recruiters actually filter on are visible in one glance. The warehouse worker resume example shows the whole page built this way.

Before and after: a sales resume

Before: 'Skills: sales, negotiation, communication, relationship building, Microsoft Office, closing deals, motivated.' Seven entries and only one ('negotiation') a recruiter might filter on, drowned by claims the bullets should be proving.

After: 'Sales systems: Salesforce, Outreach, LinkedIn Sales Navigator, CPQ. Motion: B2B prospecting, discovery calls, product demos, contract negotiation. Track record: quota attainment history detailed below.' The last line does something clever: it points the skimmer to the bullets where '114% of quota' lives, because attainment is proof, not a skill.

Skills lists for 12 common jobs

Each list below is an inventory to select from, not a block to paste whole: keep what you genuinely have, cut the rest, and reorder against the posting. Hard skills go in the section; the soft skills named for each job are the ones worth proving in your bullets. Full worked pages for these roles, with the skills section in place, live in the resume examples library.

Registered nurse

  • Hard skills: medication administration, IV insertion and management, patient assessment, telemetry monitoring, wound care, Epic, Cerner, electronic health records (EHR), medication reconciliation, patient and family education, HIPAA compliance, BLS, ACLS.
  • Soft skills to prove in bullets: calm escalation handling, interdisciplinary communication, precepting and mentoring, prioritization under load.
  • Keyword forms that match filters: 'registered nurse (RN)', 'BSN', unit names spelled out ('medical-surgical (med-surg)', 'intensive care unit (ICU)'), and certifications by exact acronym.

Software engineer

  • Hard skills: the languages you actually ship (Python, TypeScript, Go, Java), frameworks (React, Node.js, Django), PostgreSQL or the database you run, AWS or GCP services by name, Docker, Kubernetes, CI/CD (GitHub Actions, Jenkins), Git, REST and GraphQL API design, unit and integration testing.
  • Soft skills to prove in bullets: code review culture, incident response, cross-team design collaboration, mentoring juniors.
  • Keyword forms that match filters: exact stack tokens ('Node.js', not 'Node'), 'CI/CD', 'Go (Golang)' to catch both searches, and cloud services at the product level ('AWS Lambda', 'S3').

Data analyst

  • Hard skills: SQL, Excel (pivot tables, Power Query, VLOOKUP/XLOOKUP), Tableau, Power BI, Python (pandas) or R, dbt, Google Analytics 4 (GA4), A/B testing, data cleaning and validation, dashboard design, stakeholder reporting.
  • Soft skills to prove in bullets: translating analysis for non-technical audiences, requirements gathering, skepticism about dirty data.
  • Keyword forms that match filters: 'SQL' appears in nearly every posting and every search; name the visualization tool exactly ('Power BI', 'Tableau'), and write 'Google Analytics 4 (GA4)' once.

Project manager

  • Hard skills: project scheduling, budget management, risk and issue tracking, stakeholder management, Agile and Scrum, Waterfall, Jira, MS Project, Asana or Smartsheet, resource planning, vendor management, status reporting, PMP or CAPM if held.
  • Soft skills to prove in bullets: running meetings that end on time, delivering bad news early, negotiating scope without burning relationships.
  • Keyword forms that match filters: 'Project Management Professional (PMP)' spelled out once, 'Agile' and 'Scrum' as separate tokens, and the domain qualifier recruiters add ('IT project manager', 'construction project management').

Accountant

  • Hard skills: general ledger (GL) accounting, month-end close, account reconciliation, accounts payable (AP), accounts receivable (AR), GAAP, financial reporting, NetSuite, QuickBooks, SAP, advanced Excel, fixed assets, sales and use tax, audit support.
  • Soft skills to prove in bullets: deadline reliability across close cycles, documentation discipline, cross-department follow-through.
  • Keyword forms that match filters: 'certified public accountant (CPA)' exactly, 'month-end close' as a phrase, and the ERP by product name; 'accounting software' matches nothing.

Customer service representative

  • Hard skills: Zendesk, Salesforce Service Cloud, Five9 or comparable phone systems, live chat support, ticket triage, order management, returns and refunds processing, CRM data entry, knowledge-base authoring, CSAT and handle-time metrics.
  • Soft skills to prove in bullets: de-escalation, empathy under volume, first-contact ownership, staying accurate at pace.
  • Keyword forms that match filters: 'customer service' and 'customer support' both appear in searches; carry both across the resume. Name the ticketing system exactly.

Sales representative

  • Hard skills: prospecting and cold outreach, discovery calls, product demos, pipeline management, Salesforce or HubSpot CRM, quota attainment tracking, territory planning, contract negotiation, CPQ tools, LinkedIn Sales Navigator.
  • Soft skills to prove in bullets: resilience through rejection cycles, listening past the first objection, disciplined follow-up.
  • Keyword forms that match filters: 'B2B sales' or 'B2C' as the posting frames it, 'quota' with your attainment number nearby, and 'Salesforce' spelled exactly. The sales representative example shows the pairing of skills and quota bullets.

Marketing manager

  • Hard skills: campaign planning, Google Ads, Meta Ads, SEO, email marketing (HubSpot, Klaviyo, Marketo), marketing analytics (GA4, Looker Studio), content strategy, marketing automation, budget management, CRM segmentation, A/B testing, webinar programs.
  • Soft skills to prove in bullets: brief-writing that creatives can execute, defending budget with revenue numbers, running agencies without babysitting them.
  • Keyword forms that match filters: 'search engine optimization (SEO)' once, then 'SEO'; 'demand generation' if you're in B2B, 'lifecycle' or 'CRM marketing' if in B2C; platforms by exact name.

Executive assistant

  • Hard skills: executive calendar management, travel planning (domestic and international), expense reporting (Concur, Expensify), board meeting preparation, Microsoft 365, Google Workspace, DocuSign, event coordination, gatekeeping and inbox management, meeting minutes.
  • Soft skills to prove in bullets: discretion with sensitive information, anticipating needs before they're voiced, staying unflappable when the schedule detonates.
  • Keyword forms that match filters: 'executive assistant (EA)', 'C-suite support', and the specific tools; 'calendar management' is a real search phrase, 'organized' is not. Compare the executive assistant example.

Electrician

  • Hard skills: conduit bending and installation, panel installation and upgrades, blueprint and schematic reading, NEC code compliance, troubleshooting and diagnostics, low-voltage systems, PLC basics, lighting retrofits, journeyman or master license, OSHA 10/30.
  • Soft skills to prove in bullets: jobsite coordination with other trades, apprentice supervision, inspection-ready documentation.
  • Keyword forms that match filters: license level plus state ('journeyman electrician, Texas'), 'National Electrical Code (NEC)' once, and voltage classes the posting names ('480V three-phase').

Warehouse worker

  • Hard skills: forklift operation (sit-down, stand-up, reach truck; note certification), electric pallet jack, RF scanning, pick-pack operations, cycle counting, shipping and receiving, WMS platforms (SAP EWM, Manhattan), inventory control, loading dock safety, hazmat awareness.
  • Soft skills to prove in bullets: attendance reliability, pace with accuracy, shift-lead coverage when asked.
  • Keyword forms that match filters: 'forklift certified' as a phrase, the WMS by name, and 'order picking' plus your rate ('120 picks per hour at 99.8% accuracy') in a bullet directly below.

Teacher

  • Hard skills: lesson planning, differentiated instruction, classroom management, IEP and 504 implementation, formative and summative assessment, Google Classroom, Canvas or Schoology, parent communication, state standards alignment, ESL/ELL strategies, current state certification with grade band.
  • Soft skills to prove in bullets: de-escalating behavior without losing the room, collaborating in grade-level teams, communicating hard news to families with care.
  • Keyword forms that match filters: certification exactly as the state names it, grade band ('K-6', '7-12'), subject endorsements, and 'Individualized Education Program (IEP)' once. The teacher resume example shows placement.

Medical assistant

  • Hard skills: patient rooming and intake, vital signs, phlebotomy and specimen collection, EKG administration, injections and immunizations, EHR charting (Epic, Athenahealth, eClinicalWorks), prior authorizations, insurance verification, scheduling, sterilization and instrument prep, CCMA or RMA certification.
  • Soft skills to prove in bullets: patient reassurance, provider hand-off precision, keeping the flow moving when the schedule slips.
  • Keyword forms that match filters: 'certified medical assistant (CMA/CCMA)' with the credentialing body, the EHR by exact name, and 'front office' or 'back office' as the posting splits duties. See the medical assistant example.

Should certifications go in the skills section?

If you hold one or two certifications, listing them as a labeled cluster inside the skills section works fine ('Certifications: PMP, Lean Six Sigma Green Belt') and keeps the page compact. Once you hold three or more, or work in a field where the credential is the screen (nursing, accounting, trades, transportation), give certifications their own section under its own conventional heading, placed where the recruiter's eye lands first.

Either way, write each credential in its exact official form plus the acronym, with the issuing body and year where the field expects them: 'Project Management Professional (PMP), PMI, 2024'. Credential filters are the least forgiving matchers in the entire system, and a paraphrased certification name is a missed filter you'll never know about.

Skill bars, ratings, and other self-sabotage

Skill bars, the four-of-five dots next to 'Excel', fail on every axis at once. Parsers can't read graphics, so the skill may not exist in the database at all. Recruiters can't calibrate them: four dots against what scale, rated by whom? And they force a lose-lose disclosure: five dots invites the hardest possible interview question, three dots advertises mediocrity you didn't need to volunteer.

Text-based self-ratings ('Advanced Excel', 'Expert-level Python') are milder versions of the same problem, defensible only where the field has real rating conventions, language proficiency scales for instance. Elsewhere, drop the adjective and let scope carry the signal: if your bullets show you built financial models in Excel for a 200-store chain, nobody needs the word 'advanced'.

The strongest proficiency signal available is a bullet that uses the skill at scale with an outcome. The skills section gets you found; the bullet that says 'automated inventory reconciliation in Excel, cutting month-end close by two days' gets you believed. Every skill in your top group deserves one such appearance. That pairing, list plus evidence, is the whole architecture.

Where is the honesty line?

The skills section is a set of promises collected on within fifteen minutes of a phone screen starting. The line to hold: list what you could use on the job with normal ramp-up, not what you once watched a tutorial about. 'I used it in one project two years ago and could get current fast' is listable; 'I know what it is' is not.

Aspirational stuffing has a specific failure mode beyond embarrassment: interviewers often probe your weakest claimed skill first, precisely because it's the most informative question. One exposed bluff reframes every honest line on the page.

If you're building toward a skill the postings demand, do it honestly: finish the certificate and list the credential, or build the project and list it with the project. That's the standard path for thin or transitioning resumes, mapped in the no-experience guide and the career change guide.

Where should the skills section sit on the page?

Placement follows the same logic as everything else: proximity to the top tracks how central skills are to the screen. For most experienced professionals, the skills section sits after experience. The work history is the stronger argument, and the list plays supporting reference. Keep it above education, and keep it on page one if the resume runs two pages.

Three cases move it up. Technical roles, where the stack is the first thing both the recruiter and the hiring manager check; developers routinely place grouped skills directly under the summary. Career changers, whose hybrid structure leads with skills precisely because the job titles below point the wrong way. And heavily credentialed fields, where a combined skills-and-certifications block up top answers the screening question before it's asked. Wherever it sits, the section should be findable in one second under a conventional heading. 'Skills' parses and scans; 'Core Competencies' is tolerable; 'My Toolbox' costs you both readers. Every ATS-Verified template renders skills as plain text under a conventional heading for exactly this reason.

The skills section checklist

  1. Hard skills only, 8-15 entries, every one interview-defensible
  2. Grouped into 2-4 labeled clusters that match your field's mental model
  3. Ordered by relevance to the current posting, re-sorted per application
  4. Exact product and credential names, spelled-out plus abbreviated forms covered once each
  5. No skill bars, no self-ratings, no assumed-at-your-level software, no virtue adjectives
  6. Each top-group skill also appears in one experience bullet with scale and outcome

Frequently asked questions

How many skills should you list on a resume?
Eight to fifteen, grouped into two to four labeled clusters. Below eight looks thin for anyone past entry level; past fifteen the list reads as indiscriminate and the skills that matter drown. The count is per resume version: tailoring means rotating skills in and out per posting, not growing the list.
Should I put soft skills in the skills section?
No, with one exception. Listed soft skills ('communication', 'leadership') are unverifiable self-ratings that recruiters skip and filters ignore. Demonstrate them inside experience bullets at a specific scale instead. The exception is spoken languages with proficiency levels, which recruiters filter on like hard skills.
Do skills need to match the job description exactly?
For tools, credentials, and platforms, yes: matching is mostly literal, so write 'Salesforce' if the posting says Salesforce, and cover spelled-out plus abbreviated forms once each ('electronic health records (EHR)'). The resume keywords guide covers the matching mechanics in full.
Can I list a skill I haven't used in years?
If you could get current with normal ramp-up and would survive interview questions about it, yes; consider a 'familiar with' subgroup if your field distinguishes working depth from exposure. If the skill is obsolete in the market, cut it: dated software ages a resume faster than a dated graduation year.
Are skill bars ever okay on a resume?
No. Graphics don't parse, so the skill may be invisible to the database, and the rating is uncalibrated for humans. If a template you like uses them, choose a variant that renders skills as text; every template in our gallery does, because we verify extraction on real PDFs before shipping.

Build yours in minutes

Pass the bots

Every template is built single-flow and parse-tested. ATS View shows you exactly what an applicant tracking system extracts from your resume, before you send it.

AI that sounds like you

Our writing suggestions start from your real experience, not a phrase library. You keep your voice; the AI handles structure, verbs, and cut-the-fluff editing.

One document, every tool

Your resume powers everything: the ATS report, the job-match analysis, and a cover letter in the same design. Switch templates any time and your content reflows without retyping.

Create my resume, no sign-up needed

No sign-up required to start. Import your old resume or build from scratch, and see exactly what the bots read on your finished PDF.