12 min read

What Skills Can I Put on a Resume? Guide for 2026

HireFlow Editorial Team
August 4, 2026

What skills can I put on a resume? See skill categories by career stage, ATS placement tips, and examples that pass Workday and Greenhouse parsing in 2026.

Reviewed by a certified professional resume writer (CPRW) with US corporate recruiting and ATS screening experience

Job seeker organizing resume skill categories on a laptop with an ATS keyword match report

What skills can I put on a resume? List hard skills (tools, methods, certifications), soft skills you can prove in bullets (coaching, presenting, resolving conflicts), and role-specific technical skills pulled from the job description. In 2026, corporate applicant tracking systems on Workday, Greenhouse, and Taleo match posting language to your file text—so skill names must appear in plain text, not inside icons or sidebar graphics. Most US resumes need eight to fifteen honest, verifiable skills woven through a dedicated section, your summary, and achievement bullets.

Job seekers search what skills can I put on a resume when a blank skills box stares back from a template. The wrong move is copying a generic list from the internet. The right move is mapping what you actually do to what the employer actually filters on. This guide breaks skill types into a category table, shows what to emphasize at each career stage, explains where parsers expect skills on the page, and gives before and after rewrites you can adapt before you upload your next application.

Skill category Examples Best placement ATS note
Hard / technical Python, SQL, Salesforce, GA4, CNC machining Skills block + bullets Match posting spelling exactly
Software & platforms Excel, Workday HCM, Jira, HubSpot, SAP Skills block near top Plain text list, no rating bars
Methods & frameworks Agile, Lean Six Sigma, GAAP, SEO, A/B testing Bullets with outcomes Pair method with metric
Interpersonal (proved) Client negotiation, cross-functional leadership Experience bullets Avoid naked trait lists
Certifications & licenses PMP, CPA, RN, AWS Solutions Architect Skills or Certifications line Include acronym + full name once
Languages Spanish (professional), Mandarin (conversational) Skills or separate Languages line State level in words, not stars

Key Takeaways

  • Hard and technical skills should name real tools; soft skills need proof in bullets
  • Eight to fifteen targeted skills beat long generic lists for ATS keyword match
  • Place skills in plain text where Workday and Greenhouse parsers can read them
  • Mirror job description wording only when you can defend each skill in an interview
  • Run your file through HireFlow's checker at / before portal upload

Hard skills, soft skills, and technical skills: what counts

Hard skills are teachable capabilities tied to tasks: bookkeeping, welding, data modeling, copywriting, or HIPAA compliance. Technical skills are a subset—usually software, code, or equipment. Soft skills describe how you work with people: influencing stakeholders, mentoring juniors, or de-escalating customer complaints. All three belong on a resume when they are relevant to the role and backed by evidence.

Recruiters filtering in Greenhouse often search exact strings like Salesforce or patient triage. Hard and technical terms drive those filters. Soft skills rarely appear as search terms unless the posting says leadership or communication explicitly— then weave those words into bullets about presentations, training, or conflict resolution rather than an isolated trait row.

The Society for Human Resource Management notes that skills-based hiring continues to expand in US employers—meaning verified competencies matter more than pedigree alone. Your skills section is the fastest signal that you speak the employer's operational language. Read soft skills phrases recruiters trust before you default to teamwork and problem solving without context.

Transferable skills bridge industries: project coordination, budget tracking, vendor management, and quality auditing apply across sectors. Career changers should lead with transferable hard skills that overlap the new field, then support them with bullets from the prior industry showing scale and outcomes.

Pro Tip: if a skill appears in the job posting three times, it is probably a filter term—include it verbatim in your skills block or bullets when honest.

Skill categories table: what to list by job function

Use function-specific categories so recruiters instantly see fit. The table below shows starter sets; tailor every row to your target posting. Generic mega-lists from template sites hurt clarity and can trigger keyword-stuffing penalties on semantic matchers used alongside legacy ATS parsers.

