Reviewed by a certified professional resume writer (CPRW) with US corporate recruiting and ATS screening experience
Good skills to put on a resume are posting-aligned hard skills—specific tools, platforms, methods, and domain terms—plus a small set of soft skills you can prove in experience bullets. The skills section should mirror job description language, use ATS-friendly plain formatting, and repeat top keywords with context in your work history so Workday and Greenhouse rank your file above generic lists.
Job seekers often ask what are good skills to put on a resume and receive vague advice: list everything you know, add soft skills like teamwork, or copy a template from the internet. Neither approach works in 2026 US hiring. Recruiters skim in seconds; applicant tracking systems score keyword overlap and parse quality before a human opens your application. A skills block stuffed with fifty unrelated terms performs worse than eight focused tools that match the posting. This guide explains which skills belong on your resume, how to separate hard skills from soft skills, how to format for ATS platforms, how to tailor per job, and which skills work by industry—with rewrites you can apply today.
Key Takeaways
- Lead with hard skills the posting names—tools, platforms, and domain terms
- Limit soft skills to terms you can prove with actions and outcomes in bullets
- Format skills as plain text lists; skip rating bars and graphics parsers cannot read
- Tailor eight to fifteen skills per application; repeat top keywords in experience
- Test extraction in Workday and Greenhouse before you submit through employer portals
Hard skills vs soft skills: what belongs on your resume
Understanding the difference between hard skills and soft skills is the foundation of a strong resume skills section. Hard skills are teachable, measurable abilities tied to tools, technologies, methods, or regulated knowledge. Soft skills describe how you work with people, priorities, and ambiguity—but they are harder to verify without context.
Hard skills recruiters and ATS platforms index first:
- Software and platforms: Salesforce, HubSpot, SAP, Figma, Jira, AWS, Microsoft Excel
- Programming and data: Python, SQL, R, Tableau, Power BI, Spark
- Methods and frameworks: Agile, Scrum, Six Sigma, GAAP, HIPAA compliance basics
- Domain expertise: SEO, B2B outbound, accounts payable, clinical documentation
- Languages: Professional working proficiency in Spanish, Mandarin, or ASL when relevant
- Certifications: PMP, CPA, CompTIA Security+, Google Analytics, SHRM-CP
Soft skills worth listing only when the posting names them and you have proof:
- Stakeholder communication and executive presentation
- Cross-functional collaboration and matrix leadership
- Conflict resolution, negotiation, and vendor management
- Mentoring, coaching, and change management
- Strategic prioritization under deadline pressure
Avoid filler soft skills with no evidence: team player, hard worker, fast learner, detail-oriented. Every recruiter has seen them thousands of times. They add little to ATS scores and nothing to a seven-second skim. Instead, demonstrate collaboration in a bullet—Coordinated launch across engineering, legal, and sales for 12-market rollout— and reserve the skills section for searchable terms parsers can match.
| Skill type | Good examples | Resume placement | ATS note |
|---|---|---|---|
| Hard — tools | Excel, Salesforce, Python, Adobe Creative Suite | Skills section; repeat in experience bullets | Highest keyword match weight in most parsers |
| Hard — methods | Agile, financial modeling, A/B testing, UX research | Skills or Certifications when credentialed | Match posting spelling exactly (Scrum vs scrum) |
| Hard — domain | HIPAA, SOX, SEO, supply chain planning | Skills and summary when role-specific | Filters on regulated roles often require these terms |
| Soft — provable | Executive communication, mentoring, negotiation | One to three terms max; prove in bullets | Lower match weight unless posting emphasizes them |
| Soft — generic | Teamwork, work ethic, passionate | Omit or replace with evidence in experience | Contributes little; can signal template resume |
| Certifications | PMP, CPA, AWS Solutions Architect | Certifications section or inline with skills | Some ATS forms have dedicated certification fields |
CareerOneStop, sponsored by the U.S. Department of Labor, recommends identifying skills employers need and describing them clearly on every application. Review CareerOneStop skills identification guidance alongside your posting audit to build a list grounded in labor-market language, not guesswork.
Key Takeaway: hard skills drive ATS matches; soft skills belong only when named in the posting and backed by measurable proof in your experience section.
How to format your skills section for ATS platforms
Good skills to put on a resume mean nothing if parsers cannot read them. Applicant tracking systems extract your skills block into a searchable field separate from experience bullets. Formatting mistakes—columns, icons, tables inside the section, or proficiency graphics—cause keywords to drop entirely.
- Use a standard heading: Skills, Technical Skills, or Core Competencies—never My Toolkit or Expertise Cloud
- Plain text lists: comma-separated lines or simple bullets without nested tables
- No rating bars or stars: Workday and iCIMS often skip graphical proficiency indicators
- Match posting spelling: if the job says Microsoft Power BI, do not write PowerBI or MS BI
- Group logically: Technical Skills, Methods, Languages—or one combined block when space is tight
- Keep skills on page one: parsers weight early content higher on long files
A parse-safe skills section looks like this in the document body:
Skills
Technical: SQL, Python, Tableau, Excel (pivot tables, VLOOKUP), Salesforce CRM
Methods: Agile, A/B testing, cohort analysis, financial forecasting
Core competencies: Stakeholder reporting, cross-functional project leadership
Do not hide skills in a sidebar, footer, or text box. Greenhouse and Taleo read the main document flow; content in floating elements may not index. For deeper formatting rules that protect your entire file, follow Workday resume format guidance for 2026 even when you apply through other portals.
The Bureau of Labor Statistics Occupational Outlook Handbook lists skills and training for hundreds of occupations. Browse BLS Occupational Outlook Handbook entries for your target role to confirm which hard skills employers in your field expect—and use that vocabulary in your skills block.
Key Takeaway: standard headings, plain lists, and posting-exact spelling keep skills visible to parsers—graphics and creative layouts hide them.
Tailoring skills to each job posting
The single highest-impact step when deciding what are good skills to put on a resume is tailoring. A master resume can hold thirty or forty skills you have used across your career; each application should surface the eight to fifteen terms that mirror one posting.
Step-by-step tailoring workflow:
- Paste the job description into a document and highlight every tool, platform, method, certification, and domain term in requirements and responsibilities
- Rank terms by frequency and placement—skills in the first paragraph of requirements usually carry more weight
- Select skills you genuinely hold; never invent tools you cannot discuss in an interview
- Reorder your skills section so top posting keywords appear first
- Edit two to three experience bullets to repeat those keywords with actions and outcomes
- Adjust your summary headline to name the top two or three hard skills
- Save as a role-specific file before uploading—Marketing Coordinator v3 is easier to track than Resume Final FINAL
Synonyms matter. If the posting says customer relationship management and you only list CRM, some parsers still match—but exact terms rank higher in Greenhouse semantic scoring. When the employer writes Jira, do not substitute project management software. When they write stakeholder management, use that phrase instead of people skills.
For guidance on how many terms to include without overload, read how many skills you should list on your resume . For how parsers distinguish tools from methods, see how ATS interprets skills vs tools vs technologies .
Key Takeaway: one tailored skills list per posting beats a static master file—mirror language, reorder priorities, and prove skills in bullets.
Good resume skills by industry and role level
Good skills to put on a resume vary by field. The lists below are starting points—always replace generic examples with posting-specific terms before you apply. Entry-level candidates should emphasize tools learned in coursework, internships, and projects; mid-career professionals should weight recent, role-relevant platforms over outdated software.
Technology and data
- Software engineering: Python, Java, JavaScript, React, Node.js, Git, REST APIs, AWS, Docker, CI/CD, unit testing
- Data analyst: SQL, Python, R, Tableau, Power BI, Excel, statistical modeling, ETL, data visualization
- Product management: roadmapping, user research, Jira, A/B testing, SQL basics, Figma, stakeholder prioritization
- IT support: Active Directory, ticketing systems (ServiceNow), troubleshooting, network fundamentals, CompTIA A+
Business, finance, and operations
- Financial analyst: Excel financial modeling, SQL, Bloomberg, variance analysis, forecasting, GAAP
- Operations manager: Lean, Six Sigma, supply chain planning, ERP (SAP, Oracle), KPI dashboards, vendor negotiation
- Human resources: Workday HCM, applicant tracking systems, employee relations, compensation analysis, SHRM-CP, HRIS
- Project management: PMP, Agile, Scrum, Smartsheet, MS Project, risk management, budget tracking
Marketing, sales, and customer-facing roles
- Digital marketing: SEO, SEM, Google Analytics, HubSpot, content strategy, email automation, Meta Ads
- Account executive: Salesforce, pipeline management, B2B outreach, contract negotiation, CRM hygiene, quota attainment
- Customer success: Gainsight, Zendesk, churn analysis, onboarding, renewal forecasting, QBR presentation
Healthcare, education, and regulated fields
- Registered nurse: Epic, patient assessment, IV therapy, care coordination, BLS, ACLS
- Clinical research: GCP, IRB protocols, EDC systems, adverse event reporting, HIPAA
- Teacher / instructional: curriculum design, LMS (Canvas, Blackboard), differentiated instruction, IEP compliance, classroom management
O*NET OnLine, sponsored by the U.S. Department of Labor, publishes skills and technology lists for occupations nationwide. Cross-check your industry picks against O*NET OnLine occupation profiles to align vocabulary with how employers describe the role in your market.
Key Takeaway: industry examples are templates—swap in posting keywords and drop outdated tools that no longer appear in target job descriptions.
Skills placement and section order on US resumes
Where you place skills affects both recruiter skims and parser weighting. US resume conventions in 2026 favor clarity over creativity.
Recommended section order by candidate type:
- Technical and career-change candidates: Contact → Summary → Skills → Experience → Education → Certifications
- Mid-career professionals: Contact → Summary → Experience → Skills → Education → Certifications
- Recent graduates: Contact → Summary → Education → Skills → Projects → Experience
- Executive roles: Contact → Summary → Experience → Board and Leadership → Skills (short list) → Education
When skills are central to the role—software engineer, data analyst, designer—place them on page one above the fold. When your track record speaks louder—tenured sales director, operations VP—a compact skills block below experience is fine. Never bury critical posting keywords on page two.
Integrate skills into your summary when space is tight: Data analyst with five years in SQL, Tableau, and Python forecasting models targeting healthcare analytics roles. That line gives parsers and recruiters context before they reach the dedicated skills block. For broader section guidance, review what to add to your resume in 2026 .
Key Takeaway: put skills high when tools define the role; keep them on page one always; integrate top keywords into your summary for extra context.
Before-and-after skills section rewrites
Small edits to your skills block often produce the largest ATS gains. Compare these common mistakes with targeted fixes:
Marketing coordinator — generic soft-skill overload
- Skills: Communication, teamwork, creativity, Microsoft Office, social media, hard-working, detail-oriented, passionate about marketing
- Skills: SEO, Google Analytics 4, HubSpot, content calendar management, email automation, Canva, A/B testing, Meta Business Suite — posting-aligned hard skills first; creativity removed in favor of proof in campaign bullets
Data analyst — skills disconnected from experience
- Skills section lists Python, SQL, Tableau on page two. Experience bullets describe reporting and dashboards without naming any tool. Workday extracts skills but finds zero keyword context in experience.
- Skills moved to page one after summary. Top bullets rewritten: Built Tableau dashboards tracking 14 KPIs for retail ops; automated weekly ETL in Python and SQL reducing manual prep 6 hours/week
Project manager — rating bars break parsing
- Skills displayed as a two-column table with five-star ratings for Jira, Agile, and MS Project. Greenhouse parser drops the entire block; recruiter sees blank skills field.
- Plain Skills heading with comma-separated list: Jira, Confluence, Agile, Scrum, MS Project, Smartsheet, risk registers, stakeholder reporting, PMP — single column, no graphics
Career changer — untailored master list
- Same 35-skill cloud submitted to UX researcher and product manager roles. List includes unrelated tools from prior hospitality job. Match score diluted for both targets.
- UX version: Figma, user interviews, usability testing, wireframing, Miro, heuristic evaluation, accessibility (WCAG). PM version: roadmapping, Jira, SQL, A/B testing, PRD writing, stakeholder prioritization — twelve skills each, posting-specific
Key Takeaway: replace generic traits with posting tools, move skills to page one, kill rating graphics, and prove every top keyword in experience bullets.
How Workday and Greenhouse index resume skills
Applicant tracking systems do not treat your skills section as decoration. They extract it, compare it to the job description, and score overlap alongside education, experience, and parse quality. Platform behavior differs—formatting for one portal usually helps across others.
- Workday: indexes a dedicated Skills field when the heading is standard; sidebar and two-column layouts often drop right-column skill lists entirely
- Greenhouse: uses semantic matching across skills and bullets; keyword repetition without context can trigger quality flags—balance density with natural phrasing
- iCIMS: maps the first recognizable Skills heading; nested tables inside the section may parse as empty
- Taleo: strips table-based skill matrices aggressively—use plain lists only
- Lever: favors skills repeated in both the skills block and at least one dated experience entry
A common failure mode is listing skills only in a graphical template while experience bullets use vague language. Parsers see the keywords but score low on contextual match. The fix is repetition with proof: name the tool in the skills section and show how you used it with scope and outcome in a bullet.
After you build or revise your skills block, upload to HireFlow's free ATS resume checker and confirm skills extract into the correct field before you commit to an employer portal. The parsed preview often reveals missing terms the PDF hides.
Resume skills section checklist
- Eight to fifteen posting-aligned skills per tailored application
- Hard skills listed first; soft skills limited to posting-named terms with proof
- Standard Skills heading in document body—not sidebar or text box
- 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 removed; current platforms from the last three to five years prioritized
- Skills block on page one for technical and career-change candidates
- Separate tailored versions saved per target role—not one generic cloud
- Parser test completed; skills field populates in preview before portal submit
Key Takeaway: ATS platforms score skills as structured data—format for extraction, tailor per posting, and prove keywords in experience bullets.
Knowing what are good skills to put on a resume comes down to three rules: list hard skills the posting names, prove them in experience bullets, and format for parsers—not designers. Soft skills matter only when they are specific, requested, and backed by outcomes. Generic trait lists and graphical skill charts hurt more than they help in Workday, Greenhouse, and the dozens of platforms US employers use in 2026.
Build a master skills 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.
Frequently asked questions
The best skills are posting-aligned hard skills—tools, platforms, methods, and domain terms the employer repeats in the job description—plus two or three soft skills you can prove in experience bullets. Good skills to put on a resume are specific (SQL, not computer skills), current, and backed by context in your work history, not isolated in a keyword block.
Most US resumes perform well with eight to fifteen targeted skills per application. Technical roles with deep stacks may reach twenty when every term is relevant. A master resume can hold more; each tailored version should mirror one posting. Overloading forty generic terms dilutes match scores in Workday and Greenhouse.
Yes when space allows. Use labeled subgroups—Technical Skills and Core Competencies—or a single Skills section with hard tools first and soft skills limited to terms the posting names. Never use rating bars or proficiency sliders; parsers cannot read them reliably.
Many platforms index a dedicated Skills section as a separate field. Workday and Greenhouse often score keyword overlap across both the skills block and experience bullets. Skills listed only in the section without proof in bullets rank lower than skills repeated with context.
List skills you can discuss confidently in an interview. Foundational or in-progress tools belong in a Certifications or Training line with course names and dates—not as expert-level claims in the main skills list. Honesty matters when employers verify proficiency during screens.
Include soft skills only when the posting names them and you have evidence: stakeholder communication, cross-functional collaboration, conflict resolution, mentoring, or executive presentation. Generic traits like hard worker or team player without proof add little value for ATS or recruiters.
Yes. Reorder and swap skills to match each posting's language. A project manager version might lead with Jira, Smartsheet, and Agile; the same candidate applying to a product role might foreground roadmapping, user research, and A/B testing. One static skills list underperforms tailored versions.
Place skills after your summary and before or after experience depending on role. Technical and career-change candidates often put skills high on page one. Senior professionals with long track records may tuck a shorter skills block below experience. Keep the section on page one whenever possible.
Done for you
Turn this advice into an interview-ready resume
Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.