8 min read
Your skills line reads like a tag cloud: Python, leadership, Excel, teamwork, SQL, Agile, problem-solving. Forty items, no callbacks. You're not unqualified. You're making parsers and recruiters hunt for proof that isn't on the page yet.
Check your resume for free against the posting before you upload again. Most rejections I see start with a Skills block that never shows up in Experience, not with a missing comma.
Tonight's job: list skills on a resume in a format Workday and Greenhouse can map, tied to bullets a recruiter'll believe on a ten-second scan. Work the four checklists below in order. You'll know you're done when every must-have from the posting appears twice: once in Skills, once with a date and metric.
Quick Wins
- Circle ten must-haves in the posting and mark which already appear in Experience.
- Delete any skill you cannot defend with a project story on a phone screen.
- Move Skills out of sidebars and rename the header to Skills or Technical Skills.
What the skills block actually does for parsers
The skills section is a scannable index of tools, methods, languages, and certifications. Parsers in Workday, Greenhouse, Lever, and iCIMS usually map a block labeled Skills into its own field. Recruiters use it to confirm you match the posting before they read every bullet.
The list supports Experience; it does not replace it. Dated bullets with metrics win trust. A comma line without proof reads as keyword stuffing on recruiter review.
I've screened stacks of these in Workday and Greenhouse, and the file that passes isn't the longest skill list. It's the one where Tableau in Skills also shows up in a bullet about dashboards built last quarter.
Hide skills in a two-column Canva layout or a footer icon row and the parser may never see them even when a human could. That is why placement and header label matter as much as which words you pick.
How to list skills on a resume tonight
Work these four checklists in order. Finish one group, save, then move to the next. Skipping straight to keyword stuffing while Skills still sits in a sidebar wastes the upload.
Checklist 1: Pull and trim keywords
- Highlight required and preferred skills in the posting separately.
- Mirror exact spelling: Microsoft Excel, not MS Office alone.
- Keep only skills you used in the last five to seven years unless the req asks for legacy depth.
- Cut anything you cannot explain on a call with a project example.
Before: "Python, R, SQL, Java, machine learning, Excel, Tableau, leadership, communication, Agile, Scrum, Jira, Salesforce, SEO, public speaking."
After: "Python, SQL, Looker, Excel, A/B testing, lifecycle email, Salesforce, Google Analytics"
Checklist 2: Place and label the block
- Default order: Contact, Summary (optional), Experience, Skills, Education.
- Entry-level: Skills above Experience when projects carry the proof.
- Header label: Skills or Technical Skills only. Skip Core Competencies or Toolbox.
- Single column. No tables, sidebars, or text boxes for the skills block.
Read how to tailor a resume to a job description when you reorder Skills during a tailor pass for one employer.
Checklist 3: Format plain text parsers read
- No skill bars, star ratings, or icons.
- Separate items with commas or pipes on one or two lines.
- Group by category only when the list runs past twelve items.
- Export at 11 or 12 point Calibri or Arial from Word or Google Docs.
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)
Checklist 4: Tie each must-have to a bullet
- Add or rewrite one Experience bullet per top posting skill.
- Put the keyword in the first eight words when you can.
- Include a date, tool, and outcome in the same line.
- Run a plain-text paste test: copy PDF into Notepad and confirm Skills reads as separate words.
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."
Before: "Customer service, phones, CRM, problem solving, friendly attitude."
After: "Zendesk, Salesforce Service Cloud, SQL reporting, knowledge base authoring, CSAT 96%, WFM adherence 98%"
| Check | Pass signal |
|---|---|
| Posting must-haves in Skills | Ctrl+F finds each required tool on the page |
| Proof in Experience | Each top skill has a dated bullet with a metric |
| Plain layout | Notepad paste shows Skills on its own line |
| Soft skills | Only when the posting names them and bullets prove them |
Listing traps that look fine on screen
Keyword stuffing without bullets. Thirty tools in Skills and none in Experience is an automatic trust hit when a recruiter opens the profile.
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 templates often export skills as garbled text in Workday previews.
Soft skill walls. Communication, leadership, and teamwork with no proof lines read like filler. Show them in bullets or cut them.
Creative section headers. Parsers map Skills and Technical Skills reliably. Core Competencies often lands in the wrong field.
Score skills against the posting before you upload
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.
When a cover letter field asks for one top tool, mention it in the opener and point to the matching bullet. The cover letter generator helps draft that line without repeating the whole skills list.
Ship a skills block recruiters trust tonight
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, 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.
Read more
Frequently asked questions
For most US corporate resumes, place Skills after Experience or after Education for entry-level candidates. Do not bury skills in a sidebar or text box. Use the header Skills or Technical Skills so Workday and Greenhouse map the block correctly. Put your top posting keywords in Experience bullets too, not only in the list.
Aim for eight to fifteen relevant skills for mid-level roles, fewer for focused specialist jobs, slightly more for broad IC roles. Every skill should appear somewhere in your experience bullets or projects. If you cannot defend a skill on a call, remove it from the list.
No for ATS uploads. Graphics, icons, and percentage bars often break parsing or get stripped to blank space. Use plain text lists separated by commas or pipes in a single-column layout. Let experience bullets show depth instead of self-assigned proficiency scores.
Lead with hard skills that match the posting: tools, languages, platforms, certifications. Group soft skills sparingly and only when the posting names them explicitly, such as stakeholder management or cross-functional communication. Prove soft skills in bullets with outcomes, not adjectives alone.
Mirror posting language naturally in Skills and in Experience. Exact matches help parsers and human reviewers, but comma-stuffing thirty keywords with no proof hurts trust. Pair each must-have skill with at least one bullet that shows how you used it.