Function Core hard skills Tools & platforms Methods / certifications
Software engineering API design, code review, CI/CD Python, AWS, Docker, PostgreSQL Agile, REST, OAuth
Marketing Campaign analytics, content strategy GA4, HubSpot, Meta Ads Manager SEO, A/B testing, brand compliance
Finance Financial modeling, variance analysis Excel, NetSuite, Power BI GAAP, SOX controls, CPA (if held)
Healthcare clinical Patient assessment, EMR documentation Epic, Cerner, Philips monitors BLS, ACLS, RN license
Operations / supply chain Inventory planning, vendor SLAs SAP MM, Oracle SCM, WMS Lean, ISO 9001, Six Sigma Green Belt
Customer support Ticket triage, knowledge base authoring Zendesk, Intercom, Salesforce Service CSAT improvement, SLA adherence

Cross-reference your list with what keywords ATS systems look for so you understand which terms are skills versus titles. Industry keyword lists—such as nursing or supply chain guides on HireFlow—give sector-specific nouns to verify against your draft.

Common Mistake: copying the entire table into your resume without deleting rows that do not apply—recruiters spot template padding instantly.

Skills by career stage: entry-level, mid-career, and executive

Career stage changes which skills lead and how many you need. Early-career resumes lean on education-adjacent proof: coursework tools, internship platforms, capstone methods, and part-time job software. List every honest tool from labs and campus jobs; omit high school babysitting unless it is your only customer service proof.

Entry-level (0–3 years)

Lead with technical and tool skills tied to the posting. Example block: Excel (pivot tables, VLOOKUP), SQL (SELECT joins), Google Analytics 4, Figma, public speaking from debate club. Pair each with one bullet—built weekly GA4 dashboards for student marketing club; tracked 12 vendor contracts in Excel.

Mid-career (4–12 years)

Balance depth and breadth. Show advanced tool use inside bullets—automated NetSuite reporting saved 6 hours weekly—and keep a tight skills row for scanner visibility. Certifications earned in the last five years belong here. Drop outdated tools you no longer touch unless the target role still uses them.

Executive and senior (12+ years)

Skills sections shrink. Emphasize strategic capabilities: M&A integration, global team leadership, P&L ownership, enterprise architecture governance. Tool lists move to bullets under recent roles. iCIMS and Workday still index keywords in summary lines—include board reporting and change management when the posting demands them.

High school student and first-job applicants should read first-job resume examples for age-appropriate skill framing that passes campus recruiter screens.

Quick Check: every skill on your list should appear in at least one bullet or project line—orphan skills raise interview risk.

Where to place skills for ATS parsers and recruiter scan order

Applicant tracking systems do not only read a labeled Skills heading—they index the full document. Still, placement affects both parse quality and human scan order. Recruiters opening a PDF in Greenhouse often read name and current title, skim the latest job bullets, then hunt for tool names before deciding whether to read the rest.

Recommended 2026 layout for most US one-page resumes: contact header, three-line summary with two posting keywords, skills block (two to three lines of comma-separated tools or categorized sublists), experience in reverse chronological order, education last. For technical roles, a project section can carry additional stack keywords when the experience section is short.

Workday frequently exposes a separate skills field after upload. Type the same honest skills there—spelling aligned with your file. Taleo variants sometimes drop sidebar content; never put your only copy of SQL or SAP in a left column text box. Our Workday resume format guide walks through upload tests on live portals.

Avoid skill rating graphics, donut charts, and progress bars—they look modern in Canva but break extraction on Lever and SuccessFactors tenants. Plain commas or bullet characters preserve text for matchers. If you use categories, label them in words: Technical Skills, Certifications, Languages—not colored badges.

Common Mistake: stuffing thirty skills in a sidebar while bullets mention none of them—semantic matchers weight frequency across the whole file.

How to pull skills from a job description without stuffing

Start by pasting the posting into a document and highlighting nouns that describe tools, methods, certifications, and domain knowledge. Ignore filler adjectives. Repeated terms signal priority. Our keyword identification workflow expands this into a repeatable 15-minute pass before each application.

Map each highlighted term to your background: yes with proof, partial with honest framing, or no—skip it. Partial matches might read Tableau (dashboards; advancing in SQL) rather than claiming expert status. Never list skills you cannot discuss for sixty seconds under recruiter questioning.

Spread matched skills across three zones: summary (top two priorities), skills block (eight to twelve terms), and bullets (each major requirement once). That distribution mirrors how keyword density guides recommend covering requirements without repeating the same line twelve times.

