What 1,360 Software Engineer Job Postings Actually Ask For

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

72 companies · collected 2026-08-29 · method and raw data below

We pulled every open posting from 72 companies' public Greenhouse job boards, kept the 1,360 whose title contains “software engineer,” and counted how many of them mention each of 45 technical terms at least once.

The number beside each term is the share of postings that mention it — not how often it appears. A posting that says “Python” nine times counts once, the same as one that says it in passing.

The 20 most common terms

Percentage of the 1,360 postings that mention each term.

01scalability

52.9% (719)

02mentoring

47.4% (644)

03distributed systems

47% (639)

04system design / architecture

46.7% (635)

05Python

44.8% (609)

06AWS

41.3% (562)

07Java

35.4% (482)

08Go

31.1% (423)

09cross-functional

31% (422)

10Kubernetes

30.9% (420)

11code review

27.2% (370)

12React

21.1% (287)

13on-call

20.7% (281)

14TypeScript

19.8% (269)

15CI/CD

19.5% (265)

16GCP / Google Cloud

19.3% (262)

17Azure

17.6% (239)

18C++

17.4% (236)

19SQL

17.3% (235)

20PostgreSQL

14.3% (194)

What stands out

The top four are not technologies. Scalability, distributed systems, mentoring and system design 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.

No language is close to universal. Python tops the list at 44.8%, meaning 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.

Mentoring appears in 47.4% of postings — more than Kubernetes, React or TypeScript. It is one of the most commonly asked-for and least commonly written-about things on this list.

Every term, 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

Source. The Greenhouse job board API, which companies expose so their listings can be embedded on their own sites. No scraping and no private data. Any figure here can be re-derived from that endpoint; the collector and analyzer are in the repository.

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.

Deduplication. The same role posted to five offices returns five near-identical records. Postings were deduped on company, normalized title and content length, which removed 69 of an initial 1,233.

Counting. Document frequency — the share of postings mentioning a term at least once. Ambiguous English words are matched case-sensitively with exclusions, because a bare match on “Go” also catches “go to market” and overstates it by about two points. The same applies to React, Spark, Swift and Rust.

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

See which of these your resume is missing

Paste your resume and a specific job posting — the checker names the terms that posting uses and yours does not.

Check My Resume →

Or read the software engineer keyword guide · the same study for accountants · for cybersecurity · for marketing

What 1,360 Software Engineer Job Postings Actually Ask For