The technical skills to put on a resume are the languages, frameworks, cloud platforms and tools a posting names, grouped by category and limited to what you could discuss in an interview.
Picture a developer with years of collected tools and a posting that names only some of them. The skills section is where that mismatch gets fixed: cut to what the role needs, group what remains, and let experience bullets carry the rest. This shortlist covers only that section. For the rest of the document, see how to write a tech resume, and for the wider picture see career advice for tech professionals.
Skill categories at a glance
A tech skills section works best as a short set of labelled groups rather than one long line. The table below shows what each group holds and how to decide what goes in it.
| Category | What belongs there | Planning use |
|---|---|---|
| Programming languages | Languages you could use or answer interview questions about today | Lead with the ones the posting names most often. |
| Frameworks | Frameworks built on those languages | List the ones that match the stack in the posting. |
| Cloud platforms | Platforms and services you have actually worked with | Match the provider the employer uses where you can honestly do so. |
| Databases | Database technologies you can discuss | Keep to the ones relevant to the role. |
| Version control | Git | Treat it as a baseline rather than a headline skill. |
| Soft skills | Not a list category | Prove them in the summary or experience bullets. |
The category split follows HireZapp’s keyword grouping, and the guidance on Git and soft skills comes from MatchResume’s tech skills guide.
Programming languages and frameworks
Programming languages and frameworks are the first things a recruiter scans for, so they sit at the top of the section. Start with the languages the posting names, then add the frameworks that run on them.
For front-end and full-stack roles, one source expects experience with a modern JavaScript framework, such as React, Angular or Vue, according to software engineer Matthew MacRae-Bovell. Those names are examples of the category, not a checklist. List the framework or frameworks you have used, because a posting asking for one of them is not asking you to name all of them.
Cloud platforms and databases
Cloud platforms and databases show that you can work beyond a single machine. How much you claim should match your level.
For students and early-career applicants, the same engineering skills guide asks whether a resume shows familiarity with beginner-friendly cloud services such as AWS S3 and EC2, or equivalent Azure or GCP services. That is a realistic bar for a first role. Naming specific services you have used is more convincing than naming a platform you only read about.
For databases, the same source suggests picking either MySQL or PostgreSQL to highlight. That is useful advice for anyone tempted to list every database they have touched. Choose the one you know best, or the one the posting names, and let it stand for your relational database ability.
Version control and everyday tooling
Version control is the skill most likely to be taken for granted. MatchResume describes Git as assumed for any developer role and notes it is often left off the skills list.
That makes Git a low-risk, low-value line. It costs little to include, but it should never displace a language, framework or cloud service that actually separates you from other applicants. Applicants moving from non-developer work, where Git is not assumed, may reasonably keep it visible.
Soft skills for tech jobs
Soft skills for tech jobs, such as communication and collaboration, belong in your summary or experience bullets as proof, according to MatchResume. So the answer to whether to list them in the skills section is generally no.
The reasoning is practical. A bare word in a list asserts a quality, while a bullet that describes what a team delivered demonstrates it. Keep the skills section for hard skills a reader can check against the posting, and put teamwork where there is a result attached to it.
Choosing skills for a specific posting
Tailoring starts with the posting, because applicant systems compare your words with its words. HireZapp explains that these systems scan resumes for specific words and phrases from the job description to calculate a match score. Keyword matching rewards the exact terms an employer chose.
A repeatable method comes from MatchResume: pull the top 10 recurring skills from 5–10 job descriptions for your target role. Recurrence matters because it separates what the role market expects from what one employer happened to mention. Skills that recur belong near the top of their group. A skill that appears in a single posting earns a place only on the resume you send to that employer.
Tailoring is selection, not invention. If a recurring term is something you have not used, leave it off and consider the learning route covered further down.
Grouping, ordering and sizing the section
Group skills by category and keep the whole section compact. MatchResume points out that a flat alphabetical skills dump is readable by applicant systems but unfriendly to recruiters, and it calls 12–20 grouped skills the sweet spot. Treat that as a guide to the overall size, not a target to fill.
- Order the groups by relevance. A back-end posting should put languages and databases ahead of anything else, while a cloud-heavy role can open with platforms.
- Order within groups by recurrence. The terms that appeared most often in your sample of postings go first.
- Use clear labels. Labels such as languages, frameworks, cloud platforms and databases mirror how postings are written, which helps both a human scan and keyword matching.
Proficiency levels and skills you are still learning
The simplest filter for any skill is MatchResume’s test: list a skill only if you could answer an interview question about it or produce work with it today. That test also answers the proficiency question. Rating bars or self-assigned labels add little when the entry has already passed a standard that an interviewer can check.
A skill you are still learning therefore stays off the list until it passes that test. Until then, build the evidence. Matthew MacRae-Bovell suggests starting a side project with a friend as one way to pick up a skill. Once you have produced work with it, list it, and describe the project in a bullet so the claim has support.
Decision checklist
- Gather postings for your target role and note the terms that recur.
- Remove anything you could not discuss or use today.
- Sort what remains into labelled categories and order them by relevance to the role.
- Move soft skills out of the list and into summary or experience bullets.
- Reword terms to match the posting’s own phrasing, then move anything that needs context into your cover letter. See how to write a cover letter for a tech job for that step.
Frequently asked questions
Should I list Agile or Scrum as skills?
MatchResume advises against listing Agile or Scrum as a skill and recommends showing them in experience context instead. A bullet describing how you worked in a team that used the method does more than a single word.
Should I include both an abbreviation and the full name of a tool?
Yes, where space allows. HireZapp recommends including different versions of a term, such as K8s and Kubernetes, because a match score depends on the words a posting uses.
Do AI tools need their own category?
MatchResume describes AI tool proficiency as a distinct category in 2026. If you have genuine experience with such tools, give them a separate labelled group rather than mixing them into languages or frameworks.