CareerOneStop, sponsored by the US Department of Labor, publishes occupation profiles listing common tools and skills by role—useful when a posting is vague. Cross-check their lists at CareerOneStop occupation profiles against your draft for missing industry-standard terms.

Pro Tip: upload a tailored draft to HireFlow's free ATS checker with the job description pasted—gaps show before you commit to a portal upload.

Before and after skill section rewrites for common roles

Weak skill sections use vague traits, outdated tools, or unparseable layouts. Strong sections name current platforms, pair methods with scope, and align with posting language. Adapt these patterns—not copy verbatim unless truthful.

Before (weak) After (ATS-safe)
Skills: Microsoft Office, communication, teamwork, fast learner, leadership. Skills: Excel (pivot tables, Power Query), Salesforce CRM, Slack, contract redlining in Word—supported in bullets with revenue and cycle-time metrics.
Two-column template with skill bars at 80% for Java and Python in a graphic sidebar. Single-column Skills line: Java, Python, Spring Boot, Kubernetes, AWS (EC2, S3), PostgreSQL—each referenced in project bullets with scale (requests/day).
Registered Nurse skills: caring, multitasking, EMR. Clinical skills: Epic inpatient documentation, medication administration, triage assessment, BLS/ACLS, patient education for CHF discharge—mirrors posting terms.
Marketing generalist: social media, creativity, SEO basics. Skills: GA4, HubSpot Marketing Hub, SEO (technical audits), Meta Ads Manager, A/B testing on landing pages—increased qualified leads 34% in bullet proof.

After rewriting, export PDF and DOCX if the employer allows both, then confirm skills text survived parsing. See PDF vs DOCX for ATS for format tradeoffs on Greenhouse uploads.

Key Takeaway: replace trait stacks with tool names the posting actually filters on—proof lives in the bullets beneath.

Career changers: transferable skills and honest gap framing

Career changers should not dump unrelated tool stacks from the old field. Instead, extract transferable hard skills: budget ownership, CRM administration, process documentation, SQL reporting, or client onboarding—then label them in context of the target role. A teacher moving to corporate training lists LMS administration, curriculum design, and stakeholder workshops, not only classroom management as a soft label.

Add a short Target Skills or Core Competencies block at the top listing new-field tools you are actively using in coursework, certifications, or volunteer projects. Honest partial skills beat silence: HubSpot (certified; 3 client campaigns) signals intent and baseline ability.

The Bureau of Labor Statistics Occupational Outlook Handbook lists typical skill requirements by occupation—useful when pivoting to compare your inventory against the destination role's baseline expectations.

If you completed a bootcamp or returnship, place capstone stack skills in a Projects section with dates so parsers associate tools with recent use. Pair with free ATS-friendly checks before mass applying through Workday tenants.

Volunteer and unpaid project skills count when they mirror paid work—format them in skills blocks and project sections with the same tool names: GitHub Actions, Figma prototypes, QuickBooks for nonprofit treasurers. ATS matchers do not distinguish paid from unpaid; recruiters do, so pair unpaid stack proof with a bullet showing deliverable scope and hours invested.

Seasonal workers and gig platform earners should list platform tools once in skills and show repeat seasons in experience—see gig economy resume wording for timeline compression that keeps Uber Eats or freelance marketplace skills visible without listing every single weekend shift across ten years.

Key Takeaway: skills prove capability; placement and spelling help parsers and recruiters find that proof in under ten seconds.

Skills list formats that survive ATS extraction

Format choice affects whether parsers read your skills as searchable tokens. The safest US corporate formats in 2026 are comma-separated inline lists, simple bullet lists with plain hyphens, and categorized subheadings with text-only rows—Technical Skills on one line, then tools separated by commas. Each format keeps characters selectable when a recruiter copies from PDF or when Workday extracts text from your upload.

Risky formats include skill matrices with shaded cells, icon grids where each skill sits inside a graphic circle, and multi-column tables that split Python on the left from SQL on the right. Taleo parsers sometimes read column order incorrectly, pairing the wrong tool with the wrong proficiency label. Lever preview panes may strip background colors entirely, leaving empty boxes where skills should appear.

