List 8 to 15 skills, grouped into two or three labeled clusters, ordered by relevance to the job you are applying for. Every skill should be one you can discuss in an interview without flinching. A wall of 30 skills does not read as versatile — it reads as unfiltered, and it buries the five that actually match the posting.
The skills section has two readers. The recruiter uses it as a checklist against the job description, and the checklist has maybe six items on it. The parser extracts it into a searchable profile, where a skill either appears or does not — listing 30 things does not rank you higher on any of them. Neither reader rewards volume; both reward the presence of the specific skills the posting names.
Volume actively costs you with the human. A tight list of ten signals judgment: this person knows what matters for this role. A sprawl mixing Kubernetes with Microsoft Word says the list has never been curated, which casts a small shadow on every other claim on the page. The skills you cut were not helping; the noise they created was hurting.
Group by type with plain labels: Languages, Tools, Platforms for engineers; Analytics, Marketing Platforms, Design for marketers. Two or three groups, each on one line, reads instantly. Within each group, order by relevance to the target role, not alphabetically and not by personal fondness — the first two items in each group get the most eye time.
Match the posting's vocabulary exactly where it is honest to do so. If the job says Google Analytics 4 and you wrote analytics tools, the recruiter's search and the recruiter's eye both miss you. Spell out acronyms once when the long form is also searched — Search Engine Optimization (SEO) covers both queries.
Include the hard skills the role runs on: languages, frameworks, platforms, certifications, methodologies, spoken languages where relevant. Leave out defaults implied by any office job — email, Microsoft Office, internet research — and leave out soft skills as list items. Communication and leadership in a skills list are unverifiable filler; the same qualities carry weight only as achievements in bullets, where evidence backs them.
The interview test is the final filter: anything you list is fair game for a deep question. Rate-limiting your list to what you can defend also solves the honesty problem automatically — a skill you would hedge about live is a skill that should not be on the page.
No — as list items they are unverifiable and every resume has them. Prove soft skills in experience bullets instead: led a 6-person team through a migration demonstrates leadership better than the word leadership ever can.
Skip bars, stars, and percentages — they are unparseable decoration and invite awkward calibration questions. If a distinction matters, use words sparingly: fluent Spanish, working knowledge of Go. Otherwise, listing the skill implies working competence.
For technical roles, near the top — recruiters checklist it early. For roles where experience is the sell, below your work history. Either way, keep it compact: two or three labeled lines, not a column of twenty bullets.
The free scorer compares your skills section against the job description and shows exactly which required keywords are missing.
