Resume keywords for software engineers
The terms engineering postings actually repeat, grouped by where they belong on the page. Copy nothing you have not done. Every term below is only worth adding if you can point at the work behind it.
What software engineers postings actually ask for
Engineering adverts are unusually literal. They name the language, the cloud, the orchestrator and the database, often in the same sentence, and a recruiter later searches their applicant tracking system for those exact strings. That is why an engineer with eight years of Go experience gets filtered out by a Go role: the CV says Golang and the search said Go, or the CV says k8s and the search said Kubernetes. Write both forms once and the problem disappears.
The keywords, grouped
Grouped by the job each one does, because where a term belongs on the page matters as much as whether it is there at all.
| Group | Terms a posting uses | Why this group matters |
|---|---|---|
| System and craft | system design, distributed systems, microservices, API design, data modelling, concurrency, performance optimisation, scalability, code review, automated testing, debugging, technical design document | The nouns that describe what you can be trusted to own. These matter more than the language list and are the part most CVs leave out. |
| Languages and frameworks | Go, Python, Java, TypeScript, JavaScript, C#, Rust, Kotlin, React, Node.js, Spring Boot, Django, SQL | List only what you would be willing to be interviewed on this week. Spell out anything with a common short form: Go (Golang), TypeScript (TS), JavaScript (JS). |
| Infrastructure and tooling | AWS, GCP, Azure, Docker, Kubernetes (k8s), Terraform, CI/CD, GitHub Actions, observability, Datadog, Prometheus, PostgreSQL, Redis, Kafka, infrastructure as code | The cluster of terms that decides whether a platform or infrastructure role surfaces you at all. Name the cloud you actually used, not all three. |
| How you work | Agile, Scrum, on-call, incident response, postmortem, SLO, mentoring, pair programming, technical documentation, cross-functional | Seniority is signalled here, not by a number of years. On-call and incident response say more about your level than any adjective. |
| Verbs that carry evidence | shipped, migrated, refactored, profiled, instrumented, scaled, hardened, decomposed, owned, mentored | Open bullets with these rather than with built or worked on. Each one implies a before and an after, which is what forces a number out of you. |
Where each group belongs on the page
Skills block: languages, frameworks, infrastructure
A compact, honest list near the top. Group it (Languages, Infrastructure, Data) rather than running forty items together. This block exists to be found by a search, not to be read.
Bullets: system and craft terms
system design, distributed systems and performance optimisation mean nothing in a skills list. In a bullet with a latency number attached, they are the whole argument.
Headline: the two that define you
Your discipline plus the one or two technologies you want the next role built on. 'Senior Backend Engineer | Go, Kubernetes, Payments' does more work than a paragraph.
Nowhere: proficiency bars and logo grids
A five-star rating for Python is unverifiable and parsers read the image as nothing. Cut them and put the space into evidence.
A keyword only counts inside evidence
Both columns below contain the keyword. Only one of them survives a hiring manager reading it, which is the whole reason a keyword list is not a strategy on its own.
The keyword is present in both. Only the second proves it.
Skills: performance optimisation, profiling, PostgreSQL
Profiled the 12 slowest endpoints and added covering indexes, cutting p95 latency from 840ms to 210ms and removing a planned read replica from the roadmap.
One of these survives a technical interview.
Experience with Docker, Kubernetes and CI/CD pipelines.
Migrated 14 services from EC2 to Kubernetes with zero customer-visible downtime, cutting deploy time from 40 minutes to 6.
How these terms appear in a real posting
Where these CVs lose points
- A logo wall instead of a skills block. Thirty technologies at the top signals that none of them is yours. Cut to what you would defend in an interview.
- Seniority claimed in years, not scope. '8 years experience' is weaker than 'owned the payments service through a 4x traffic increase'.
- Performance work with no numbers. 'Improved performance' is the single most common wasted bullet on an engineering CV.
- One form of an acronym only. Write CI/CD and continuous integration, Kubernetes and k8s, once each.
- Side projects competing with production work. A hobby repo above a system that took real traffic reads as thin.
Check your CV against the posting in front of you
This page lists what software engineers postings tend to ask for. The advert you are answering today weights them differently, and that is the list that decides your application. Paste both into the checker at the top of this page to see which of its terms your CV never mentions, or read the worked Software Engineer CV example to see the terms sitting inside real bullets.
Get the gaps fixed, not just listed
Paste the job link and FitMyCV rewrites your CV and cover letter against that posting, keeping your real experience and your real numbers.
Software Engineer resume keywords: FAQ
How many programming languages should I list?
Three to five you would be happy to be tested on, ordered by how well you know them. Listing ten reads as a course history rather than a working set, and the interview will find the gap in about four minutes.
Should I write Go or Golang?
Write Go in the skills block and Golang once in a bullet, or the reverse. Recruiters search both. This is the cheapest keyword fix on an engineering CV and almost nobody does it.
Do I need every cloud on my resume?
No. Name the one you actually used at depth. Claiming AWS, GCP and Azure together usually means a tutorial on two of them, and an interviewer will pick the one you are weakest on.
Where do I put open source contributions?
In their own short section below your experience, and only when the project is recognisable or your contribution was substantial. A merged typo fix costs you the line it sits on.
Can I just copy these keywords onto my resume?
No, and a CV built that way falls apart in the first interview. Use the list as a checklist against work you have actually done. A term you cannot evidence in a bullet is a term that moves your rejection from the screen to the phone call, which is worse for you, not better.
How many keywords should a resume have?
There is no target number, and any tool that gives you one is guessing. What matters is coverage of the specific posting in front of you: the terms it repeats should be findable on your CV, in your own evidence. Twelve well placed terms beat forty in a list.
Ready to stop being ignored?
Join job seekers landing interviews faster with AI-tailored applications. Lifetime access from $16.99.