What skills to put on a resume, and how many

The skills section is the part of a resume most likely to be searched by keyword, either by an applicant tracking system or by a recruiter using GitHub-style search filters. It is also the part most likely to be padded until it stops meaning anything.

Relevant beats comprehensive

List the tools, languages, and platforms you have genuinely used to do real work, not everything you have ever installed. A list of eight to twelve items grouped by category reads as a filtered judgment about what actually matters. A list of forty reads as an attempt to match every keyword in every job posting at once, and reviewers notice that pattern quickly.

If you are unsure whether something belongs, ask whether you could talk about it competently for two minutes in an interview. If not, leave it off.

Group by category

A flat list of twenty items in random order is harder to scan than the same items sorted:

Languages: TypeScript, Python, Go
Frameworks: React, Next.js, Django
Infrastructure: AWS, Docker, PostgreSQL

This structure also happens to match how applicant tracking systems and recruiters typically search: by category, then by specific tool.

Match the job listing, honestly

Read the specific job listing and prioritize the skills it mentions, assuming you genuinely have them. This is not about gaming an ATS keyword match, though it does help with that; it is that a hiring manager wants to see quickly whether you have the specific things they need, not a general inventory of your career.

Do not add a skill you do not have just because it appears in the listing. It tends to surface in the interview within the first few questions, and the damage from an unconvincing answer outweighs whatever the keyword match gained you.

Skip ratings and progress bars

Self-assessed skill bars, five stars for Python, three for Go, are common in visual resume templates and worth avoiding. They carry no real information (your four stars and someone else’s four stars are not comparable), they are invisible to a parser, and they invite exactly the kind of scrutiny you do not want: why four and not five.

For soft skills, show them instead of listing them

“Strong communicator” and “team player” on a skills list are close to meaningless, since almost every resume claims them and none of them are checkable. If a soft skill matters for the role, it is usually better demonstrated inside an experience bullet: “Led a cross-team migration involving four engineering groups” shows collaboration and leadership without naming either word directly.

For developers specifically: let the code confirm the list

A skills section that says “Python, Go, TypeScript” is a claim. A Projects section with real repositories written in those languages is the confirmation. Reviewers who know what to look for check the second thing anyway, so it is worth making it easy to find.

resumefromgit.com builds that connection automatically: it reads a public GitHub profile and generates a language breakdown from actual repository data, so the skills section on the resulting resume is backed by a verifiable history rather than a self-reported list.