Every job listing is a signal. When a company publishes a role requiring Python, Kubernetes, and AWS, it is telling you exactly what its engineering organization runs on, what problems it is solving, and what kind of engineer it needs. Multiply that signal across 77,480 active software engineering listings, and you get something remarkably close to a real-time census of the technology industry's priorities.

We analyzed every listing in the findjobs.dev index to extract and count the technologies employers are actively hiring for. The results confirm some assumptions -- Python is dominant, cloud skills are non-negotiable -- but they also reveal surprises. Go has quietly overtaken TypeScript. CI/CD pipelines have become so universal that they rank third overall, ahead of every programming language except Python. And the AI/LLM category, which barely registered two years ago, now accounts for 3,382 listings and is accelerating.

What follows is a detailed breakdown of what the data actually says. Not predictions, not opinion polls, not recruiter anecdotes -- just what companies are asking for when they sit down to write a job description.

The Top 15: Technologies by Listing Count

The chart below ranks technologies by the number of active listings that mention them as a requirement or preferred skill. A single listing can mention multiple technologies, so these numbers reflect demand overlap -- a backend role might count toward Python, AWS, and Kubernetes simultaneously.

Python
19,670
AWS
16,813
CI/CD
13,686
Java
11,132
Kubernetes
10,970
React
10,736
Go
10,696
SQL
9,636
TypeScript
9,345
Azure
9,044
Docker
8,843
JavaScript
7,483
GCP
7,450
PostgreSQL
6,630
Terraform
5,896

The most striking feature of this chart is not what sits at the top -- Python's dominance has been clear for years -- but the density of infrastructure technologies in the top tier. Five of the top eleven entries (AWS, CI/CD, Kubernetes, Docker, Azure) are infrastructure and platform engineering tools. This is a market that has fundamentally shifted from "build the application" to "build the system that runs the application." The platform engineer, once a niche specialization, has become central to how modern software organizations operate.

The other pattern worth noting is the sheer scale of the top cluster. Python at 19,670 and AWS at 16,813 are in a league of their own, but then there is a dense band from Java (11,132) through Docker (8,843) where six technologies are separated by only about 2,300 listings. Competition for talent in this band is fierce precisely because so many companies need exactly the same combination of skills.

The Language Wars: Python, Java, Go, TypeScript, and JavaScript

Programming language debates generate more heat than light, but hiring data cuts through the noise. Here is what employers are actually putting in their job descriptions.

Python
19,670
25.4% of all listings
Java
11,132
14.4% of all listings
Go
10,696
13.8% of all listings
TypeScript
9,345
12.1% of all listings
JavaScript
7,483
9.7% of all listings

Python's lead is commanding and growing. One in four job listings mentions Python, making it the single most requested technology in software engineering. This is not just a data science story anymore. Python appears across backend services, infrastructure automation, machine learning pipelines, and increasingly in AI/LLM tooling. Its versatility as a glue language -- the thing you use to connect systems, write scripts, build prototypes, and train models -- has made it indispensable in a way that no other language currently matches.

Java holds steady as the enterprise backbone. At 11,132 listings, Java remains the second most requested language. Its strength is concentrated in fintech, insurance, and large enterprise companies where JVM-based systems handle mission-critical workloads. The listings skew heavily toward senior and staff roles, reflecting mature codebases that need experienced maintainers and architects rather than greenfield builders.

Go has overtaken TypeScript. This is perhaps the most significant shift in the data. Go's 10,696 listings edge out TypeScript's 9,345, a reversal from where these two stood even a year ago. Go's rise is driven by cloud-native infrastructure: Kubernetes itself is written in Go, and the explosion of platform engineering roles has dragged Go demand upward with it. Companies building internal developer platforms, service meshes, and observability tooling are overwhelmingly choosing Go for new systems work.

TypeScript and JavaScript together tell a nuanced story. Counted separately, TypeScript (9,345) and JavaScript (7,483) occupy different tiers. But they share an ecosystem, and many roles list both. Combined, the JavaScript/TypeScript family appears in roughly 16,828 listings -- second only to Python. The migration from JavaScript to TypeScript is clearly visible in the data: TypeScript now outpaces its predecessor by 25%, and the gap is widening. New frontend and full-stack roles almost universally specify TypeScript; plain JavaScript listings increasingly correspond to legacy maintenance work.

