Skills to Put on a Developer Resume in 2026 (By Role)

The skills section looks like the easiest part of a dev resume. You just list your stack right?

Then you sit down to write it and suddenly it's 30 items long. Every language you touched in school, three frameworks you tried for a weekend, "HTML/CSS" next to "Kubernetes" and somehow "Microsoft Word" at the end. Recruiters see this all the time and honestly it makes it harder for them to tell what you're actually good at.

So here's how to pick skills that help, plus what usually works for the most common dev roles.

The trick most people miss: start with the job post

Don't write one skills list and send it everywhere. Open the posting and look at what shows up in the requirements or comes up more than once. Those are the things the recruiter is scanning for and probably what the hiring software is matching too.

If the posting says "PostgreSQL" and you have used Postgres, write PostgreSQL. Not "relational databases." If they say "TypeScript" and your resume says "JS/TS," spell it out. Use their words when they're true for you.

Then fill in the rest with things you're genuinely strong at that fit the role. Somewhere around 10 to 15 items is plenty for most devs.

Group them so they're easy to scan

A wall of comma separated tech is hard to read. Split it into a few lines instead. Languages on one line, frameworks and libraries on another, then tools and platforms. A recruiter who isn't technical can still find "React" in two seconds that way, and so can the ATS.

Skills by role

Treat these as a starting point, not a list to copy.

Frontend

JavaScript and TypeScript, a main framework (React, Vue or Angular, pick the one you actually use), CSS and a styling approach like Tailwind, testing with something like Jest or Playwright and accessibility basics. If you have worked with Next.js or a design system, those are worth calling out.

Backend

One or two main languages (Node.js, Python, Go, Java), databases you have used in a real project (PostgreSQL, MongoDB, Redis), API design (REST or GraphQL), auth and some cloud experience. Mention message queues or caching only if you have actually used them.

Full stack

Basically the best of both lists above, but be careful not to list everything. Pick the stack you'd want to work in and show it end to end. A clear "React, Node.js, PostgreSQL, AWS" tells a better story than 20 scattered tools.

Data and analytics

SQL first, always. Then Python with pandas, a viz tool like Tableau or Power BI, maybe dbt or Airflow if you have used them and any cloud warehouse like BigQuery or Snowflake. Excel still counts here, don't be shy about it.

DevOps and cloud

A cloud platform (AWS, GCP or Azure), Docker, Kubernetes if you have actually run it, CI/CD tools like GitHub Actions or GitLab CI, infrastructure as code with Terraform and monitoring tools. Certifications like AWS Solutions Architect are worth listing here because they actually carry weight in this area.

QA and testing

Test automation frameworks (Selenium, Cypress, Playwright), a language you write tests in, API testing with Postman, CI integration and bug tracking tools like Jira. If you have done performance testing name the tool.

Students and bootcamp grads

You don't need a huge list. List the stack from your best projects, Git (everyone should list Git) and anything from coursework you'd be happy to talk about. If you speak more than one language add a line for it, a lot of Canadian teams work with clients and users in other languages.

What about soft skills?

Writing "team player" or "strong communicator" in your skills section doesn't prove anything. Anyone can type it.

Showing it does. A bullet like "Wrote onboarding docs that cut new dev setup time from 2 days to 3 hours" shows communication without saying the word. "Ran code reviews for 4 junior devs" shows leadership. So keep soft skills out of the list and put them in your experience bullets where you can back them up.

Mistakes that make a dev skills section useless

Listing 30 technologies is the big one. It turns into noise and it invites interview questions you can't answer. Skill bars or "Python ●●●●○" are another, nobody knows what four dots means and parsers can't read them. Listing outdated or super basic stuff like "Windows" or "internet research" wastes space. And listing anything you can't talk about for five minutes is risky, because a technical interview is exactly where that catches up with you.

Match your skills to every job without starting over

Tweaking your skills for each application doesn't have to take long. If you want to speed it up, ResumeStart's resume tailoring compares your resume to the job post you paste in and shows which skills they're asking for that your resume doesn't mention yet. You decide what to add, nothing changes without you.

The bottom line

A good dev skills section is short, grouped and matched to the job. Start with the posting, use their exact terms where they're true for you, keep it to what you'd defend in an interview and let your project and experience bullets prove the soft skills.

Do that and this little section does a lot more work than you'd expect.