How to List Skills on a Resume | HireFlow

10 min read

Your resume skills section looks like a tag cloud from 2014. Python, leadership, Excel, teamwork, SQL, communication, Agile, problem-solving. You've got forty items and you're still not getting callbacks. You're not unqualified. You're just making parsers and recruiters work too hard to see what you actually use on the job.

I've screened stacks of these in Workday and Greenhouse. The files that pass aren't the longest skill lists. They're the ones where every keyword in Skills shows up again in a dated bullet with an outcome. Before you upload tonight, check your resume for free against the posting and see which required skills are missing from both sections.

This guide covers how to list skills on a resume in a format ATS reads: where the section goes, how many items to include, grouping rules, and copy-paste layouts you can paste into a plain Word or Google Doc file. You don't need fancy graphics. You need posting keywords tied to proof.

What is the resume skills section for?

The skills section is a scannable list of tools, methods, languages, and certifications that parsers and recruiters use to confirm you match the posting. It is not a personality test and not a place to dump every technology you touched once in a tutorial.

Workday, Greenhouse, Lever, and iCIMS usually map a block labeled Skills into its own field. If you hide skills in a two-column Canva layout or a footer icon row, the parser may never see them even when a human could.

Skills support your experience section; they do not replace it. Recruiters trust dated bullets with metrics more than a comma list. The list helps keyword match. The bullets prove you can do the work.

Recruiter filter: If your Skills block lists Tableau but no bullet mentions dashboards, I assume keyword stuffing until you prove otherwise on a call.

Read what are good skills to put on a resume when you are choosing which items belong on the page at all.

How to list skills on a resume step by step

Step 1: Pull keywords from the posting first

Open the job description and highlight required and preferred skills separately. Required items must appear in Skills or in Experience, ideally both. Preferred items go in when you truly have them.

Mirror exact spelling: if they write "Microsoft Excel," don't write "MS Office suite" alone. If they write "Looker," don't write "BI tools" without naming Looker somewhere on the page.

Step 2: Keep only skills you can prove

Walk your experience section line by line. Every skill in the list should connect to a bullet, project, or certification within the last five to seven years unless the posting asks for deep legacy experience.

Before: "Python, R, SQL, Java, C++, machine learning, deep learning, NLP, Excel, Tableau, Power BI, leadership, communication, Agile, Scrum, Jira, Salesforce, HubSpot, SEO, SEM, copywriting, public speaking."
After: "Python, SQL, Looker, Excel, A/B testing, lifecycle email, Salesforce, Google Analytics"

Step 3: Choose placement and header label

Default order for most candidates: Contact, Summary, Experience, Skills, Education, Certifications. Entry-level candidates with thin experience can put Skills above Experience when projects and coursework carry the proof.

Use Skills or Technical Skills as the header. Avoid Core Competencies, Toolbox, or What I Bring. Parsers and recruiters both recognize the standard label.

Read should you put skills above experience if you are debating order for a career change or student resume.

Step 4: Format for ATS in plain text

Single column. No tables for the skills block. No icons, bars, or star ratings. Separate items with commas or a pipe character on one or two lines, or use short subgroups with bold labels.

Copy-paste layout (single group):
Skills: Python, SQL, Looker, Excel, stakeholder reporting, financial modeling, Workday reporting

Copy-paste layout (grouped):
Tools: Python, SQL, Looker, Excel
Methods: A/B testing, cohort analysis, executive dashboards
Certifications: AWS Cloud Practitioner (2025)

Step 5: Tie each must-have skill to a bullet

After you build the list, open Experience and add or rewrite one bullet per top posting skill so the keyword appears in context with a date and metric.

Data analyst example:
Before: "Used SQL and Python for various analyses."
After: "Built weekly churn dashboards in Looker with SQL models that flagged at-risk SMB accounts, cutting reactive support tickets 11% in Q3."

Registered nurse example:
Before: "Skilled in Epic and patient care."
After: "Documented care plans in Epic for a 32-bed med-surg unit while precepting four orientees through fall-prevention workflows during a staffing surge."

Step 6: Handle soft skills without fluff

List soft skills only when the posting names them and you can prove them in bullets. Stakeholder management, cross-functional launches, and executive communication belong when your bullets show meetings, approvals, or outcomes tied to people work.

Cut standalone lines like "team player" and "fast learner." They add length without parser value and signal template thinking to human reviewers.

Step 7: Tailor skills per application without rewriting the whole resume

You do not need a brand-new file for every posting. Keep a master resume with every defensible skill, then save a tailored copy where you reorder Skills, adjust the summary, and rewrite two to three bullets to mirror the top req.

