One of seven role studies in the ATS Resume Keyword Study counts 3,518 job postings from 81 companies, term by term. Terms counted in more than one role are compared in the same-term comparison across roles.

Keyword study

What 1,360 Software Engineer Job Postings Actually Ask For

Most resume advice about keywords is guesswork. This is a count.

The dataset

Postings
1,360, after removing duplicates
Companies
72
Collected
2026-08-29, a one-day snapshot of open roles
Source
Public company job boards, via the Greenhouse job board API. Nothing scraped, nothing private; every figure can be re-derived from the same endpoint
Coverage
Weighted toward US technology companies; one ATS vendor
Role definition
Title contains “software engineer”; engineering managers excluded
Deduplication
Company, normalized title and content length
Terms measured
45
Unit
Share of postings naming a term at least once
Margin of error
Not recorded per term for this collection; at most ±2.7 points at this sample size
Analysis
ResumeFitting, method v1.0

Download this study as CSV · Full method and limits

Before you apply

Your stack against one posting's

The aggregate says no stack is universal. The posting you are applying to has one. Paste both and see which of its terms your resume never uses.

Check My Resume

The top of the list is not a technology

scalability, mentoring, distributed systems, system design / architecture each appear in more postings than any single programming language. A resume built entirely from a tools list is missing the vocabulary that most postings lead with.

Mentoring appears in 47.4% of postings: more than Kubernetes (30.9%), React (21.1%) or TypeScript (19.8%). It is one of the most commonly asked-for and least commonly written-about things on this list. If you have onboarded, reviewed for, or taught another engineer, it belongs in a bullet.

Which language to list first

All 13 languages we counted, their rank among the 45 terms, and whether the gap to the next language is larger than the sampling noise.

LanguageOverall rankPostingsShareNext one down
Python560944.8%clearly behind
Java748235.4%clearly behind
Go842331.1%clearly behind
TypeScript1426919.8%within noise
C++1823617.4%within noise
SQL1923517.3%clearly behind
JavaScript2117913.2%within noise
Kotlin2516312%within noise
Rust271359.9%within noise
Scala311178.6%within noise
Ruby321158.5%clearly behind
C#41725.3%clearly behind
Swift45312.3%n/a

No language is close to universal. Python leads at 44.8%, so more than half of these postings never name it. Writing a resume to match “the” software engineering stack is writing to a stack that does not exist.

The top 3 separate cleanly. Python, Java and Go each sit clearly ahead of the next language down. Below that, neighbors are often within the noise, so the order of the middle of this table should not decide what you learn next. List the languages you have shipped in, strongest first.

On the frontend, one framework. React 21.1%, Vue 3.2%, Angular 2.9%. React is named about 7 times as often as Angular.

The 20 terms named most

Share of the 1,360 postings that mention each term, with the posting count in brackets. A posting that says “Python” nine times counts once.

scalability

52.9% (719)

mentoring

47.4% (644)

distributed systems

47% (639)

system design / architecture

46.7% (635)

Python

44.8% (609)

AWS

41.3% (562)

Java

35.4% (482)

Go

31.1% (423)

cross-functional

31% (422)

Kubernetes

30.9% (420)

code review

27.2% (370)

React

21.1% (287)

on-call

20.7% (281)

TypeScript

19.8% (269)

CI/CD

19.5% (265)

GCP / Google Cloud

19.3% (262)

Azure

17.6% (239)

C++

17.4% (236)

SQL

17.3% (235)

PostgreSQL

14.3% (194)

All 45 terms, by category

Languages

TermPostingsShare
Python60944.8%
Java48235.4%
Go42331.1%
TypeScript26919.8%
C++23617.4%
SQL23517.3%
JavaScript17913.2%
Kotlin16312%
Rust1359.9%
Scala1178.6%
Ruby1158.5%
C#725.3%
Swift312.3%

Cloud & infra

TermPostingsShare
AWS56241.3%
Kubernetes42030.9%
GCP / Google Cloud26219.3%
Azure23917.6%
Terraform17913.2%
Docker17112.6%
microservices977.1%
Linux654.8%

Data

TermPostingsShare
PostgreSQL19414.3%
Kafka17813.1%
MySQL15311.3%
Spark1339.8%
MongoDB1017.4%
Redis1017.4%
Elasticsearch876.4%
Snowflake765.6%

Frontend

TermPostingsShare
React28721.1%
REST / RESTful1309.6%
GraphQL826%
Node.js755.5%
Vue443.2%
Angular402.9%

Practice

TermPostingsShare
scalability71952.9%
mentoring64447.4%
distributed systems63947%
system design / architecture63546.7%
cross-functional42231%
code review37027.2%
on-call28120.7%
CI/CD26519.5%
Agile / Scrum1279.3%
unit / automated testing896.5%

