Resume sections
Resume skills: list them where the parser looks
List skills as grouped nouns a parser can file: tools, methods, languages, and licenses. Repeat the same words inside bullets you can defend, not only in a footer cloud. Workday and Greenhouse search those strings; a soft-skill paragraph and star ratings usually vanish or read as padding.
Written by EnhanceCV Editorial Team·Editorial review: CPRW
Published August 27, 2026·Last updated August 27, 2026

Key takeaways
- · Copy nouns from one posting — tools, methods, licenses — then keep only the ones you can explain on a screen.
- · Give Workday and Greenhouse a labeled Skills block in the body, not icons, bars, or a paragraph buried under hobbies.
- · Repeat the same nouns inside experience bullets so search and humans see them in context.
- · Soft skills belong in a result line, not as a list of personality adjectives.
- · Run the ATS checker against the posting before you upload; a missing Skills heading is a common miss.
Group the nouns the posting would actually search
Key takeaway: A skills section is a filing cabinet, not a personality essay. Parsers and recruiters look for labeled groups of tools, methods, and licenses.
Most skills sections fail for a boring reason: they try to be complete. People dump every class, weekend course, and personality trait into one block, then wonder why Greenhouse search still misses them for the one tool named in the posting. You are not writing a biography of everything you have ever clicked. You are building an index of nouns that this job uses, in words you can defend when a recruiter asks “walk me through that.”
Print the job ad or split-screen it. Highlight tools (PioneerRx, ADP Workforce Now, ServiceTitan), methods (FIFO, HACCP, Kanban), languages, and licenses. Those highlighted words are the only skills that earn a place on the version you upload. If a line on your current resume does not help that list, move it to a master file. A master document can be messy. The Workday attachment should be the master filtered for this posting. That is the same method as tailoring a resume to a job, applied to one section.
Name tools the way the employer names them. If the posting says “ADP Workforce Now” and you only wrote “payroll software,” the recruiter’s saved search in Greenhouse will not surface you. You may add a short parenthetical once — “ADP Workforce Now (payroll)” — but do not invent a product you used for ten minutes in a demo. Taleo and iCIMS will not rescue you in the interview when someone asks which screens you actually touched.
Hard skills, methods, and the soft-skill trap
- Hard skills: named systems and licenses. PioneerRx, Epic Cadence, OSHA 10, Class B CDL, QuickBooks Online.
- Methods and environments: FIFO, cycle counts, bilingual English/Spanish, night shift, HIPAA front desk — still nouns, still searchable.
- Soft skills: put them in a bullet with a result (“calmed 15–20 walk-ins during vaccine clinic overflow”), not as “excellent communicator.”
- Do not rate yourself with bars, dots, or “10/10 Excel.” Humans distrust the scale; many parsers ignore the graphic entirely.
If you are applying to two very different jobs — grocery overnight and junior benefits coordinator — keep two skills blocks. LinkedIn can be broader. The file you upload to Workday cannot. For what else belongs on the page, use what to put on a resume. This article stays on the skills block, but the block fails if the rest of the file never parses.
Give Workday and Greenhouse a skills block they can map
Key takeaway: Pretty skill clouds and sidebar icons drop nouns. A boring heading that says Skills, in the body of the file, is what search actually queries.
Workday, Greenhouse, Taleo, Lever, and iCIMS do not admire your layout. They extract text and try to hang it on fields: contact, employers, dates, education, and often a skills or qualifications blob. If your tools live in a two-column sidebar, a donut chart, or a header text box, the extract can come back empty. A recruiter then searches “ServiceTitan” and you are simply not in the result set, even though the PDF looks complete on your laptop.
Use one column. Put a heading the ATS already maps: Skills, Technical Skills, or Skills and Licenses. Then use short labeled lines, not a paragraph. “Pharmacy systems: PioneerRx, QS/1. Compliance: HIPAA, NDC checks.” is a block a human can scan in two seconds and a parser can tokenize. A 90-word paragraph that starts with “I am proficient in a wide variety of…” is how nouns get lost between adjectives.
Repeat the important nouns inside experience bullets. Greenhouse keyword search is not limited to the skills field — it often searches the whole parsed text — but Workday recruiters still filter on structured skills when those fields populated. One mention in a buried paragraph is weaker than a labeled line plus a bullet that shows you used the tool on a shift. For the layout rules around columns and headings, stay with the ATS resume guide; this page is about which words go in the block.
Dates do not belong in the skills section. Licenses do, with an expiry if the posting cares: “ServSafe Manager, exp. 2027.” Do not hide a CDL, pharmacy tech registration, or forklift card in a hobby line. Do not replace the word Skills with “What I bring” or a sparkle icon. Lever and iCIMS are literal; they are not guessing your metaphor.
File type, fonts, and what not to draw
- Upload .docx or a tagged, selectable-text PDF. A skill grid exported from Canva as an image is a brick.
- Calibri, Arial, Georgia, or the system font in Enhance CV. No script, no ultra-thin display face for the skills line.
- Body 10.5–12 pt. If a recruiter pinches-to-zoom on a phone to read your tool list, the type is too small.
- No photos, no skill bars, no logos of products. Product names as text beat a tiny Salesforce cloud Workday cannot read.
Test the file the way the ATS will. Select all in Preview or Word. If you cannot highlight “PioneerRx,” neither can Greenhouse. Then run the ATS checker so you are not guessing which nouns survived. Pair that with resume keywords when the posting is a wall of tools and you need a method to pick which ones to keep.
Rewrite weak skills lines: three before-and-after transforms
Key takeaway: A skills dump describes a catalog. A grouped line plus a proof bullet describes you. If the block could sit on anyone’s resume in that title, it is not finished.
Recruiters skim the skills block in seconds, then look for the same nouns beside a shift, a caseload, or a queue. “Proficient in Microsoft Office” hides all three. Below are three rewrites we use constantly in edits — pharmacy tech, grocery overnight, and bilingual benefits admin. Steal the grouping pattern, not the facts. If a bullet needs a stronger verb after you place the noun, keep resume action verbs open beside this page.
Before
Skills: excellent communication, Microsoft Office, teamwork, pharmacy, fast learner, customer service.
After
Pharmacy systems: PioneerRx, QS/1. Compliance: HIPAA, NDC verification. Languages: English. Shift: evenings, drive-thru.
Before
Proficient in many store systems and helping the team with freight and customers as needed.
After
Store ops: handheld RF scanner, planogram resets, shrink logs. Equipment: electric pallet jack (in-house certified). Availability: overnight.
Before
HR skills including payroll, benefits, onboarding, and being a people person who thrives in fast-paced environments.
After
HRIS: ADP Workforce Now (payroll, new-hire records). Benefits: open enrollment support, COBRA packets. Languages: English/Spanish.
If you do not have a branded tool, use the method plus the scope: “Cycle counts: 4 aisles, twice weekly” is still a noun cluster. “Detail-oriented” is not. Three to six labeled groups beat a comma soup of twenty tools you touched once. Older or irrelevant tools go on the master file, not the footer of the PDF you send to Workday.
Stop adding soft skills as a separate stacked list. One proof bullet under the most relevant job does more for a human than five adjectives. For line-level patterns after the nouns are placed, use resume bullet points. The skills block and the bullets should share vocabulary, not duplicate the same sentence twice.
A 12-step playbook for a skills section you can finish tonight
Key takeaway: Do the steps in order. Designing skill bars first is how people ship a beautiful file that Greenhouse stores without a single tool name.
This is an editing sequence, not a theory. Block 45 minutes. Have the job ad, your last resume, and a notes app. If you prefer to type inside a known-good layout, start in the Enhance CV builder and paste groups as plain lines.
- Save the job ad. Circle every tool, method, license, language, and shift pattern. Ignore adjectives like “dynamic” and “self-starter.”
- Open a new file (do not overwrite the master). Put contact details in the body, then experience, then a heading that literally says Skills.
- Make four empty labels: Systems, Methods, Licenses, Languages. Delete a label later if it stays empty. Empty headings look like you forgot a section.
- Under Systems, type only products you have used on a real shift, rotation, or project — not a 20-minute vendor demo.
- Match spelling to the posting when both are true: “QuickBooks Online,” not “quickbooks” and not a sister product you never opened.
- Under Methods, add process nouns the ad uses if you actually ran them: FIFO, cycle count, intake, triage, close-of-day cash.
- Under Licenses, add the credential, issuer if it helps, and expiry if the posting asks. Do not list a lapsed card as current.
- Languages: name them and the context (phone, documents, patients). “Bilingual” with no pair is a weak token in Lever.
- Delete any leftover personality adjectives. Move “team player” into a bullet with a number, or drop it.
- Mirror each kept noun at least once in an experience bullet so Greenhouse search and a human see the same word in a story.
- Export selectable text. Confirm you can highlight every tool name. Open the PDF on your phone; if the skills line wraps into a cramped sidebar, flatten to one column.
- Paste the resume and the job ad into the ATS checker. Fix missing headings and noun gaps, then upload to Workday or Greenhouse.
Step 9 is the one people skip. They keep “excellent communicator” because it feels harmless. It costs a line that could have held “HIPAA” or “RF scanner.” Recruiters do not search for adjectives. Parsers do not map them to a skills field in a useful way.
If the posting is a wall of software and you have only two of the five named tools, say so in the summary with the two you have and a close substitute. Do not stuff the other three into a keyword footer. That habit is how resume keywords go wrong, and it is how a Taleo knockout question later exposes the gap.
Do this with skills, skip that
Key takeaway: Most skills advice optimizes for looking well-rounded. Parsers and recruiters optimize for fields and proof.
Use this as a desk-side filter while you edit. If a choice is not in the table, ask: will Workday store the noun, and will a human still understand it at 7 a.m. on a phone?
Parser-friendly vs. parser-hostile skills choices
| Topic | Do | Don’t |
|---|---|---|
| Placement | A Skills heading in the body, after experience (or after education if you are early career). | A sidebar cloud, footer dump, or tools only inside a logo row. |
| Grouping | Systems / methods / licenses / languages, each on its own labeled line. | One 40-item comma list mixing Photoshop, “leadership,” and a forklift card. |
| Soft skills | One result bullet with a volume or audience. | A second list of adjectives under Skills. |
| Ratings | Plain text. Years of use only if they are honest and the posting cares (e.g. “Excel: 4 years”). | Star bars, doughnut charts, or “expert / ninja / guru.” |
| Evidence | The same noun in a bullet with shift, caseload, or queue. | Listing a tool you cannot describe past the login screen. |
| File | Selectable PDF or .docx. Skills as text. | Canva infographic, Pages file, or ResumeSkillsFINAL2.pdf as an image wrap. |
Functional resumes that replace dates with a skills cloud still show up in career-change advice. Greenhouse can parse some of them; humans distrust them because the calendar disappears. If you are changing fields, keep chronology and let the skills block carry the new nouns — see career change resume. Do not make the reader reconstruct when you worked.
Edge cases: licenses, career change, bilingual work, and empty tools
Key takeaway: The method stays the same. You only change which group sits first, and how honest the substitute line is.
License-heavy jobs. Lead the skills block with the credential the posting uses as a knockout: pharmacy tech registration, ServSafe, CDL class, CNA, notary. Workday and iCIMS often store those as structured fields on the application form too — match the wording on the form and the resume so the recruiter does not see two different names for the same card.
Career change. Keep old tools that still transfer (Excel, cash handling, HIPAA) and drop the ones that scream the old title if they confuse the new search. A teacher moving toward instructional design can keep Canvas and Google Classroom; they should not lead with “classroom management” as if it were a programming stack. Pair the new nouns with a short project bullet. Details live with career change resume and how to write a resume.
Bilingual roles. Put the language pair on its own line and name the channel: phone, walk-in, documents, patients. “Spanish” with no context is weaker than “Spanish: benefits explanations, COBRA packets.” Greenhouse search often uses the language name; a human needs the channel so they do not assume literary translation.
No branded software yet. Students and first jobs still have methods: POS at a campus café, Google Sheets for a club treasury, Airtable for a bike-shop inventory. Those are skills. “Coursework: Microsoft Office Suite” is weaker than naming the actual file you built. See resume with no experience and student resume.
What to do next today: pick one posting, rebuild four labeled skill lines, mirror each noun in a bullet, then score the file. If the checker flags a missing Skills heading or a tool that never appears in selectable text, fix that before you add another adjective. The Enhance CV home page is the shortest path back to the builder and the checker in one place.
FAQ
How many skills should you list on a resume?
Enough to cover the posting’s real nouns you can defend, usually three to six labeled groups rather than a 25-tool dump. Workday and Greenhouse do not reward length; they reward strings that match a search. If a tool will not come up on a screen, it does not belong on this version of the file.
Should skills go at the top or the bottom of a resume?
After experience for most people, so the nouns still appear in context in bullets first. Put skills higher only when you are early career and the degree plus tools are the main qualification, or when the posting is a wall of systems. Never hide the block in a header image that Workday cannot parse as text.
Do Workday and Greenhouse read a skills section?
They extract text and often fill a skills or qualifications field when the heading is obvious and the nouns are plain. They do not reliably read skill bars, icons, or text baked into a graphic. Repeat key tools in experience bullets as well, because recruiter search frequently runs on the whole parsed document, not only one field.
Are soft skills worth listing?
Not as a stacked adjective list. Soft skills become useful when they sit inside a result: volume, audience, or a messy situation you handled. “Excellent communicator” is not a Greenhouse search term. “Explained COBRA packets in Spanish to 12 terminating employees in one week” is both a skill and a story.
Should you use skill ratings or bars?
No. Recruiters do not share your scale, and many ATS parsers skip or scramble graphics. If years of use matter, write them in text only when they are honest. A doughnut chart of Excel is how a nice PDF becomes an empty skills field in Taleo.
Can you list a skill you used only in a class or a demo?
List class or project tools when they are the closest proof you have, and say so in a project bullet so you are not implying a two-year job. Do not list a vendor demo as production experience. iCIMS knockout questions and live screens will catch the gap faster than the parser will.
How do you tailor skills without stuffing keywords?
Start from the posting’s nouns, keep only what you can defend, and place those words in labeled lines plus bullets. Do not paste the requirements block into a footer. For the full matching method, use resume keywords and tailor a resume to a job. Honesty plus shared language beats a hidden keyword cloud.
How do you check that skills survived an ATS parse?
Select-all in the PDF. If a tool name does not highlight, the ATS may never store it. Then run the Enhance CV ATS checker against the job ad for headings and noun gaps. Fix those, then upload to Workday or Greenhouse. Do not wait for a silent empty search result to tell you the skills block was an image.
Put the skills block in a layout parsers already map
Open the Enhance CV builder, group tools and methods as plain text, then score the file against the posting so the nouns land in the right fields.