Move the three must-have tools from the posting to the front of the Skills line. Demote rare tools that are not mentioned in the job description to the bottom or drop them for that version. Filename tip: LastName_Analyst_Northwind.pdf so you do not upload the wrong tailored copy to the wrong portal.

After each tailor pass, run the checker again. Small keyword moves in Skills without matching bullet updates create mismatches recruiters notice fast.

Step 8: Preview what parsers actually extract

Upload your PDF to the employer portal if they offer a preview, or copy all text from the PDF into a plain Notepad file. If Skills arrives as one garbled line or disappears entirely, your layout is breaking parsing.

Fix by removing columns, tables, and text boxes. Re-export from Word or Google Docs using a single-column template at 11 or 12 point Calibri or Arial. That boring file usually survives Workday better than the designed version you liked on screen. Save the plain export before you upload.

Edge case: career change with new tools

Pivot candidates should lead Skills with target-role tools from bootcamp, certification, or freelance work. Keep prior-field tools only when they transfer to the new posting.

Example: moving from teaching to instructional design. List Articulate 360, LMS administration, and curriculum mapping up top. Move classroom management lower unless the posting asks for facilitation in live sessions.

Edge case: very long tool list in tech roles

Senior engineers sometimes need fifteen to twenty tools. Group by category and drop anything not used in the last three years unless the posting is legacy-heavy. Put the rarest must-have from the posting in line one of Skills and in your summary if you use one.

Do not create a second page just for skills. Trim first. Recruiters read depth in Experience, not encyclopedias in Skills.

Edge case: federal or clearance resumes

Name clearance level and program domains in Skills or Certifications when the posting requires it. Avoid classified program titles. Use environment types and outcome bands instead.

Example: "Active Secret clearance; IL5 environments; ServiceNow; Splunk; STIG remediation"

Edge case: creative roles with portfolio links

Designers and writers still use plain text skills for ATS. List Figma, Adobe Creative Cloud, and HTML/CSS in Skills. Put portfolio URL in contact lines, not inside the skills comma string.

One line under Skills works: "Portfolio: janedoe.design" as plain text, not a button graphic parsers cannot read.

Second composite: customer support specialist

Before: "Customer service, phones, email, chat, CRM, problem solving, multitasking, friendly attitude."
After: "Zendesk, Salesforce Service Cloud, SQL reporting, knowledge base authoring, CSAT 96%, WFM adherence 98%"

Tools plus metrics beat adjectives. Pair that list with two bullets showing ticket volume and QA scores so Skills and Experience agree.

For deeper formatting rules, read resume skills section: how to make it readable for ATS and humans.

Common skills section mistakes

Keyword stuffing without bullets. Thirty tools in Skills and none in Experience is an automatic trust hit in recruiter review.

Skill bars and star ratings. Visual proficiency meters break in many parsers and look subjective to humans. Use plain lists.

Skills trapped in columns or tables. Sidebars and multi-column Canva templates often export skills as garbled text in Workday previews.

Outdated versions nobody uses. Listing COBOL when you have not touched it in twelve years invites technical questions you cannot pass.

Soft skill walls. Communication, leadership, and teamwork with no proof lines read like filler. Show them in bullets or cut them.

Wrong section header. Creative labels fail mapping. Stick to Skills or Technical Skills unless the employer asks for a federal CV format with a different convention.

Verify skills match the posting before you apply

Listing skills is guesswork until you score the file against the req. Upload your resume and posting to HireFlow's free ATS resume checker and fix gaps in both Skills and Experience in one pass.

Use job match score to see which required keywords are missing entirely. Add those to Skills only after you write or rewrite a bullet that proves them.

Building from scratch? Use the free resume builder for a single-column layout, then paste the grouped Skills block from step four. Export PDF and run the checker before upload.

When skills gaps show up in a cover letter field, mention one top tool in the opener and point to the matching bullet. The cover letter generator helps draft that line without repeating the whole skills list.

List skills that parsers and recruiters both believe

How to list skills on a resume comes down to three moves: pull keywords from the posting, cut anything you cannot prove, and format the block in plain text where Workday can read it.

• Highlight must-have tools in the job description first.
• Pair every top skill with a dated bullet and metric.
• Use a standard Skills header in a single-column file.

Open your resume tonight, trim the skills list to ten defensible items, rewrite one bullet per must-have, and run the free resume check against a role you want this week. That is how skills sections stop looking like tag clouds and start matching what employers search for.