The skills section does two jobs: exact-string matching for the ATS, and a fast capability scan for the human. Both are served by a short, grouped, honest list — and ruined by a long one.
Group, don't dump
An unbroken comma-separated line of 30 items is unreadable. Three or four labelled groups of four to six items each can be scanned in seconds.
Skills: Python, Java, HTML, CSS, JavaScript, React, Node, MySQL, MongoDB, Git, GitHub, VS Code, Windows, Linux, MS Word, MS Excel, PowerPoint, Teamwork, Leadership, Communication
Languages: Python, JavaScript, SQL Frameworks: Django, React, FastAPI Data & infra: PostgreSQL, Redis, Docker, AWS (EC2, S3, RDS) Practices: CI/CD, code review, unit testing
The cut list
- MS Office — assumed, unless the role is Excel-heavy; then say what you can do in it
- Operating systems — nobody hires on 'Windows'
- Your IDE — VS Code is not a skill
- Soft skills as bare words — 'communication' proves nothing; a bullet about presenting to a client does
- Anything you last used three years ago and couldn't discuss now
Proficiency bars, stars and percentages
Delete them. They parse as meaningless graphics, they're self-assessed so no reader trusts them, and 'Python 80%' invites the question of what the missing 20% is. If levels matter, group them: 'Strong: Python, SQL. Working knowledge: Go, Kotlin.'
How many is right
Ten to eighteen for a technical role, six to twelve for most others. Beyond that, the list stops being a signal — a candidate who claims 40 skills has told you nothing about what they're actually good at.
Order matters
Put the job's required skills first within each group. A recruiter scanning for 'Kubernetes' finds it faster, and so does an eye-tracking-driven six-second read.
Put this into practice
Build, score and tailor your resume with JotCV — free plan, no card needed.
See which skills a job wants