Key finding: If you combine JavaScript and TypeScript into a single "JS ecosystem" category, it accounts for roughly 21.7% of all listings -- nearly matching Python's 25.4%. The web platform remains an enormous source of engineering employment, even as backend and infrastructure roles dominate the headlines.

Cloud Platform Comparison: AWS vs Azure vs GCP

Cloud skills have become table stakes for software engineers. Across our entire index, at least one cloud platform appears in 43% of all listings. But the three major providers occupy very different positions in the hiring market.

Market share
AWS 50.5%
Azure 27.2%
GCP 22.4%
AWS — 16,813 Azure — 9,044 GCP — 7,450

AWS dominates with 16,813 listings, holding 50.5% of the cloud hiring market. This is not merely proportional to AWS's infrastructure market share -- it exceeds it. AWS has become the default assumption in job descriptions the way "Linux experience" once was. Many listings treat AWS fluency as a baseline requirement rather than a differentiating skill, which means the actual number of roles where AWS knowledge is useful is likely even higher than what explicit mentions capture.

Azure's 9,044 listings reflect its stronghold in enterprise and regulated industries. Azure demand is disproportionately concentrated in financial services, healthcare, and government-adjacent technology companies -- sectors where Microsoft's compliance certifications and Active Directory integration create genuine lock-in. If you are targeting enterprise software engineering roles, Azure expertise is often more valuable than AWS experience.

GCP at 7,450 listings occupies a smaller but distinct niche. GCP demand correlates heavily with data engineering and machine learning roles, driven by BigQuery, Vertex AI, and Google's Kubernetes Engine. Companies running sophisticated data pipelines or building AI products are disproportionately likely to be on GCP. The platform also shows up heavily in startup job listings, particularly in the Series B through pre-IPO range.

A growing number of listings -- roughly 12% of cloud-mentioning roles -- now specify multi-cloud experience, naming two or all three platforms. This trend toward multi-cloud fluency is strongest at staff-plus seniority levels, where architects are expected to make platform decisions rather than simply operate within one.

The Infrastructure Stack: Docker, Kubernetes, and Terraform

If there is a canonical "modern infrastructure" stack in 2026, it is Docker for packaging, Kubernetes for orchestration, and Terraform for provisioning. Together, these three technologies appear in a combined 25,709 listings.

10,970
Kubernetes listings
8,843
Docker listings
5,896
Terraform listings
4,854
Microservices listings

Kubernetes has surpassed Docker in listing volume, which tells an important story about where the industry's complexity -- and thus its hiring needs -- actually sits. Docker is a solved problem. Most engineers know how to write a Dockerfile. But operating Kubernetes at scale, debugging networking issues across service meshes, managing resource quotas, and implementing progressive delivery patterns requires deep specialization. The 10,970 Kubernetes listings represent the industry's growing appetite for engineers who can operate the platform layer, not just deploy to it.

Docker's 8,843 listings still represent massive demand, but the nature of that demand has shifted. Docker increasingly appears as a "required" checkbox skill -- something you must know but that alone does not differentiate you. The premium is now on orchestration and infrastructure-as-code skills that sit above the container layer.

Terraform at 5,896 listings has become the de facto standard for infrastructure as code. While alternatives like Pulumi and AWS CDK exist, Terraform's HCL-based approach dominates job requirements by a wide margin. Terraform listings correlate strongly with senior and staff roles, reflecting the seniority typically required to design and manage infrastructure provisioning across environments.

The microservices pattern itself, mentioned in 4,854 listings, has become an assumed architectural style rather than an aspirational one. Companies no longer describe microservices as a goal they are moving toward; they describe it as the architecture they already have and need engineers to maintain, extend, and sometimes consolidate.

Frontend Frameworks: React, Angular, and the Rest

The frontend framework landscape is less competitive than the language wars suggest. React has won, and the data makes this unambiguous.

React
10,736
13.9% of all listings
Angular
2,967
3.8% of all listings

React's 10,736 listings represent a 3.6x multiple over Angular's 2,967. This gap is even more dramatic than it appears, because React's count does not include the many full-stack and backend-leaning roles that mention React as a "nice to have" rather than a primary requirement. The framework has achieved a degree of market dominance that makes it less of a technology choice and more of an industry default.

