Python in 39% of software engineer postings, Go in 32%, Git in 3% or fewer. A measured look at which languages, tools and AI skills postings name, and how to tailor.
Published by MatchCV. Editorial scope and corrections. Example bullets are illustrative; use only skills and results supported by your own experience.
The first version of this guide was a checklist of languages, frameworks and tools, assembled from what's generally true about engineering resumes. It had no counts behind it, and it said so. We've now counted, so this version leads with what 2,301 software engineer postings actually name.
The postings come from 82 companies and were collected on 14 October 2026 as part of a wider study of 13,332 postings. The method and its limits are in the job posting keyword study. The percentages below use at most 20 postings per company (1,137 postings in total), so a company with hundreds of openings can't tilt the ranking.
We tracked 49 languages, frameworks, platforms and practices. These are the ones that appear in at least 5% of postings:
| Term | Share of postings |
|---|---|
| Python | 39% |
| Distributed systems | 39% |
| Go | 32% |
| AWS | 29% |
| Java | 26% |
| Kubernetes | 26% |
| React | 24% |
| TypeScript | 23% |
| LLMs | 19% |
| Machine learning | 17% |
| GCP | 17% |
| CI/CD | 16% |
| C++ | 14% |
| Azure | 12% |
| Kafka | 11% |
| Rust | 11% |
| Kotlin | 11% |
| System design | 11% |
| Terraform | 11% |
| Data structures and algorithms | 11% |
| SQL | 10% |
| JavaScript | 9% |
| Docker | 8% |
| Testing (unit, integration, TDD) | 8% |
| Ruby | 8% |
| PostgreSQL | 7% |
| GraphQL, REST APIs, Node.js | 7% each |
| gRPC, Redis, Linux, MySQL | 5% each |
Three things stand out.
Go beats Java, which will surprise some people. That's a property of the sample. These boards are heavy on cloud, infrastructure and developer-tools companies, where Go is common. We haven't measured banks or enterprise software vendors, so we can't say how they'd rank. Use the ranking as a picture of this slice of the market, not of all hiring.
The basics are rarely named. Git and Agile each appear in 3% of postings or fewer. Postings assume them. Listing them takes space from terms that do discriminate.
The vocabulary is broad, and each posting uses a small part of it. The median posting names five of the 49 terms. Imagine a generic resume containing the 15 most common terms. It would fully cover only 20% of postings. The other 80% name at least one term it doesn't have. For a security engineer the same exercise covers 41%. That is the case for tailoring in numbers: no single stack list fits.
About 30% of software engineer postings ask the candidate to use or be familiar with AI, outside the AI-first companies. Most of those are about how you work, with 56% referring to AI tools in daily work and 15% to building with LLMs or agents. "LLMs" appears in 19% of postings, while named libraries are rare: PyTorch and TensorFlow appear in under 3%.
So a "Copilot and ChatGPT" skills line is unlikely to do much. A bullet that says what you did with an assistant, and how you checked it, matches what postings ask. The AI skills study covers this in detail.
About 64% of software engineer postings state years of experience. The median figure, by level in the title:
| Level in the title | Postings | State years | Median |
|---|---|---|---|
| Entry or intern | 35 | 11% | 2 |
| Mid (no level in title) | 369 | 58% | 3 |
| Senior | 386 | 69% | 5 |
| Staff, principal and up | 347 | 71% | 8 |
Entry-level postings seldom state years, so there's no number to match there. For other levels, use the posting's own number in your summary when it's true of you. A degree is mentioned in 27% of postings, and 17.5% say "or equivalent experience."
Match the stack the posting names, and attach each term to something you did. The example below is a fictional teaching case, and it shows the trap of overclaiming.
A backend posting asks for Go, PostgreSQL, Docker and Kubernetes. The applicant has built a Go service backed by PostgreSQL and packaged it with Docker, but has never deployed Kubernetes.
| Posting asks for | Evidence available | Resume decision |
|---|---|---|
| Go | Implemented a billing API in Go | Name the language and the system in a bullet |
| PostgreSQL | Wrote queries and maintained billing tables | Describe the database work and its context |
| Docker | Packaged the API for local and staging environments | Say where the containers ran |
| Kubernetes | No hands-on experience | Don't add it as a skill |
Before: Worked on backend development and deployments.
After: Built a billing API in Go with PostgreSQL and packaged the service with Docker for local and staging environments.
The second version makes the existing evidence visible without adding a result or deployment experience the applicant can't support. A frontend applicant would do the same with interface, accessibility and browser-performance evidence. A senior platform applicant should show scope and ownership rather than collect tool names. For related roles, see the data analyst and cybersecurity analyst guides.
We counted terms in postings. We didn't observe what any recruiter or applicant tracking system searched for, so a high percentage is a reason to include a term, not proof it gets filtered on. Our term list has 49 entries, so a skill we didn't list wasn't counted. The sample leans toward tech companies using Greenhouse, Lever and Ashby, and was taken on a single day.
How many technologies should a software engineer resume list? Enough to cover the stack you really work in. The median posting names five of the 49 terms we tracked, so a list of 12 to 20 is plenty, and a 40-item wall mostly dilutes the terms that match.
Should I include technologies I've only used in side projects? Yes, if you can discuss them in technical depth, and label the context honestly with a Projects section. For career-changers and new grads, project work is legitimate evidence.
My title doesn't match what postings use. Can I translate it? Use the standard equivalent when your scope matches: "Member of Technical Staff" to "Software Engineer" is an honest translation. Inflating "QA Engineer" to "Software Engineer" is not.
Paste your resume and a target posting into the resume keyword scanner to see your exact gaps, or run the free ATS checker first if you haven't verified your format. When the gaps are clear, sign in free and MatchCV rewrites the bullets against that exact posting.
Start with this fictional role example or replace both inputs with your own text. A keyword match is wording coverage, not proof of qualifications.
Maximum 4 MB. Old .doc files must be saved as DOCX.
Use the actual posting. A job title alone does not describe its requirements.
No sign-up to analyze · Daily AI limits apply.
Text checks cannot verify a file’s visual layout or predict an interview.
Find the keywords your resume is missing for any job description
Scan my resume keywords →or sign in free to tailor your resume with AI