How to write the skills section of a software engineer resume
By Mubeen Jawed, founder of ResumeForDev · Updated
List technical skills in three or four labelled groups (for example Languages, Frameworks, Developer Tools, Cloud/Databases), keep each group to the tools you'd be comfortable being interviewed on, and make sure the important ones also appear in your experience bullets. Leave out soft skills, proficiency bars, and basics every engineer is assumed to know.
Key points
- Group by type, one line per group.
- Order each line by relevance to the job, not alphabetically.
- Every important skill should also appear in a bullet.
- No ratings, no “Microsoft Word”, no “team player”.
A simple structure
| Group | Example line |
|---|---|
| Languages | TypeScript, Python, SQL, Go |
| Frameworks | React, Next.js, Node.js, Express, FastAPI |
| Data & Cloud | PostgreSQL, Redis, AWS (ECS, S3, Lambda), Docker |
| Tools | Git, GitHub Actions, Terraform, Datadog |
Examples by role
| Role | Lead with | Often expected |
|---|---|---|
| Frontend | TypeScript, React, Next.js | CSS, accessibility, testing (Jest, Playwright), performance |
| Backend | Go / Java / Python / Node.js | PostgreSQL, Redis, REST or gRPC, queues, Docker |
| Full stack | TypeScript, React, Node.js | SQL, auth, deployment, CI/CD |
| DevOps / SRE | Kubernetes, Terraform, AWS/GCP | Linux, monitoring (Prometheus, Grafana), incident response |
| Data / ML | Python, SQL, Spark | Airflow, dbt, PyTorch or scikit-learn, warehouses |
| Mobile | Swift / Kotlin / React Native | App Store releases, offline storage, push notifications |
What to leave out
- Proficiency bars and star ratings. Parsers can't read them and reviewers don't trust them.
- Soft skills (“communication”, “leadership”). Show them in bullets instead.
- Office software and operating systems everyone uses.
- Anything you touched once in a tutorial and can't discuss.
ResumeForDev checks this for you: its skills rule awards points when skills are grouped and when they overlap with what your bullets actually describe. Its fabrication guard also removes any skill from the generated resume that you never mentioned. Read more about ATS-friendly formatting.
Frequently asked questions
- How many skills should a software engineer list?
- Usually 12–25 across all groups. Enough to cover the job post's stack, few enough that each one is credible.
- Should the skills section go at the top or bottom?
- In the Jake-style layout it goes after Experience and Projects. If you're changing stacks, moving it higher can help the reader place you quickly.
- How many skills should I list on a resume?
- About 8 to 30 technical skills, grouped into three or four categories. List only what you could discuss in an interview.
- Should I list soft skills on a developer resume?
- Not as a list. Show communication, leadership and collaboration in bullets instead, for example mentoring, leading a project or working with design.
Keep reading
- GuidesWhat makes a software engineer resume ATS-friendlyWhat an ATS resume is, how applicant tracking systems read developer resumes, the ATS-friendly resume format to use, and how keyword matching really works. No myths, no fake scores.Read
- GuidesHow to tailor a developer resume to a job descriptionA repeatable 15-minute process to tailor a software engineer resume to each job post: extract keywords, reorder bullets, and close real gaps without inventing experience.Read
- GuidesHow to write a software engineer resumeStep by step: how to write a one-page software engineer resume, with section order, a bullet formula, skills, projects, resume examples, and what ATS software and recruiters check.Read
- GuidesHow to write a front end developer resumeHow to write a front end developer resume: UI work written as outcomes, performance and accessibility numbers, React and TypeScript skills, projects, and example bullets.Read
- GuidesHow to write a backend developer resumeHow to write a backend developer resume: APIs, databases and services written with scale and latency numbers, a focused skills section, and example bullets.Read
- GuidesHow to list certifications on a software engineer resumeWhere to put certifications on a tech resume, the exact format to use, which certs are worth listing for developers, cloud, security and IT roles, and how to show ones in progress.Read
- GuidesResume keywords for software engineers, by roleThe keywords recruiters search for on software developer, data analyst, data science, machine learning, cyber security and DevOps resumes, and how to add them without keyword stuffing.Read