Angular's 2,967 listings, while far behind React, represent a stable and well-defined segment. Angular demand is concentrated in enterprise environments -- large financial institutions, government contractors, and established SaaS companies with mature frontend codebases. These are often large-scale applications where Angular's opinionated structure and built-in tooling provide genuine advantages over React's flexibility. The Angular market is not growing, but it is not shrinking either. It has found its equilibrium.

Vue.js, while a beloved framework in developer surveys, does not appear in our top-26 technologies, falling below the 2,762 listing threshold of GitHub Actions. This highlights a persistent gap between developer preference and employer demand. Vue has strong adoption in certain markets -- particularly in Asia-Pacific and among smaller startups -- but it has not penetrated the enterprise hiring pipeline the way React and even Angular have.

Key finding: React is now so dominant in frontend hiring that listing it on your resume is less of a differentiator and more of a prerequisite. The engineers commanding the highest frontend salaries are those who pair React with performance optimization, accessibility expertise, or design system architecture -- skills that cannot be reduced to a framework name.

The AI and LLM Boom

No technology story in 2026 is complete without addressing the elephant in the room. LLM-specific roles have reached 3,382 listings in our index, and the trajectory is unmistakable.

3,382
Active LLM and AI engineering listings across 77,480 total jobs. That is 4.4% of all software engineering roles -- a category that effectively did not exist in job listings before 2023. The majority of these positions are at companies with fewer than 1,000 employees, concentrated in AI/ML, developer tools, and healthcare industries.

The LLM hiring surge is qualitatively different from previous technology hype cycles. When blockchain roles spiked in 2021-2022, they were concentrated in a narrow band of crypto-native companies. LLM roles, by contrast, are distributed across virtually every industry in our index. Fintech companies are hiring LLM engineers to build fraud detection and customer service systems. Healthcare companies want them for clinical documentation and diagnostic assistance. Developer tools companies are building AI-powered code generation, testing, and review products. Even defense contractors are posting LLM engineering roles.

The skill requirements in LLM listings reveal an interesting pattern. Python appears in over 90% of them, as expected. But the second most common requirement is not TensorFlow or PyTorch -- it is experience with prompt engineering, RAG architectures, and fine-tuning workflows. The market has moved past needing researchers who can train models from scratch. It now needs engineers who can integrate foundation models into production systems, manage context windows, build retrieval pipelines, and evaluate model outputs at scale.

Salaries in this category reflect the supply-demand imbalance. LLM engineering roles in the US show a median base salary roughly 15-20% above the overall senior engineer median. The premium is even higher at AI-native companies and well-funded startups competing directly for talent against OpenAI, Anthropic, Google DeepMind, and Meta's AI research division.

Database Technologies: PostgreSQL and SQL

Database skills remain foundational, but the data reveals a clear hierarchy in what employers specify.

SQL
9,636
12.4% of all listings
PostgreSQL
6,630
8.6% of all listings

SQL as a general skill appears in 9,636 listings, making it the eighth most demanded technology overall. This speaks to the enduring importance of relational data modeling and query fluency regardless of which specific database a company uses. SQL is one of those technologies that transcends trends -- it appeared in job listings thirty years ago and it will appear in them thirty years from now.

PostgreSQL at 6,630 listings has cemented its position as the default relational database for new projects. When companies specify a particular database system rather than generic "SQL," PostgreSQL leads by a wide margin. Its combination of reliability, feature richness (JSONB, full-text search, extensions), and the absence of licensing costs has made it the overwhelming choice for startups and growth-stage companies. PostgreSQL demand is particularly strong in roles that also mention Go, Python, or Kubernetes -- the modern backend stack almost universally assumes Postgres as the data layer.

The data also points to an interesting evolution in how database skills are valued. Listings at the senior and staff level increasingly ask for experience with database performance tuning, query optimization, and schema design rather than simply "SQL knowledge." The commoditization of basic database operations through ORMs and managed services means that differentiated value now comes from deep understanding of how databases work under the hood -- indexing strategies, query planners, replication topologies, and connection pooling.

Which Stacks Pay the Most?

Technology choice and compensation are correlated, though the relationship is not always what you might expect. Using the 38% of listings in our index that include salary data, we can identify which technology combinations command the highest base compensation.

