Reviewed by a certified professional resume writer (CPRW) with US corporate recruiting and ATS screening experience
What to put in the skills section of resume files is not a random list of everything you have ever touched—it is a structured block of posting-aligned categories: technical tools, methods, domain terms, languages, and certifications, with soft skills limited to terms you can prove in experience bullets. The section needs a standard heading, plain formatting parsers can read, and placement on page one so Workday and Taleo index your keywords before a recruiter opens the file.
Job seekers often confuse which skills are good with what actually belongs inside the skills section. Those are different questions. A strong Python background matters, but whether Python sits in a labeled Technical Skills line, a combined comma list, or a sidebar text box determines whether an applicant tracking system extracts it at all. This article focuses on the container: which categories to include, how to group them, where to place the block on a US resume, what to leave out, and how major ATS platforms read the result. For which individual skills rank highest by role, see what are good skills to put on a resume —here we cover what goes inside the section and how to structure it.
Key Takeaways
- Group skills into five categories: tools, methods, domain, languages, certifications
- Use a standard Skills heading with plain comma or bullet lists—no rating graphics
- Place the section on page one; put it high when tools define the role
- Repeat top posting keywords in experience bullets, not only in the skills block
- Remove hobbies, generic traits, outdated tools, and unverifiable claims
What to put in the skills section: five categories employers expect
A resume skills section is a structured inventory, not a personality profile. US recruiters and ATS parsers look for searchable terms grouped in predictable categories. When you know what to put in the skills section of resume files, you stop treating it as a catch-all and start treating it as indexed metadata that mirrors job posting language.
Category 1 — Technical tools and platforms: Software, systems, and hardware you operate daily. Examples: Salesforce, SAP, Figma, Jira, AWS, Microsoft Excel, Epic, ServiceNow. These terms carry the highest keyword weight in most parsers. List the exact product names the posting uses.
Category 2 — Methods and frameworks: Repeatable processes and approaches tied to your role. Examples: Agile, Scrum, Six Sigma, financial modeling, A/B testing, UX research, GAAP reporting. Methods often appear in requirements without a brand name—include them when you have used them in paid work.
Category 3 — Domain and industry knowledge: Regulated or specialized vocabulary that signals you understand the field. Examples: HIPAA, SOX compliance, B2B SaaS sales cycles, supply chain planning, instructional design, clinical documentation. Domain terms filter candidates on regulated roles.
Category 4 — Languages: Human languages at professional or working proficiency when relevant to the role or market. Format as Spanish (professional working proficiency) or Mandarin (conversational). Do not list programming languages here—Python and SQL belong under technical tools.
Category 5 — Certifications and licenses: Abbreviations parsers can match—PMP, CPA, RN, CompTIA Security+, SHRM-CP. Full credential details with issuer and date belong in a separate Certifications section; repeat the acronym in Skills for keyword overlap.
Soft skills — limited add-on: Include one to three interpersonal terms only when the posting names them and your bullets prove them: stakeholder communication, executive presentation, cross-functional collaboration. Soft skills are not a sixth full category—they are supporting lines, not the bulk of the section.
O*NET OnLine publishes technology and skill inventories by occupation. Cross-check your category choices against O*NET OnLine occupation profiles to confirm which category each term belongs in for your target role.
Key Takeaway: fill the skills section with five structured categories—tools, methods, domain, languages, certifications—plus a small set of posting-named soft skills with proof in bullets.
How to structure the skills section by category
Structure matters as much as content. Applicant tracking systems map your Skills heading to a dedicated field; what sits under that heading must be scannable plain text. Three common layouts work for US resumes in 2026—choose based on role type and space.
Layout A — Labeled subgroups (best for technical and hybrid roles):
Skills
Technical: SQL, Python, Tableau, Power BI, Salesforce CRM, Microsoft Excel (pivot tables, VLOOKUP)
Methods: Agile, cohort analysis, A/B testing, financial forecasting
Domain: B2B SaaS metrics, churn analysis, subscription revenue modeling
Core competencies: Stakeholder reporting, cross-functional project leadership
Layout B — Single comma-separated block (best when space is tight):
Skills
Jira, Confluence, Agile, Scrum, MS Project, Smartsheet, risk registers, stakeholder reporting, budget tracking, PMP
Layout C — Bulleted subgroups (best for career changers showing range):
Skills
• Design: Figma, Adobe XD, wireframing, prototyping, usability testing
• Research: user interviews, heuristic evaluation, survey design
• Collaboration: Miro, stakeholder workshops, accessibility (WCAG 2.1)
| Category | What to include | What to exclude | Typical count |
|---|---|---|---|
| Technical tools | Named software, platforms, programming languages | Generic computer skills, Microsoft Office alone | 5–10 per tailored version |
| Methods | Frameworks and processes used in paid work | Buzzwords with no project evidence | 2–5 |
| Domain | Industry and compliance vocabulary | Broad industry names without specifics | 1–4 when role-specific |
| Languages | Human languages with proficiency level | Elementary or tourist-level claims | 0–2 |
| Certifications | Acronym for ATS keyword match | In-progress courses without completion date | 1–3 acronyms; details in Certifications |
| Soft skills | Posting-named traits with bullet proof | Team player, hard worker, fast learner | 0–3 max |
Keep each subgroup under fifteen terms. Longer lists dilute match scores and push critical keywords below the fold. For count guidance by role, read how many skills you should list on your resume .
Expert tip: lead every subgroup with the three terms the posting repeats most often—parsers and recruiters weight early items higher within each line.
Skills section formatting that Workday and Greenhouse parse
What to put in the skills section of resume files only works when parsers can extract it. Workday and Greenhouse—two of the most common US employer platforms—index skills as structured data separate from your experience narrative. Formatting errors cause entire categories to disappear from the recruiter view.
- Standard heading only: Skills, Technical Skills, or Core Competencies—never My Toolkit, Expertise Cloud, or Strengths Matrix
- Document body placement: main column, not sidebar, header, footer, or floating text box
- Plain lists: commas or simple bullets—no nested tables, icons, or skill clouds
- No proficiency graphics: rating bars, stars, and percentage rings fail in Workday and ADP Recruiting uploads
- Posting-exact spelling: Microsoft Power BI, not PowerBI; Jira, not project management software
- Single column inside the section: two-column skill matrices break in Taleo and iCIMS
The Bureau of Labor Statistics Occupational Outlook Handbook describes skills and training employers expect by occupation. Browse BLS Occupational Outlook Handbook entries for your target role to confirm standard vocabulary before you finalize category labels and tool names.
After you structure the section, upload a draft to HireFlow's free ATS resume checker and confirm skills extract into the correct field. The parsed preview often reveals terms hidden by layout choices your PDF looks fine displaying.
For platform-specific file rules beyond the skills block, follow Workday resume format guidance for 2026 even when you apply through Greenhouse or Lever.
Parser insight: a plain Skills heading in the document body with comma-separated categories outperforms every designed template that hides terms in graphics or side columns.
Where to place the skills section on your US resume
Placement is part of what to put in the skills section of resume strategy—not just what terms you list, but where the block sits relative to summary, experience, and education. Section order signals priority to recruiters skimming in seconds and affects how early parsers encounter your keywords on multi-page files.
Recommended placement by candidate type:
- Technical and career-change candidates: Contact → Summary → Skills → Experience → Education → Certifications. Tools define your fit—show them before work history.
- Mid-career professionals: Contact → Summary → Experience → Skills → Education. Track record leads; keep a compact skills block on page one.
- Recent graduates: Contact → Summary → Education → Skills → Projects → Experience. Coursework tools and project stacks belong in Skills after Education.
- Executive roles: Contact → Summary → Experience → Board and Leadership → Skills (short list) → Education. Six to ten terms max; depth lives in bullets.
Never bury posting-critical keywords on page two. If your experience section runs long, trim older roles or tighten bullets before you push Skills to a second page. Integrate top tools into your summary when space is tight: Operations analyst with five years in SQL, Tableau, and SAP reporting for manufacturing supply chains.
LinkedIn profiles use a separate Skills section with endorsement mechanics that do not transfer to PDF resumes. LinkedIn's skills section help documentation explains how endorsements work on the platform—your resume skills block follows different rules: no endorsements, no skill quizzes, plain text only.
For broader section-order decisions across the full document, review what to add to your resume in 2026 .
Quick note: put Skills high when tools define the role; keep every tailored keyword on page one even when experience leads the document.
What not to put in the skills section
Knowing what to put in the skills section of resume files requires an equally clear leave-out list. Cluttered sections signal template resumes, break parsers, and waste the eight-to-fifteen term budget that should mirror one posting.
- Proficiency rating bars and stars: parsers skip graphical indicators; recruiters distrust self-scored expertise
- Hobbies and personal interests: photography, travel, and cooking belong nowhere near Skills unless the role explicitly requires them
- Generic computer literacy: email, internet, Microsoft Word—assumed baseline in 2026 US hiring
- Outdated tools: software you have not used in five or more years unless the posting still requires it
- Unverifiable claims: expert-level tags on tools you are still learning—use a Training line with course name and date instead
- Duplicate certification paragraphs: full PMP credential text in Skills when Certifications already lists issuer and date—repeat the acronym only
- Soft-skill filler: team player, detail-oriented, passionate, go-getter—replace with evidence in experience bullets
- References and contact info: never inside the skills block
Skills listed only in the section without proof in experience rank lower in Lever and SuccessFactors semantic scoring. If you remove a term from the leave-out list and add it to Skills, repeat it in at least two bullets with action, scope, and outcome. For how parsers classify tools versus methods, see how ATS interprets skills vs tools vs technologies .
Pro move: audit your skills block against the posting and delete every term that does not appear in requirements—irrelevant keywords dilute match scores worse than a shorter list.
Before-and-after skills section rewrites
Structure fixes often produce larger ATS gains than adding new skills. Compare these common mistakes with targeted category and placement corrections:
Operations analyst — unstructured keyword dump
- Skills: Excel, teamwork, SAP, communication, passionate about data, SQL, hard worker, PowerPoint, problem solving, Tableau, detail-oriented, Python, leadership
- Skills — Technical: SQL, Python, Tableau, SAP, Microsoft Excel (pivot tables, VLOOKUP) — Methods: variance analysis, forecast modeling, KPI dashboard design — Core competencies: cross-functional stakeholder reporting (soft skills cut to one posting-named term; generic traits removed)
Registered nurse — certifications buried in a comma list
- Skills: patient care, BLS certified since 2019 American Heart Association, Epic, teamwork, IV therapy, ACLS, compassionate, care coordination, medication administration
- Skills — Clinical systems: Epic, Cerner — Clinical skills: IV therapy, patient assessment, care coordination, medication administration — Certifications: BLS, ACLS (full issuer details moved to Certifications section; acronyms kept for ATS match)
Software engineer — skills trapped in a sidebar column
- Two-column resume template places Python, React, AWS, and Docker in a right-sidebar Skills box. Workday upload extracts an empty skills field; recruiter view shows blank technical inventory.
- Single-column layout: Skills heading in document body after summary — Technical: Python, JavaScript, React, Node.js, AWS, Docker, Git, REST APIs — Methods: Agile, CI/CD, unit testing, code review. Sidebar removed entirely.
Marketing manager — rating graphics break iCIMS parsing
- Skills displayed as a table with five-star ratings for HubSpot, Google Analytics, SEO, and SEM. iCIMS parser drops the entire block.
- Plain Skills heading: SEO, SEM, Google Analytics 4, HubSpot, content strategy, email automation, Meta Business Suite, A/B testing — comma-separated, no graphics, page one placement after summary
Bottom line: category labels, document-body placement, and plain lists fix more screening failures than adding extra keywords to a broken layout.
How Taleo, iCIMS, and SuccessFactors read your skills block
Platform behavior varies, but the same structural rules protect your skills section across employers. Understanding how major ATS products index the block helps you decide what to put in the skills section of resume files before every upload.
- Workday: maps a standard Skills heading to a dedicated field; sidebar and two-column layouts often drop right-column content entirely
- Greenhouse: scores semantic overlap across skills and experience bullets; keywords without contextual proof in work history rank lower
- Taleo: strips table-based skill matrices aggressively—plain comma lists only
- iCIMS: indexes the first recognizable Skills heading; nested tables inside the section may parse as empty
- Lever: favors skills repeated in both the skills block and at least one dated experience entry
- SuccessFactors: weights early-page content higher on two-page files—keep Skills on page one
- ADP Recruiting: struggles with graphical proficiency indicators and non-standard section headings
A common failure mode: strong tools listed only in a designed template while experience bullets use vague language. Parsers extract keywords but score low on contextual match. The fix is structural repetition—name the tool in a labeled category and show how you used it with scope and outcome in a bullet.
Skills section build checklist
- Five categories identified: tools, methods, domain, languages, certifications
- Standard Skills heading in document body—not sidebar or text box
- Eight to fifteen posting-aligned terms per tailored application
- Hard tools listed first; soft skills limited to posting-named terms with proof
- Plain comma-separated or bulleted lists; no rating bars, stars, or charts
- Spelling matches job description exactly (Power BI, not PowerBI)
- Top posting keywords repeated in two or more experience bullets
- Outdated tools, hobbies, and generic traits removed
- Section placed on page one; high placement when tools define the role
- Parser test completed before portal submit
Parser insight: format once for extraction, tailor categories per posting, and prove every priority keyword in both Skills and experience bullets.
What to put in the skills section of resume files comes down to structure, not volume. Group tools, methods, domain terms, languages, and certification acronyms under a standard heading. Format as plain text lists parsers can read. Place the block on page one. Cut everything that does not mirror one posting or prove itself in experience bullets. Soft skills, hobbies, rating graphics, and sidebar layouts belong outside the section—or off the document entirely.
Build a master category inventory, tailor eight to fifteen terms per application, and verify extraction before every upload. Run your file through HireFlow's free ATS resume checker after you finalize the skills section—a missing or mangled skills field costs interviews even when your experience is a strong match. Structure the container correctly, fill it with posting language, and let parsers do the matching work for you.
Frequently asked questions
Put posting-aligned hard skills grouped by category: technical tools and platforms, methods and frameworks, domain knowledge, languages, and certifications. Add one to three soft skills only when the job description names them and you can prove them in experience bullets. Skip hobbies, personality traits, and outdated software.
Use a standard Skills heading with labeled subgroups—Technical Skills, Methods, Core Competencies—or a single comma-separated block when space is tight. List hard tools first, keep each line under fifteen terms, and match job posting spelling exactly. Never use tables, rating bars, or two-column layouts inside the section.
Technical and career-change candidates place skills after the summary on page one. Mid-career professionals often put a shorter skills block after experience. Recent graduates may list skills after education and projects. Keep every posting keyword on page one whenever possible.
List credentialed certifications in a dedicated Certifications section with issuer and date. You may repeat the certification acronym in the skills block for ATS keyword matching—PMP, CPA, AWS Solutions Architect—but the full credential belongs in Certifications, not buried in a comma list.
Yes, but limit soft skills to terms the posting explicitly requests and that you support with evidence in bullets. Stakeholder communication, cross-functional collaboration, and executive presentation work when named in the job description. Generic traits like team player or hard worker belong in experience bullets or nowhere.
Most tailored US resumes perform well with eight to fifteen skills per application. Deep technical stacks may reach twenty when every term is relevant. A master resume can hold more; each version should mirror one posting. Overloading forty generic terms dilutes match scores in Workday and SuccessFactors.
Do not include proficiency rating bars, skill-level graphics, hobbies, references to basic computer literacy, outdated tools from a decade ago, skills you cannot discuss in an interview, or duplicate content already covered in a Certifications section without adding searchable keywords.
Yes. Applicant tracking systems extract a dedicated Skills field separately from experience bullets. Workday, Greenhouse, and iCIMS score overlap across both areas. Skills named only in bullets without a structured section often rank lower than candidates who repeat top keywords in both places.
Done for you
Turn this advice into an interview-ready resume
Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.