If you need categories, use bold text labels—not boxes: Languages: Spanish (fluent), French (conversational). Certifications: PMP, AWS Solutions Architect Associate. Software: Salesforce, Tableau, Jira. That structure scans well for humans and survives most extraction engines because every token sits in continuous text flow.

Repeat high-priority posting skills once in the skills block and once in a recent bullet when natural—semantic matchers reward corroboration across sections without requiring identical duplication twelve times. After formatting, export and upload to HireFlow's ATS checker to confirm skill tokens appear in the extracted text panel, not only in the visual preview.

Pro Tip: run find-and-replace on curly quotes and special bullets before export—smart punctuation sometimes breaks token boundaries in older parsers.

Skills section checklist before you upload

  1. Highlight repeated tools and methods in the job posting.
  2. List eight to fifteen honest skills—not every synonym variant.
  3. Place skills in plain body text, not icons or rating bars.
  4. Match posting spelling for software names (HubSpot vs Hub Spot).
  5. Prove each major skill in at least one experience bullet.
  6. Put soft skills in bullets; avoid naked trait rows.
  7. Include certifications with acronym and full name once.
  8. Remove obsolete tools unless the posting still requires them.
  9. Duplicate key skills in Workday or Taleo form fields when prompted.
  10. Run HireFlow parse and keyword match at / on the exported file.

Quick Check: if your skills block exceeds six lines, cut lowest-priority terms until the section scans in under ten seconds.

Frequently asked questions

List skills you can prove from school, internships, volunteer work, or personal projects: Excel formulas, customer service from retail shifts, coding languages from class labs, bilingual ability, and tools like Google Analytics or Canva if you used them on real assignments. Group them under a Skills or Core Competencies heading and mirror language from the job posting. Entry-level applicants should prioritize hard skills and tool names over vague traits like hardworking.

Aim for eight to fifteen targeted skills for most US resumes, not a laundry list of forty buzzwords. Each skill should connect to a bullet in your experience section or to a requirement in the job description. Applicant tracking systems score overlap between posting text and resume text; density matters more than count. If a skill cannot be defended in an interview, remove it.

For ATS uploads, place a concise skills block after your summary or after your most recent job if you are mid-career. Recruiters scanning a PDF often look at the current role first, then skim a skills row for tool names. Avoid burying skills on page two. Workday and Greenhouse often map a dedicated skills field separately from body text—still include skills in the document body so keyword matchers see them.

Yes, but prove them in bullets rather than listing communication or teamwork alone. Soft skills work best when paired with context: presented quarterly updates to directors, mediated vendor disputes, or trained new hires. Our guide on soft skills phrases explains credible wording recruiters accept. Raw trait lists without evidence read as filler and rarely help ATS keyword scores.

Most corporate ATS parsers extract skills from anywhere in the document—dedicated sections, bullet text, and summary lines. Taleo and iCIMS may also offer a skills tag field on the application form. Duplicating honest skills in the file and in form fields is fine when wording matches. Graphic skill bars, icons, and multi-column skill tables often fail parsing—use plain text lists.

Include tools you use weekly: Microsoft Excel, Salesforce, Zendesk, SAP modules, Adobe InDesign, or SQL if you pull reports. Skip programming languages you touched once unless the role asks for them. Operations, marketing, and finance roles still need software names because recruiters filter on those terms. Match the posting's exact product names when you genuinely use them.

Highlight repeated nouns and tools in the posting—those are priority skills. Copy exact phrases only where truthful: if the ad says HubSpot CRM, write HubSpot CRM, not marketing software. Spread matched skills across your summary, skills list, and bullets rather than stuffing one block. HireFlow's checker at hireflow.net compares your file to a pasted job description for gap analysis.

Avoid star ratings, progress bars, and beginner-intermediate-expert scales on US resumes. Recruiters find them subjective, and ATS parsers often garble graphical elements. State proficiency in plain text only when it matters—bilingual fluent in Spanish, advanced Excel—or demonstrate level through bullets showing scope and outcomes.

Done for you

Turn this advice into an interview-ready resume

Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.

Job match tool·Free builder

Tags

what skills can i put on a resumeresume skills sectionskills to put on resume 2026ATS skills keywordshard skills resumesoft skills resumetechnical skills resumeresume skills by career stagewhere to put skills on resumeskills for ATSresume skill categoriesjob description skills match