Developer Salary Guide by Stack 2026
Developer Salary Guide by Stack 2026
Which technology you specialize in has a real and measurable impact on your earning potential. The gap between the highest-paying and lowest-paying technology stacks at the same experience level can exceed $40,000 annually in major US markets. And the stacks that were commanding premiums five years ago aren't necessarily the ones commanding premiums today.
This guide provides concrete salary data by technology, role, and experience level for 2026—with analysis of what's moving and why.
TL;DR
AI/ML engineering leads compensation in 2026, with experienced AI engineers earning $135,000–$240,000 depending on company tier. Cloud and platform engineering (particularly Kubernetes/Terraform specialists) runs $120,000–$180,000. Full-stack development (React + Node, or React + Python) averages $118,781 nationally. Go and Rust developers earn premiums in the systems programming and infrastructure markets. The biggest upward movers: AI engineers (+15–22% YoY), cloud security engineers (+12–18%), and platform engineers (+10–15%). The biggest downward pressure: traditional Java enterprise, legacy PHP, and junior front-end roles facing increased competition from AI-assisted offshore hiring.
Key Takeaways
- Full-stack developer (React + Node.js or Python): $118,781 national median in 2026.
- AI engineer / ML engineer: $135,000–$240,000 depending on experience and company tier; fastest-growing compensation segment.
- React developer: $107,000–$145,000 median; +6.85% YoY growth in listed salaries.
- DevOps/Platform engineer: $120,000–$175,000 depending on Kubernetes and cloud depth.
- Go developer: $135,000–$165,000 for infrastructure and backend roles.
- Rust developer: $130,000–$170,000; premium due to skill scarcity and workload characteristics.
- Python developer (non-ML): $105,000–$145,000; highest variance by specialization (data engineer vs web vs automation).
- Java enterprise developer: $110,000–$145,000; slower growth trajectory.
- Experience multiplier: Senior engineers earn 2–2.5x entry-level; staff/principal engineers earn 3–4x entry-level in total compensation at top companies.
Methodology Note
Salary data in this guide synthesizes information from Levels.fyi (verified compensation data, primarily Tier 1 companies), Stack Overflow Developer Survey 2025, GitHub Octoverse 2025, Glassdoor salary data, LinkedIn Salary Insights, Dice Tech Salary Report 2025, and BLS Occupational Employment Statistics. All figures are US-based unless otherwise noted. "National median" figures represent a blend across geographies; expect +30–50% in San Francisco/Seattle, +15–25% in NYC/Boston, and -20–35% in lower cost-of-living markets.
By Technology Stack
Frontend: React
React remains the dominant frontend framework by adoption in 2026, with approximately 39% of all web applications using it according to npm download data. The React developer market is large, well-established, and increasingly saturated at the junior level—but still commands significant premiums at senior levels.
Entry level (0–2 years): $65,000–$90,000 Mid level (3–5 years): $95,000–$130,000 Senior (6–9 years): $130,000–$165,000 Staff/Principal: $165,000–$220,000+ (total compensation at top companies significantly higher) National median (all levels): ~$107,000–$115,000
YoY salary growth: +6.85% for active React job listings in 2025–2026.
React developer compensation depends heavily on depth: a frontend specialist who knows only React earns less than a full-stack developer who uses React on the frontend and Node.js, Python, or Go on the backend. The highest-earning React developers are those who combine frontend expertise with API design, database architecture, and deployment skills.
React specializations that command premiums: React Native mobile development (+$10,000–$20,000 for mobile experience), Next.js SSR/performance optimization, and design system development.
Frontend: Vue, Angular, Svelte
Vue.js developer: $85,000–$130,000. Strong in European markets and companies that built on Vue before React dominated. Growth is slower than React in the US market.
Angular developer: $95,000–$135,000. Still heavily used in enterprise (particularly financial services and healthcare applications). Slower growth trajectory but large existing market.
Svelte / SvelteKit developer: $90,000–$135,000. Svelte continues gaining adoption, particularly for performance-sensitive applications. Smaller talent pool = slight premium, but job market is also smaller.
Backend: Python
Python's salary distribution has the highest variance of any language because Python is used across wildly different domains—web development, data engineering, scientific computing, automation, and ML/AI—each with different compensation norms.
Python web developer (Django/FastAPI): $95,000–$140,000 Python data engineer: $115,000–$160,000 Python data scientist: $105,000–$155,000 Python ML engineer: $130,000–$200,000+
The key insight: Python alone isn't a compensation driver. What you build with Python determines where you land. A Python developer doing web backend work earns notably less than a Python developer doing data pipeline work or ML system development, at the same experience level.
Backend: Go
Go has established itself as the language of cloud-native infrastructure, distributed systems, and high-throughput backends. Its adoption by Kubernetes, Docker, and the broader CNCF ecosystem has made it a near-requirement for infrastructure engineers.
Entry level: $90,000–$115,000 Mid level: $120,000–$155,000 Senior: $150,000–$185,000 National median (all levels): ~$135,000–$150,000
Go commands a premium because: (1) the talent pool is smaller than Python or JavaScript, (2) Go is primarily used in infrastructure and systems work that commands higher compensation, and (3) Go developers are concentrated in companies that value engineering craft (startups, cloud-native companies, developer tools companies).
Backend: Rust
Rust continues growing in systems programming, WebAssembly, blockchain infrastructure, and high-performance computing. The learning curve remains steep, which keeps the talent pool constrained and premiums high.
Entry level: $85,000–$115,000 (harder to find entry-level Rust roles) Mid level: $120,000–$160,000 Senior: $150,000–$185,000 National median (applicable roles): ~$140,000–$160,000
Rust's highest-paying applications: crypto/blockchain protocol engineering, operating systems work, game engine development, and WebAssembly-based edge computing. The premium is real but the market is narrower than Go.
Backend: Java / Kotlin
Java remains dominant in enterprise software, financial services, and Android development. The compensation is solid but has been growing more slowly than cloud-native stacks.
Java enterprise developer: $100,000–$145,000 Kotlin (Android / backend): $110,000–$150,000 Java microservices (Spring Boot / Quarkus): $110,000–$150,000
Java developers who can also work with Kubernetes, cloud-native architectures, and event streaming (Kafka) earn toward the top of these ranges. Purely Java/Spring developers at enterprise companies earn toward the bottom.
Full-Stack Development
Full-stack roles (combining frontend, backend, and some infrastructure) are the most common developer category by job listing volume and represent a practical sweet spot for compensation and opportunity.
React + Node.js (JavaScript full-stack): $95,000–$145,000 React + Python (Django/FastAPI backend): $100,000–$150,000 React + Go: $120,000–$165,000 National full-stack median: $118,781
Full-stack developers at startups often handle broader responsibilities (infrastructure, database administration, deployment) which inflates compensation relative to specialists in comparable experience bands. The trade-off is breadth over depth—senior full-stack developers at startups can earn well, but the highest individual contributor compensation comes from deep specialization at top companies.
By Specialization
DevOps and Platform Engineering
DevOps compensation has been rising steadily as Kubernetes expertise became genuinely scarce despite widespread adoption. Platform engineering—building internal developer platforms (IDPs) to abstract infrastructure for product engineers—is the fastest-growing DevOps specialization.
DevOps engineer (CI/CD, IaC, cloud): $105,000–$150,000 Site Reliability Engineer (SRE): $120,000–$175,000 Platform engineer: $125,000–$175,000 Kubernetes specialist (CKA level): $130,000–$180,000
Certifications matter here more than most specializations. AWS SA Professional or Google Cloud Architect, combined with CKA, can move compensation toward the top of these ranges. See our tech certifications ROI guide for the certifications that generate the clearest salary impact.
AI/ML Engineering
AI engineering has bifurcated into distinct roles with different compensation profiles:
ML engineer (traditional, model training, feature engineering, productionizing ML models):
- Entry: $110,000–$135,000
- Mid: $140,000–$175,000
- Senior: $170,000–$220,000
AI engineer / LLM engineer (application layer, LLM integration, RAG systems, fine-tuning):
- Entry: $105,000–$130,000 (role is new, entry paths are forming)
- Mid: $135,000–$175,000
- Senior: $165,000–$215,000+
Research scientist (AI) (PhD-track, fundamental research):
- Tier 1 companies: $180,000–$350,000+ total compensation
- Effectively requires advanced degree
The AI engineering job market is adding roles faster than the talent supply is growing. For engineers with solid software fundamentals who can add LLM integration expertise, this represents a significant compensation upgrade opportunity.
Security Engineering
Application security engineer: $115,000–$165,000 Cloud security engineer: $120,000–$175,000 Security engineer (CISSP-certified, senior): $140,000–$195,000 CISO: $180,000–$350,000+ (role depends heavily on company size and stage)
Security was already constrained in talent supply; the complexity of cloud-native and AI systems is expanding the attack surface faster than security engineers can grow. This is a high-compensation specialization with strong long-term tailwinds.
Geographic Premium/Discount
All figures above are national medians. Apply these adjustments for your market:
| Market | Adjustment |
|---|---|
| San Francisco Bay Area | +40–60% |
| Seattle | +30–45% |
| New York City | +25–35% |
| Boston, Austin, Denver | +10–20% |
| Chicago, Atlanta, Miami | +0–10% |
| Remote (US-based) | +0–25% (varies by company) |
| Midwest / Southeast mid-markets | -10–25% |
Remote work has partially but not fully equalized geographic salary differences. Many companies have moved to pay bands based on the employee's location rather than the company's location. Some companies (GitLab, Automattic) pay location-adjusted rates; others (Stripe historically, some tech companies) pay a single rate regardless of location.
What's Moving Compensation Up vs Down
Compensation Tailwinds (2026)
AI fluency: The ability to integrate LLMs, work with vector databases, and build AI-assisted features is commanding compensation premiums across almost all engineering roles.
Cloud-native depth: Kubernetes, service mesh, observability, and infrastructure-as-code expertise remains scarce relative to demand.
Security engineering: Growing regulatory complexity (EU Cyber Resilience Act, NIS2, DORA) is increasing demand for security-competent engineers.
Edge computing and WebAssembly: Emerging premium for engineers who can optimize for edge environments.
Compensation Headwinds (2026)
Junior frontend roles: AI coding tools have increased the productivity of mid-level engineers enough that some companies are hiring fewer juniors. Entry-level frontend competition has intensified.
Legacy stack enterprise: Classic Java enterprise, COBOL-adjacent roles, and on-prem infrastructure have stable but slow-growing compensation relative to cloud-native equivalents.
Offshore automation risk: Roles with highly routine tasks (basic CRUD API development, test automation scripting) face increasing competition from offshore markets where AI tools have reduced the skill floor for entry-level work.
For context on how to develop and certify skills in the highest-compensation areas, see our tech certifications worth it guide and our career switch to tech complete guide if you're entering the field.
Negotiation: The Biggest Salary Lever
No section in a salary guide matters more than this one. The numbers in the salary ranges above represent what companies will pay—they do not represent what companies will offer first. Most engineers accept initial offers without negotiating, leaving $10,000–$30,000 per year on the table. At a senior level, the unrealized amount is often larger.
Why negotiation works: Every company's recruiting process assumes negotiation. Initial offers are calibrated to leave room. Recruiters are not penalized for candidates who negotiate; they're doing their job by starting below the ceiling. The cost of attempting a negotiation is close to zero—companies don't rescind offers because a candidate asked for more—and the upside is real and compounding, since subsequent raises and equity refreshes are typically percentages of your base.
The negotiation window opens the moment you receive an offer and closes when you accept. During this window, you have the most leverage you'll ever have in this employment relationship. Once you accept, your next opportunity to move compensation is typically at review cycles or when you have another external offer.
Specific tactics that work:
Never give a number first. If asked for your target salary before an offer, use: "I'm flexible and more focused on finding the right fit—I'm confident we can align on compensation once I learn more about the full package." If you name a number before they do, you've either left money on the table (if your number was too low) or risked anchoring negatively (if it was too high relative to their band). Let them anchor first.
When you receive an offer, ask for time. "Thank you—I'd like to review this carefully and get back to you by [specific date, 48–72 hours out]." This is normal and expected. Using this time, research what comparable roles are paying at that company tier using Levels.fyi and recent job postings, and identify your counter-offer number.
The counter-offer email framework: Express genuine enthusiasm for the role and company. State a specific counter number with brief justification (market data, competing offers if applicable, total scope of role). Ask for confirmation on timeline. Keep it short—3–4 sentences. Don't over-explain or apologize.
Total compensation components beyond base: Equity is often where the largest money lives. RSUs (restricted stock units) at public companies are straightforward—shares that vest over a schedule (typically 4 years with a 1-year cliff). Options at private companies are more complex: the strike price, valuation at grant, and likely exit path all affect actual value. Vesting schedules are negotiable, particularly the cliff. A signing bonus is frequently available and often exists to offset unvested equity you're forfeiting at your current employer—always ask even if it's not in the initial offer. Bonus structure (percentage of base, performance gates, guaranteed first year) should be clarified in writing.
What else is negotiable: Remote work flexibility, start date, equipment budget (particularly relevant for engineers who work on large monitors or specialized hardware), education and conference stipend, and additional PTO. At senior levels, job title can also be negotiable—moving from "Senior Engineer" to "Staff Engineer" in title, even with minimal compensation difference, affects your positioning for future roles.
A real example: A mid-level engineer received an offer from a Series B startup at $165,000 base with 0.3% equity vesting over 4 years with a 1-year cliff. She had a competing offer from another Series B company at $158,000 with 0.25% equity. She presented the competing offer honestly, expressed a preference for the first company, and asked whether they could reach $182,000 base and 0.4% equity. The final offer: $185,000 base, 0.4% equity with the cliff removed on 0.1% (so 0.1% vested immediately). Total outcome: $20,000 more per year in base, and an additional 0.1% equity fully vested on day one. The negotiation email took 20 minutes to write.
Salary Transparency and Market Data Sources
The quality of your salary data directly determines the quality of your negotiation. Walking into a counter-offer with a number you feel is right is much weaker than walking in with three specific comparable data points from verifiable sources.
The main data sources and their trade-offs:
Levels.fyi is the best source for total compensation at large tech companies. Data is self-reported but high-volume, and the platform breaks down TC into base, equity, and bonus components. The level/band information is particularly useful—you can see what an L5 at Google or an E5 at Meta earns across percentiles. Limitation: coverage is thinner for smaller companies, startups, and non-tech-industry engineering roles.
Glassdoor has broad coverage across company sizes and industries. The quality is more variable because there's no verification mechanism and the sample sizes at individual companies can be small. More useful for companies that aren't on Levels.fyi than as a primary source for big tech.
LinkedIn Salary Insights aggregates from profile data and reported compensation and is useful for getting a broad range for a given title and geography. The methodology is opaque, which limits its use as a precise negotiation data point, but it's good for directional validation.
Hired's State of Tech Salaries report (published annually) provides aggregate benchmarks across specializations, experience levels, and metros. Less granular than Levels.fyi for individual company data but more comprehensive for market-wide trends.
Stack Overflow Developer Survey is the largest-sample annual tech compensation survey (90,000+ respondents globally in 2025). Highly useful for cross-technology and cross-country comparisons, but global scope means US figures need geographic filtering to be meaningful.
How to read salary data accurately: Median and mean diverge significantly in compensation data because equity at top companies skews the mean upward. When evaluating a role, compare your offer against median, not mean—the mean includes a small number of very high-TC engineers who distort the average. Equity reporting also varies: some engineers report vesting-year TC (which can spike in equity-heavy years), and others report steady-state annual TC. Ask specifically: "What is the expected total compensation in year two assuming no additional equity grants?"
Pay transparency laws have created a powerful negotiation tool. Colorado (effective 2021), New York City (effective November 2022), and California (effective January 2023) all require employers to include salary ranges on job postings for roles open to candidates in those jurisdictions—and since remote roles are often posted for multiple states, a large percentage of job listings now include salary bands. These bands are the company's own disclosed range for the role. They tell you the ceiling the company has approved for the position.
Practical application: Before submitting a counter-offer, pull the salary range directly from the job posting (if the company posted it). Find 2–3 comparable postings on LinkedIn or Indeed from similar-tier companies in your target market. Look up the role on Levels.fyi filtered to the company's size band. Combine these three data points into a specific number that represents the 80th–90th percentile of the disclosed range. This is your counter-offer anchor. "Based on current market data and the published range for this role, I'd like to come in at $X" is a materially stronger position than "I was hoping for a bit more."
Methodology
Primary data sources: Levels.fyi verified compensation database (tech company-specific, primarily Tier 1), Stack Overflow Developer Survey 2025 (global, 65,000+ respondents), Dice Tech Salary Report 2025 (US tech hiring market), LinkedIn Salary Insights (job listing compensation data), Glassdoor Compensation Data, and Bureau of Labor Statistics Occupational Employment and Wage Statistics (May 2025). YoY growth figures are from LinkedIn's 2025 Jobs on the Rise report and Burning Glass Technologies job market analysis. Geographic adjustment multipliers are from Numbeo cost-of-living indices and Levels.fyi geographic salary data. All figures are in USD and reflect base salary unless otherwise noted; total compensation at major tech companies includes equity and bonuses that can increase figures significantly.