Reviewed by a certified professional resume writer (CPRW) with US corporate recruiting and ATS screening experience
What to write under skills on resume files is a set of posting-aligned keyword phrases—not full sentences—grouped under a standard Skills heading: named tools and platforms, methods, domain terms, languages with proficiency, and certification acronyms, with soft skills limited to one to three terms the job description names. Write comma-separated lists or labeled subgroups in plain text so Workday and Taleo index every term before a recruiter opens the file.
Job seekers often know which skills they have but freeze at the blank line under Skills. Should you write SQL or Structured Query Language? Team player or stakeholder communication? A single comma list or labeled subgroups? The wording you choose determines whether applicant tracking systems extract your terms into a dedicated skills field or drop them entirely. This article covers exact phrasing, category labels, what to write for hard versus soft skills, formatting parsers read, and before-and-after examples. For which categories belong in the section, see what to put in the skills section of a resume —here we focus on the text you type under that heading.
Key Takeaways
- Write keyword phrases and comma-separated terms—not full sentences—under Skills
- Use labeled subgroups (Technical:, Methods:) or one compact comma block
- Match job posting spelling exactly: Microsoft Power BI, not PowerBI
- Limit soft skills to one to three posting-named terms with bullet proof
- Repeat top keywords in experience bullets, not only under the Skills heading
What to write under Skills: hard skills employers scan first
What to write under skills on resume files starts with hard skills—searchable terms parsers weight highest. US recruiters and ATS products look for named software, platforms, programming languages, methods, and domain vocabulary written as plain text directly under a standard Skills heading.
Technical tools and platforms: Write the exact product names the posting uses. Examples: Salesforce CRM, SAP S/4HANA, Figma, Jira, AWS, Microsoft Excel (pivot tables, VLOOKUP), Epic, ServiceNow. Lead each subgroup with the three terms the job description repeats most often.
Methods and frameworks: Write repeatable processes tied to paid work: 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 on the job.
Domain and industry terms: Write regulated or specialized vocabulary: HIPAA, SOX compliance, B2B SaaS sales cycles, supply chain planning, instructional design, clinical documentation. Domain terms filter candidates on regulated roles.
Languages: Write human languages with proficiency when relevant: Spanish (professional working proficiency) or Mandarin (conversational). Write programming languages under Technical—not here.
Certifications: Write acronyms parsers match—PMP, CPA, RN, CompTIA Security+, SHRM-CP. Full credential details with issuer and date belong in a separate Certifications section; repeat the acronym under Skills for keyword overlap.
O*NET OnLine publishes technology and skill inventories by occupation. Cross-check what you write against O*NET OnLine occupation profiles to confirm standard vocabulary for your target role before you finalize wording.
Key Takeaway: write hard skills as named, posting-aligned keyword phrases—tools first, then methods, domain terms, languages, and certification acronyms.
How to phrase what you write under the Skills heading
Phrasing matters as much as selection. Applicant tracking systems map your Skills heading to a dedicated field; the text underneath must be scannable plain keywords. Three phrasing patterns work for US resumes in 2026.
Pattern 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
Pattern 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
Pattern 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)
| What to write | Strong phrasing | Weak phrasing | Why it matters |
|---|---|---|---|
| Software tools | Microsoft Power BI, Salesforce CRM | BI tools, CRM experience | Named products match ATS keyword fields |
| Methods | Agile, Scrum, Six Sigma | Project management methodologies | Specific terms score higher than vague labels |
| Soft skills | Stakeholder communication | Great communicator, team player | Posting-named terms with bullet proof only |
| Languages | Spanish (professional working proficiency) | Fluent in Spanish | Proficiency level sets recruiter expectations |
| Certifications | PMP, AWS Solutions Architect | Project Management Professional since 2022 | Acronyms for ATS; full text in Certifications |
| Excel depth | Microsoft Excel (pivot tables, VLOOKUP) | Advanced Excel | Named functions match posting language |
Never write full sentences under Skills. I am proficient in Python and SQL fails parsers optimized for keyword extraction. Write Python, SQL, Tableau instead. For count guidance, read how many skills you should list on your resume .
Expert tip: copy exact tool names from the job posting—including capitalization and spacing—before you write anything under the Skills heading.
Skills section formatting that Workday and Greenhouse parse
What you write under skills on 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 lines 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 employers expect by occupation. Browse BLS Occupational Outlook Handbook entries for your target role to confirm standard vocabulary before you finalize what you write under Skills.
After you write the section, upload a draft to HireFlow's free ATS resume checker and confirm your text extracts 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: plain keyword phrases under a standard Skills heading outperform every designed template that hides terms in graphics or side columns.
Where to place what you write under Skills on your US resume
Placement affects what recruiters see first and how early parsers encounter your keywords. What you write under skills on resume strategy includes where the block sits relative to summary, experience, and education—not just the terms themselves.
Recommended placement by candidate type:
- Technical and career-change candidates: Contact → Summary → Skills → Experience → Education → Certifications. Write tools before work history when they define your fit.
- 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. Write coursework tools and project stacks under Skills after Education.
- Executive roles: Contact → Summary → Experience → Board and Leadership → Skills (short list) → Education. Write 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 what you wrote under 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.
For broader section-order decisions across the full document, review what to add to your resume in 2026 .
Quick note: write Skills high when tools define the role; keep every tailored keyword on page one even when experience leads the document.
What not to write under the skills section
Knowing what to write under skills on resume files requires an equally clear do-not-write list. Cluttered text signals template resumes, breaks parsers, and wastes the eight-to-fifteen term budget that should mirror one posting.
- Full sentences: I have five years of experience with Salesforce—write Salesforce CRM instead
- Proficiency rating bars and stars: parsers skip graphical indicators; recruiters distrust self-scored expertise
- Hobbies and personal interests: photography, travel, cooking—write these nowhere near Skills unless the role 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
- Soft-skill filler: team player, detail-oriented, passionate, go-getter—replace with evidence in experience bullets
- Duplicate certification paragraphs: full PMP credential text when Certifications already lists issuer and date—write the acronym only
Skills written only under the heading without proof in experience rank lower in Lever and SuccessFactors semantic scoring. If you add a term under 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 what you wrote under Skills 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: what to write under Skills
Wording fixes often produce larger ATS gains than adding new skills. Compare these common mistakes with targeted phrasing corrections:
Data analyst — vague labels instead of named tools
- Skills: data analysis, BI tools, spreadsheets, programming, visualization, teamwork, problem solving, SQL experience
- Skills — Technical: SQL, Python, Tableau, Microsoft Power BI, Microsoft Excel (pivot tables, VLOOKUP) — Methods: cohort analysis, A/B testing, financial forecasting — Core competencies: cross-functional stakeholder reporting
Project manager — full sentences under Skills
- Skills: I am certified in PMP and have extensive experience managing Agile projects using Jira and Confluence. Strong communicator with leadership skills.
- Skills — Technical: Jira, Confluence, MS Project, Smartsheet — Methods: Agile, Scrum, risk registers, budget tracking — Certifications: PMP — Core competencies: stakeholder reporting
Software engineer — skills written in a sidebar column
- Two-column template writes 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 under 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 replace plain text
- 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: named keyword phrases, document-body placement, and plain lists fix more screening failures than adding extra terms to poorly phrased text.
How Taleo, iCIMS, and SuccessFactors read what you write under Skills
Platform behavior varies, but the same phrasing rules protect what you write under Skills across employers. Understanding how major ATS products index the block helps you choose wording 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—write plain comma lists only
- iCIMS: indexes the first recognizable Skills heading; nested tables inside the section may parse as empty
- Lever: favors skills written under Skills and repeated in at least one dated experience entry
- SuccessFactors: weights early-page content higher on two-page files—write Skills on page one
- ADP Recruiting: struggles with graphical proficiency indicators and non-standard section headings
A common failure mode: strong tools written 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—write the tool in a labeled category and show how you used it with scope and outcome in a bullet.
Skills wording checklist
- Standard Skills heading in document body—not sidebar or text box
- Keyword phrases and comma lists—no full sentences under Skills
- Eight to fifteen posting-aligned terms per tailored application
- Hard tools written first; soft skills limited to posting-named terms with proof
- Spelling matches job description exactly (Power BI, not PowerBI)
- Labeled subgroups or one compact comma block—no rating bars or charts
- Top posting keywords repeated in two or more experience bullets
- Hobbies, generic traits, and outdated tools removed from what you write
- Section placed on page one; high placement when tools define the role
- Parser test completed before portal submit
Parser insight: write once for extraction, tailor phrasing per posting, and prove every priority keyword in both Skills and experience bullets.
What to write under skills on resume files comes down to phrasing, not volume. Write named tools, methods, domain terms, languages, and certification acronyms as keyword phrases 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. Full sentences, hobbies, rating graphics, and sidebar layouts do not belong under Skills.
Build a master wording 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 what you wrote under Skills—a missing or mangled skills field costs interviews even when your experience is a strong match. Write posting language, prove it in bullets, and let parsers do the matching work for you.
Frequently asked questions
Write posting-aligned hard skills as plain text under a standard Skills heading: named software and platforms, methods and frameworks, domain terms, languages with proficiency, and certification acronyms. Use comma-separated lists or labeled subgroups. Match job description spelling exactly and limit soft skills to one to three posting-named terms you can prove in experience bullets.
Use a standard Skills heading with labeled lines such as Technical:, Methods:, or Core competencies:, or a single comma-separated block when space is tight. Keep each line under fifteen terms, use posting-exact spelling, and avoid rating bars, nested tables, sidebars, and graphics parsers cannot read.
No. US resume skills sections use keyword phrases and comma-separated terms, not full sentences. Write SQL, Python, Tableau—not I have experience using SQL and Python for data analysis. Save narrative proof for experience bullets.
Write one to three soft skills only when the job description names them and your bullets prove them: stakeholder communication, cross-functional collaboration, executive presentation. Do not write team player, hard worker, detail-oriented, or passionate—these belong in experience bullets or nowhere.
Most tailored US resumes perform well with eight to fifteen terms per application. Deep technical stacks may reach twenty when every term is relevant. Overloading forty generic terms dilutes match scores in Workday and SuccessFactors.
Write proficiency only for human languages: Spanish (professional working proficiency). Do not use rating bars, stars, or beginner/intermediate/expert tags for software—recruiters distrust self-scored expertise and parsers skip graphical indicators.
Do not write hobbies, generic computer literacy, outdated tools, unverifiable claims, full certification paragraphs, references, contact information, or personality traits. Do not bury skills in sidebars, headers, or designed graphics.
No. Keep a master inventory, then tailor eight to fifteen posting-aligned terms per application. Swap tool names, methods, and domain vocabulary to mirror each job description while keeping your core stack consistent across versions.
Done for you
Turn this advice into an interview-ready resume
Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.