A skills section helps two readers: the recruiter skimming for a match, and the applicant tracking system (ATS) searching for keywords. Both want the same thing: the skills the job asks for, named the way the job names them.
Group them
A long comma-separated list is hard to read. Group skills by kind, a line each:
- Languages: TypeScript, Python, SQL
- Frontend: React, Next.js, CSS
- Cloud: AWS (Lambda, DynamoDB), Terraform
- Leadership: hiring, mentoring, roadmap planning
In JSON Resume each group is a skill with a name and its keywords, and every theme shows them that way.
Use the job's words
If the post says "Kubernetes", write "Kubernetes", not just "container orchestration". Spell out abbreviations once if both are common: "Search engine optimisation (SEO)".
Only what you'd talk about
Every skill you list is fair game in an interview. Leave out tools you used once years ago. "Microsoft Word" and "email" don't need listing for most jobs.
Show them, too
Skills in a list are claims; skills in your work experience are evidence. The strongest resumes mention the important ones in both places: "Moved billing to Stripe and cut failed payments by a third" proves more than "Stripe" in a list.
Levels
Self-rated levels ("Expert", five stars) mean little to readers. If you include them, keep them honest and consistent, or leave them out.
Make your resume, or see example resumes by job title.