Technology / Stack Median Salary (US) Listings with Salary
LLM / AI Engineering $210,000 1,284
Go + Kubernetes $195,000 2,847
Terraform + AWS $190,000 2,156
Kafka + Java $185,000 1,593
React + TypeScript $170,000 3,421
Python + AWS $168,000 4,087
Spark + Python $175,000 1,102
iOS / Android (Mobile) $165,000 2,814
Angular + Java $160,000 892

LLM and AI engineering roles command the highest median salaries at $210,000 for US-based positions. This premium reflects genuine scarcity: the number of engineers with production experience building LLM-powered systems is still small relative to demand. Companies are paying a premium not just for AI knowledge but for the ability to ship AI features that work reliably in production.

The Go + Kubernetes combination at $195,000 represents the infrastructure engineering premium. These roles typically involve building and maintaining the platform layer that other engineers deploy to. The salary reflects both the complexity of the work and the critical nature of the systems involved -- when Kubernetes goes down, everything goes down.

React + TypeScript at $170,000 is notable because it represents the upper end of frontend engineering compensation. The frontend roles that pay at this level are not simple UI implementation work. They involve complex state management, performance-critical rendering, design system architecture, and often a significant amount of tooling and build pipeline work.

Key finding: Infrastructure and platform engineering stacks (Go, Kubernetes, Terraform, Kafka) consistently command 10-15% salary premiums over application-layer stacks at the same seniority level. The market is pricing in the operational complexity and blast radius of infrastructure work.

Emerging Signals: What to Watch

Beyond the top-line numbers, several smaller signals in the data point to where the market is heading.

GitHub Actions at 2,762 listings

CI/CD is the third most demanded skill overall (13,686 listings), and GitHub Actions has become the dominant specific implementation. Its 2,762 listings represent the standardization of CI/CD around GitHub's ecosystem. For companies already on GitHub -- which is most of them -- Actions has replaced Jenkins, CircleCI, and Travis as the default choice. Engineers who can write sophisticated GitHub Actions workflows, including matrix builds, reusable workflows, and custom actions, are finding this to be a genuinely differentiating skill.

Kafka at 4,075 listings

Apache Kafka's presence in 4,075 listings reflects the continued shift toward event-driven architectures. Kafka demand is concentrated in fintech, e-commerce, and large-scale SaaS companies where real-time data streaming is a core requirement. The skill is strongly correlated with senior and staff-level roles, and Kafka-mentioning listings show median salaries roughly 8% above the overall senior median.

Mobile: iOS (4,132) and Android (4,272)

Mobile development demand remains substantial but stable. The combined 8,404 mobile listings represent a mature market segment that is neither growing nor shrinking dramatically. The interesting dynamic here is the convergence: cross-platform frameworks like React Native and Flutter are eating into native development, but the highest-paying mobile roles still specify native iOS (Swift) or native Android (Kotlin) expertise.

R at 3,908 listings

R's 3,908 listings are concentrated almost entirely in data science, biostatistics, and quantitative research roles. It occupies a niche that Python is steadily encroaching on but has not fully displaced. R demand is strongest in pharmaceutical companies, academic-adjacent research organizations, and hedge funds where statistical rigor and domain-specific packages still give R an edge.

Spark at 3,152 listings

Apache Spark remains the go-to framework for large-scale data processing. Its 3,152 listings are tightly correlated with data engineering roles and companies operating at significant data scale. As data volumes continue to grow exponentially, Spark expertise -- particularly in its PySpark and Spark SQL interfaces -- remains a high-value specialization.

Methodology

How we collected this data

The data in this analysis is drawn from the findjobs.dev live index of 77,480 active software engineering job listings, aggregated from 21 applicant tracking systems and company career pages across 214 countries. Technology mentions are extracted from job descriptions using structured field parsing and natural language processing. Each listing's technology requirements are normalized to a canonical set of technology names to avoid double-counting variants (e.g., "Golang" and "Go" are counted as the same technology, "JS" and "JavaScript" are unified).

A single listing can mention multiple technologies, so the counts in this report reflect the number of listings that mention each technology, not the number of unique roles. Salary data is included only when the original listing provides explicit compensation information. All salary figures represent annual base compensation in USD for US-based roles. The data reflects a snapshot of active listings as of February 2026.

Percentages are calculated against the total index of 77,480 listings. The "market share" visualization for cloud platforms is calculated against the combined cloud platform listing count (33,307), not the total index.