Method

Selection. Postings were matched on the title alone, requiring the phrase “software engineer.” Titles like “Senior Software Engineer, Payments” are in; “Engineering Manager” is out.

Language names that are also English words. A bare match on “Go” also catches “go to market” and overstates it by about two points, so it is matched case-sensitively with exclusions. The same applies to React, Spark, Swift and Rust.

No interval column. This was the first study and its rows were recorded without per-term intervals. At 1,360 postings the widest possible is ±2.7 points; the “next one down” column above applies the proper test to each pair.

Limits worth stating. These are 72 mostly US technology companies hiring through one ATS vendor. They are not a random sample of all software engineering jobs, and the mix skews toward well-funded product companies. Terms absent from our 45-term list are not counted, so absence here is not evidence of absence in the market.

Companies included

adyen · affirm · airtable · anaplan · anthropic · asana · billtrust · blend · braze · brex · carta · checkr · chime · cloudflare · coinbase · coursera · databricks · datadog · discord · doximity · dropbox · duolingo · elastic · figma · fivetran · flexport · gemini · gitlab · gusto · gympass · hellofresh · impact · instabase · instacart · intercom · justworks · klaviyo · lattice · launchdarkly · lyft · mixpanel · mongodb · monzo · newrelic · nuro · okta · oscar · peloton · pendo · pinterest · postman · pushpay · reddit · ridgeline · ripple · robinhood · sagesure · samsara · setpoint · smartsheet · sofi · squarespace · stripe · taskrabbit · tide · tripadvisor · twilio · vercel · verkada · webflow · zocdoc · zscaler

Using these findings on a resume

Illustrative pairs, not taken from the postings: the same work, written without and then with the terms postings name.

Before

Built web applications and worked with APIs

After

Architected React + FastAPI platform serving 400k MAU; introduced GraphQL federation layer reducing mobile API payload 60% and cutting Time to Interactive from 4.1s to 1.8s

Before

Worked on backend systems and improved performance

After

Redesigned PostgreSQL query pipeline with covering indexes and materialized views; eliminated N+1 queries and cut P95 latency from 820ms to 95ms for 2M daily active sessions

Before

Set up cloud infrastructure and deployment processes

After

Migrated monolith to 8 Docker microservices on AWS (ECS + RDS + ElastiCache); GitHub Actions CI/CD pipeline ships to production 12× daily with automated rollback on error rate >0.5%

The other role studies

All seven studies use the same collection and counting method, so their figures can be read side by side.

What a figure here means

A percentage is the share of the 1,360 postings in this sample that name the term at least once. It is not the share of all employers that ask for it, a cutoff an applicant tracking system applies, or a measure of your chances of an interview.

The 95% interval shows sampling error only. It does not correct for which companies publish on the job boards it draws from or for the one-day snapshot. A larger sample for one role says nothing about which role is more in demand or more important.

Version history

  • 2026-08-29: published, from postings collected 2026-08-29.

The table as it stands: 1,360 postings from 72 companies, 45 terms, method v1.0.

No figure on this page has been corrected. Every withdrawn row and corrected figure across the studies is listed in the corrections log. The analysis script that built this table and the collector it reads from are published as plain text.

How to cite this study

Quote any figure on this page. If you do, link back to it so readers can see the sample and its limits rather than the number alone.

General citation

ResumeFitting, “What 1,360 Software Engineer Job Postings Actually Ask For” (method v1.0, data collected 2026-08-29). https://resumefitting.com/software-engineer-job-description-keywords

APA style

ResumeFitting. (2026-08-29). What 1,360 Software Engineer Job Postings Actually Ask For. https://resumefitting.com/software-engineer-job-description-keywords

MLA style

ResumeFitting. “What 1,360 Software Engineer Job Postings Actually Ask For.” ResumeFitting, 2026-08-29, resumefitting.com/software-engineer-job-description-keywords.

Chicago style

ResumeFitting. “What 1,360 Software Engineer Job Postings Actually Ask For.” ResumeFitting, 2026-08-29. https://resumefitting.com/software-engineer-job-description-keywords.

Before you apply

Check your resume against a software engineer posting

The aggregate says no stack is universal. The posting you are applying to has one. Paste both and see which of its terms your resume never uses.

Check My Resume

Or read the same infrastructure terms, counted in DevOps and SRE postings · Python and Go, counted in security postings

The rest of the research

This role is one corpus of seven

The study hub holds the method, every role's figures, the limits of each sample, and the full dataset as a CSV.

Back to the full 3,518-posting study →

Software Engineer Keywords: Scalability Beats Every Language