Compensation in software engineering has always been a moving target. After two years of post-pandemic corrections, layoff cycles, and a fundamental reshaping of what companies value in technical talent, the 2026 salary landscape looks meaningfully different from what engineers experienced during the boom years of 2021 and 2022. The frothy offers that defined that era are largely gone. What has replaced them is a market that rewards specialization, seniority, and increasingly, the ability to work with artificial intelligence systems at a production level.
To understand where compensation stands today, we analyzed the 29,442 job listings in the findjobs.dev index that include explicit salary data. That represents 38% of the 77,480 active software engineering positions we track across 214 countries. Rather than relying on self-reported figures from anonymous surveys, this data comes directly from what companies are willing to put in writing on their job postings. It is, by definition, what employers are actually offering, not what candidates hope to earn.
The picture that emerges is nuanced. Senior engineers remain the most sought-after cohort, commanding a median of $180,000, while the junior market has contracted into a narrow, competitive band. Meanwhile, infrastructure and AI specializations continue to pull away from the pack, with premiums that would have seemed excessive just three years ago becoming the new normal.
Compensation by Seniority Level
Annual base salary ranges across 29,442 listings. Bars show the 25th to 75th percentile range; markers indicate the median.
The most striking feature of this data is the sheer dominance of the senior band. With 27,179 listings, senior engineer roles account for roughly 59% of all positions in the index. This is not a statistical artifact. It reflects a genuine structural shift in how companies build engineering organizations. The mid-level tier, which used to be the largest hiring band a decade ago, has been compressed from both sides: companies increasingly want either cheap junior labor for well-defined tasks or experienced seniors who can own entire systems without hand-holding.
The junior squeeze is real. With just 1,313 listings carrying explicit salary data, entry-level positions represent the smallest segment we track. The median of $85,000 is competitive by historical standards, but the narrow range ($65K to $125K) tells an important story. Companies posting junior roles at the high end of that range are typically in San Francisco or New York, where cost of living adjustments push even entry-level compensation upward. In most markets, new graduates are looking at offers in the $70K to $90K range for their first full-time role.
At the top of the ladder, principal engineers see a median of $270,000 with a ceiling that stretches above $366,000. These figures represent base salary only. When equity and bonuses are factored in, total compensation for principal-level engineers at public technology companies regularly exceeds $500,000. The 2,530 principal listings in our index are disproportionately concentrated at companies with 500 or more employees, where the IC track is well-established and distinguished from the management path.
The senior engineer band alone contains nearly as many listings as all other seniority levels combined. Companies are not hiring pyramids anymore. They are hiring diamonds.
Engineering managers land at $195,000 median, which places them above senior ICs but below staff engineers. This reflects the reality that management and staff engineering have become parallel tracks in most modern organizations. A staff engineer at $230K is not underpaid relative to their manager counterpart at $195K; rather, the two tracks have converged around similar economic value, with the premium going to depth of technical expertise over people management scope. The 4,762 manager listings in our dataset show a wider range ($155K to $260K) than any other band, suggesting that "engineering manager" encompasses a broad spectrum of responsibilities, from first-line team leads to directors of large organizations.
Tech Stack Salary Premiums
How specific technology requirements shift compensation relative to the overall median.
The 18% premium for AI and ML roles is the headline number, but the story beneath it is more specific than it first appears. Not all AI work pays equally. The premium is concentrated in roles that require production-level experience with large language models, including fine-tuning, inference optimization, retrieval-augmented generation, and evaluations infrastructure. Research-oriented ML scientist positions, while still well-compensated, carry a smaller premium because the supply of PhD-trained candidates has grown substantially. The real scarcity, and therefore the real money, is in engineers who can take a model from a notebook to a production API that handles thousands of requests per second with predictable latency.
The Kubernetes and infrastructure premium (+12%) is one of the most durable wage signals in the industry. It has held steady for over three years now, which is unusual. Most tech-specific premiums tend to compress as adoption grows and the talent pool expands. Infrastructure is different because the work itself becomes more complex over time, not less. As companies adopt multi-cloud strategies, service meshes, and zero-trust networking, the demand for engineers who can reason about distributed systems at the platform level continues to outpace supply.
Python's position at exactly the median is telling. It is the most requested technology in our entire index, appearing in 19,670 listings. But prevalence does not equal premium. When a skill appears in one out of every four job postings, it stops being a differentiator and becomes a baseline expectation. Python fluency is to 2026 what "proficiency in Microsoft Office" was to 2006: assumed, not compensated. The engineers commanding the highest Python salaries are those who combine it with specialized domains like ML infrastructure, quantitative finance, or data platform engineering.
React's -5% position below median may surprise some, given that frontend development is not trivial work. The discount reflects supply dynamics more than the intrinsic value of the work. The frontend talent pool expanded dramatically during the bootcamp boom of 2018 to 2022, and React became the default framework taught in nearly every program. The result is a buyer's market for React skills at the junior and mid levels. Senior frontend engineers who specialize in performance optimization, design systems, or complex state management still command strong offers, but the baseline React-focused role pays less than a comparable backend or infrastructure position.
What about Rust, Go, and other emerging languages?
Go roles pay roughly 8% above median, benefiting from strong demand in cloud infrastructure and backend services. Rust carries a similar premium but in a much smaller market (fewer than 1,200 listings). TypeScript has converged with the overall median as it has become the default choice for full-stack development. The niche languages like Elixir and Haskell show high per-listing compensation but too few data points to draw reliable conclusions.
Remote vs. Onsite Compensation
How work location policy affects salary offers across seniority levels.
| Work Model | Senior Avg. | Staff Avg. | vs. Onsite |
|---|---|---|---|
| RemoteFully distributed, no office requirement | $191,000 | $245,000 | +6% / +7% |
| OnsiteFull-time office presence required | $180,000 | $230,000 | baseline |
| HybridTypically 2-3 days per week in-office | $183,000 | $235,000 | +2% / +2% |
One of the persistent myths in the return-to-office debate is that remote workers accept a salary discount in exchange for flexibility. Our data shows the opposite. Remote senior engineers average $191,000, roughly 6% above their onsite counterparts at $180,000. At the staff level, the gap widens slightly: $245,000 remote versus $230,000 onsite, a 7% premium.
This inversion has a straightforward explanation: companies offering remote positions are competing in a national (or global) talent market rather than a local one. A remote-first startup in Austin is not just competing with other Austin employers. It is competing with companies in San Francisco, New York, and Seattle, all of which anchor their compensation to higher cost-of-living baselines. To attract strong candidates from these markets, remote employers have to offer competitive pay regardless of where the employee actually sits.
There is a second, subtler force at work. Companies that have committed to remote work tend to be more intentional about their compensation philosophy. They are disproportionately represented among well-funded startups and growth-stage companies that use transparent pay bands. These organizations often benchmark against the 75th percentile of market data because they view competitive compensation as a prerequisite for hiring without the benefit of a physical office and in-person culture as selling points.
Hybrid roles, at $183,000 for seniors and $235,000 for staff, sit closer to the onsite baseline. This makes sense intuitively: hybrid positions still require geographic proximity to an office, which limits the talent pool and reduces the competitive pressure that pushes remote salaries upward. The 2% premium likely reflects the slightly broader geographic radius that "2-3 days per week" enables compared to a fully onsite requirement.
Remote roles do not pay less. They pay more. The competitive dynamics of a location-independent talent market push remote compensation above onsite baselines at every seniority level.
Geographic Salary Differences
Median senior engineer compensation by city. All figures converted to USD at time of indexing.
San Francisco retains its position as the highest-paying city for software engineers, with a senior median of $195,000. But the gap between San Francisco and its closest competitors has narrowed substantially. Seattle, at $190,000, is now within striking distance, driven by Amazon and Microsoft's massive engineering organizations and the cloud infrastructure ecosystem that surrounds them. The $5,000 gap between these two cities is within the margin of error for median calculations on datasets of this size.
New York's $185,000 median reflects a different market composition. While the Bay Area is dominated by pure technology companies and venture-backed startups, New York's engineering demand is more evenly distributed across fintech, media, advertising technology, and enterprise software. The financial services sector, in particular, pays generously for engineers who understand both systems design and the domain-specific requirements of trading, risk, and payments infrastructure. However, New York is notably more onsite-oriented than its West Coast counterparts, with a higher percentage of roles requiring full in-office presence.
Austin's $165,000 median places it as the clear value play among major US tech hubs. With no state income tax in Texas, the effective take-home pay for an engineer earning $165,000 in Austin is comparable to someone earning roughly $185,000 to $190,000 in California, depending on total compensation structure. This arithmetic, combined with a lower cost of living, explains the steady migration of both companies and engineers to the Austin metro area over the past several years.
The transatlantic salary gap remains stark. London's median of approximately $95,000 (roughly 75,000 GBP) is less than half the San Francisco figure. This is not new, but it continues to be one of the most significant structural features of the global engineering labor market. European salaries reflect a different compensation model that includes stronger benefits mandates, longer vacation allowances, and social safety nets that reduce the need for individually negotiated compensation. For individual engineers, however, the dollar-denominated gap is real and has been a persistent driver of remote-work arbitrage, where London-based engineers seek US-paying remote positions.
Cost-of-living adjustment note
These figures represent nominal compensation and do not adjust for local cost of living or tax burden. An engineer earning $165,000 in Austin likely has more purchasing power than one earning $195,000 in San Francisco after accounting for housing costs, state taxes, and general price levels. We report nominal figures because they reflect what companies are actually paying and what candidates will see on offer letters.
Compensation by Industry
Median senior engineer salary across the major industry verticals in our index.
The AI and machine learning industry leads all verticals with a senior median of $212,000, a full $32,000 above the overall senior median. This premium reflects the extreme concentration of venture capital in AI companies over the past two years. Firms building foundation models, inference infrastructure, and AI-native applications are competing for a relatively small pool of engineers with production ML experience, and they are willing to pay accordingly. This figure, remember, represents base salary only. When equity grants at well-funded AI startups are included, total compensation at the senior level can exceed $400,000.
Fintech's $195,000 median makes it the highest-paying traditional industry. The financial services sector has long understood that technology is a competitive advantage, and the salary data reflects that conviction. Fintech companies, from established payment processors to growth-stage lending platforms, offer compensation that approaches (and sometimes exceeds) what pure technology companies pay. The premium is particularly pronounced for engineers with domain expertise in payments, compliance, or real-time transaction processing.
Crypto and Web3 at $190,000 may raise eyebrows given the sector's turbulent recent history. However, the companies that survived the 2022-2023 downturn tend to be well-capitalized infrastructure players (exchanges, custody solutions, layer-2 protocols) rather than speculative token projects. These surviving firms compete directly with fintech and traditional tech companies for backend and infrastructure talent, which keeps their compensation competitive.
At the other end of the spectrum, defense ($162,000) and insurance ($165,000) offer lower base salaries but compensate in other ways. Defense companies typically provide stability, generous benefits, and access to technically interesting problems that are unavailable in the commercial sector. Insurance, despite being one of the largest hiring verticals in our index (8,432 listings), pays below the tech-sector median because much of the work involves modernizing legacy systems rather than building greenfield products. The engineers working on next-generation underwriting models and real-time pricing engines within insurance companies command salaries closer to the fintech range, but the median is pulled down by the large volume of conventional enterprise development roles.
What This Means for Engineers
Practical implications of the data for career and compensation decisions.
If there is a single actionable takeaway from this analysis, it is that specialization pays. The gap between a generalist senior engineer at the median ($180K) and a senior engineer with AI/ML production experience ($212K+) is not a marginal difference. It is a 18% premium that compounds over a career. For an engineer in their early thirties evaluating where to invest their learning time, the salary data makes a compelling case for depth over breadth.
That said, chasing the highest-premium technology of the moment is a strategy with diminishing returns. Kubernetes has carried a 10-12% premium for three consecutive years now. AI/ML premiums have been climbing for two years. By the time a technology becomes clearly legible in salary data, the window for early-mover advantage is closing. The engineers who command the highest premiums today are the ones who made bets on these technologies before the market consensus formed, not after.
For engineers considering a transition to management, the data offers a clear message: do it for the right reasons, because the money alone does not justify it. Engineering managers at $195K earn less than staff engineers at $230K, and the gap only widens at the principal level. The IC track pays more at every rung above mid-level. Management offers different rewards, including organizational impact, people development, and strategic influence, but purely financial optimization points toward the staff-plus IC path.
Finally, the remote premium is worth considering for anyone anchored to a lower-cost market. A senior engineer in a mid-tier US city earning $165,000 at a local employer could potentially capture a $25,000 to $30,000 raise simply by transitioning to a remote role at a company that benchmarks against the national market. The 6% remote premium on senior salaries is a broad average. For engineers outside the major coastal hubs, the effective premium of accessing the remote labor market can be significantly higher.
Methodology
This analysis is based on the findjobs.dev index of active software engineering job listings. We analyze positions aggregated from 21 applicant tracking systems and company career pages across 214 countries. Each listing is processed to extract structured salary data when explicitly provided by the employer.
Salary figures reflect base compensation only. We report salaries only when the original listing includes explicit compensation data. We do not estimate, impute, or infer salaries from comparable roles. All figures represent annual base compensation in USD. Listings denominated in other currencies are converted at the exchange rate at the time of indexing. Equity, bonuses, signing bonuses, and benefits are excluded.
Medians and ranges represent the 50th percentile and approximately the 25th to 75th percentile of reported salary midpoints. Where a listing provides a range (e.g., $150K to $200K), we use the midpoint ($175K) for aggregation. Seniority classifications are determined by our fingerprinting system, which analyzes job titles, required experience, and description language to assign standardized levels.