인사이트 목록으로
tech salary 2026software engineer salaryML engineer salaryAI salaryproduct manager salarydata science salarysecurity engineer salaryRSU equitytotal compensationtech careersalary negotiationlevels fyicompensation benchmark

2026 Tech & Engineering Salary Report

💻 Salary Benchmarks Series

2026 Tech & Engineering
Salary Report

Real Numbers by Specialization

"Software Engineer, Senior" is not a salary. It's a placeholder. This report breaks down what you actually earn — or should — by specialization, employer tier, and level. No vague ranges. No last year's data dressed up as current.

Updated January 2026 14-min read US-focused · Global notes included
How Tech Comp Works Software Engineering AI / ML Product Data Security & Infra Equity Deep-Dive Negotiation FAQ

You've seen the salary surveys. "$110K–$180K for a Senior Software Engineer." Technically true. Practically useless. A Senior SWE at a 40-person Series B in Columbus and a Senior SWE (L5) at Google in Seattle are doing nominally comparable work — the difference in total compensation can be $150,000 a year. That's not a range. That's a different life.

This report cuts the data by what actually matters: your specialization, your level, and the tier of company you're at. It covers software engineering, AI/ML, product management, data science and analytics, and security/infrastructure. Where relevant, it includes total compensation — base plus equity plus bonus — because that's the number that actually goes to your bank account.

All base figures are in USD for major US markets (NYC, SF, Seattle, Chicago, Austin). For remote roles, employer-tier benchmarks apply more than geography. International context is flagged where the gap is meaningful.

📐

How to read the tables

Ranges show the 25th–75th percentile base salary for that role/level in major US markets. The "top-of-band" figure is a real data point, not a ceiling — 25% of people at that level earn more. Equity and bonus figures are annual equivalents and addressed separately. Remote roles skew toward the employer's HQ tier, adjusted down ~10–20% for non-coastal locations.

The Framework

How Tech Compensation Actually Works

Before any number makes sense, you need the mental model. Tech compensation at most companies above ~100 employees has three components that matter:

Total Compensation = Base + Equity (annualized) + Bonus

Base Salary
~40–60% of TC
RSU / Equity
~30–45% of TC
Annual Bonus
~10–20% of TC

At hyperscalers (Google, Meta, Microsoft, Amazon), equity can exceed base. At startups, base is higher relative to equity, which is in illiquid options.

The "employer tier" framework is the single most important lens for reading tech comp data. It's not about prestige — it's about how each tier prices talent and structures offers.

Tier 1
Hyperscalers
Google, Meta, Apple, Amazon, Microsoft, Stripe, Salesforce
Highest TC. RSU-heavy. Rigid bands. Hard to get in.
Tier 2
Growth-Stage
Well-funded Series D+, recent IPOs, mid-size public tech
Strong base. Good equity upside. Faster scope growth.
Tier 3
Early-Stage
Seed through Series C, sub-200 employees
Lower base. High option grants. Equity is a bet.
Tier 4
Non-Tech Employers
Banks, retailers, healthcare, enterprise software legacy
Competitive base. Minimal equity. More predictable.

Throughout this report, salary ranges are anchored to Tier 2 as the baseline — it represents the broadest and most accessible market for most tech professionals. Tier 1 premiums and Tier 3 discounts are noted where the gap is significant.

01 / Software Engineering

Software Engineering Salaries

The biggest function, the widest range, and the level that matters more than the title.

Leveling systems differ wildly across companies, but a rough universal translation holds: Junior (0–2 yrs), Mid (2–5 yrs), Senior (5–8 yrs), Staff (8–12 yrs, or equivalent IC leadership), Principal / Distinguished (above that). The important caveat: years of experience are a weak proxy. A highly capable engineer can reach Senior in 3 years; a coasting engineer might never leave Mid.

Use the scope definition, not the year count, to calibrate your level before benchmarking.

Level Scope Signal Base (Tier 2) Est. TC (Tier 1) Base (Tier 4)
Junior / L3 Guided tasks, defined scope $90K–$125K $180K–$230K TC $75K–$100K
Mid / L4 Independent features, some mentoring $120K–$160K $230K–$300K TC $95K–$130K
Senior / L5 Owns systems, drives tech decisions $155K–$210K $300K–$420K TC $120K–$160K
Staff / L6 Cross-team impact, architecture ownership $195K–$260K $420K–$580K TC $145K–$190K
Principal / L7+ Org-wide or company-wide technical direction $240K–$330K $550K–$900K+ TC $170K–$230K

TC = Total Compensation (base + annualized RSU + bonus). Tier 1 TC figures sourced from Levels.fyi aggregates, Q4 2025.

The IC vs. Management Fork

At most large tech companies, there are two valid career tracks past Senior: the Individual Contributor (IC) track (Staff → Principal → Distinguished → Fellow) and the Engineering Manager track. Compensation is roughly equivalent at each level equivalency — a Staff SWE and an Engineering Manager leading 6–8 people earn similar base in the same company.

The choice between them is about what work you want to do, not which one pays more. What it's not: a seniority ladder where you have to manage people to advance. The IC track at hyperscalers goes all the way to Fellow-level compensation in the multiple millions. Don't take the management track because you think it's the only way up.

Specialization Premiums on Top of SWE Base

Not all Senior SWE roles are priced equally. These specializations consistently earn above the generalist SWE band:

Distributed Systems / Infra
+15–25% premium
High barrier to entry; hard to hire for
Security Engineering
+20–30% premium
Compliance + breach pressure; scarce talent
Compiler / Systems (C++, Rust)
+15–20% premium
Very small candidate pool
Mobile (iOS/Android)
~Flat to +10%
Premium at consumer tech; discount elsewhere

02 / AI & Machine Learning

AI / ML Engineering Salaries

The highest-demand discipline in tech. The premium is structural, not temporary.

The AI/ML engineering market in 2026 is split into two distinct segments: applied ML engineers who build and deploy models within products (the larger group), and frontier ML researchers who advance the underlying science (the smaller, extraordinarily well-compensated group). If you're not at a lab, you're almost certainly in the applied segment — and that's where most of the hiring is happening.

Every major enterprise is deploying AI into products, workflows, and infrastructure. The bottleneck is people who can actually build production-ready AI systems — not just train a model in a notebook, but deploy, monitor, and iterate on it at scale. That scarcity is reflected in comp.

2026 Market Signal

AI/ML commands a 25–45% premium over comparable generalist SWE roles.

This premium is broader than "AI labs." Enterprise SaaS, fintech, healthcare tech, and even traditional industries are actively outbidding each other for ML talent. The demand is outpacing supply through at least 2027.

Role Level Base Range Est. TC (Tier 1)
ML Engineer Mid $145K–$190K $270K–$360K TC
ML Engineer Senior $185K–$255K $360K–$520K TC
ML Engineer / Staff Staff $230K–$310K $500K–$750K TC
AI Research Scientist Mid–Senior (Lab) $220K–$340K $450K–$900K+ TC
LLM / GenAI Engineer Mid–Senior $170K–$260K $320K–$500K TC
MLOps / AI Infra Engineer Senior $165K–$230K $310K–$450K TC

Research Scientist figures reflect top-tier AI labs (Anthropic, OpenAI, Google DeepMind, Meta AI). Applied ML at non-lab companies is the row above.

If you're adjacent to AI but don't have the title yet:

Data engineers who've built LLM pipelines, backend engineers who've integrated AI APIs into production systems, and analytics engineers who've built RAG workflows are commanding ML Engineer-adjacent comp. The credential matters less than the demonstrated production experience. Document what you've shipped.

03 / Product Management

Product Manager Salaries

High comp ceiling, wide variance, and a title that means wildly different things across companies.

Product Management is arguably the highest-variance role in tech when it comes to comp. At a hyperscaler, a Senior PM runs a product area touching millions of users, earns $250–350K+ total comp, and has the organizational leverage to make decisions worth hundreds of millions. At a 30-person startup, a "Senior PM" might be the only PM and earn $130K with minimal equity. The title is almost irrelevant. Scope is everything.

Level Scope Signal Base (Tier 2) Est. TC (Tier 1)
Associate PM Feature-level, high mentorship $95K–$130K $190K–$240K TC
PM Product area ownership, independent $130K–$175K $240K–$330K TC
Senior PM Multi-team, revenue or retention impact $155K–$215K $300K–$430K TC
Principal / Group PM Multiple PMs, P&L ownership $195K–$265K $400K–$600K TC
Director / VP of Product Business unit, full product strategy $230K–$340K $500K–$900K+ TC

The AI PM premium is real

PMs with genuine technical depth in AI/ML — who can work credibly alongside research and engineering teams on model-adjacent products — are seeing 20–30% comp premiums over comparably leveled generalist PMs. If your current product involves any AI surface area and you're building that fluency, it's worth calling out explicitly in any negotiation.

04 / Data

Data Science & Analytics Salaries

Three distinct tracks with different comp ceilings. Know which one you're actually on.

"Data" is not one career. The field has matured into three distinct tracks, each with different work, different skills, and different comp trajectories. Where you sit matters for benchmarking.

Track A
Data Science
Statistical modeling, experiments (A/B tests), predictive analytics, business insight generation
Mid–Senior: $120K–$180K
Track B
Data Engineering
Pipelines, warehouses, infrastructure, data reliability — the plumbing that everything else runs on
Mid–Senior: $130K–$195K
Track C
Analytics Engineering
dbt, metrics layers, semantic models — the translation layer between raw data and business decision-making
Mid–Senior: $120K–$175K
Role Level Base Range Note
Data Scientist Mid $115K–$155K Varies heavily by industry vertical
Senior Data Scientist Senior $145K–$200K Bonus 10–20%; some RSU at scale cos
Staff Data Scientist Staff $185K–$250K Effectively a science leadership role
Data Engineer Mid–Senior $130K–$195K Strongest demand growth in data
Analytics Engineer Mid–Senior $115K–$170K Fast-growing role; newer title
Data Analyst Mid–Senior $85K–$130K Ceiling lower without engineering skills

The single most reliable way to increase your comp in data is to push up the engineering skill stack. A data scientist who can build production pipelines, or an analyst who can write dbt models and own a data product, earns in a different bracket. It's not glamorous career advice — it's just where the market prices the work.

05 / Security & Infrastructure

Security & Infrastructure Salaries

The most consistently underestimated comp segment in all of tech. If you're here, you're likely underpaid.

Security engineering is structurally underpaid relative to its market value and its criticality. The reason is cultural: security teams are often staffed as cost centers, not value generators. Boards understand this after a breach. The comp market knows it before one happens — which is why experienced security engineers at companies that do understand the stakes earn more than their headcount would suggest.

Platform / infrastructure engineering is in a similar position: less visible than product engineering, but often the highest-leverage work in the stack. Senior infra engineers who have rebuilt observability systems, tamed cloud costs, or built developer platforms are increasingly in demand and increasingly aware of it.

Role Level Base Range Context
Security Engineer Mid $130K–$175K Appsec, cloud sec, detection
Security Engineer Senior $175K–$240K +25–30% vs. generalist SWE same level
Security Architect Sr. / Staff equiv. $195K–$270K Fintech/healthcare pay top of band
Platform / Infra Engineer Senior $165K–$225K Cloud cost optimization a hot skill in '26
DevOps / SRE Senior $155K–$215K SRE (Google model) skews higher
CISO Executive $260K–$450K+ Significant equity; highly variable

06 / Equity

Equity: What You Actually Need to Know

RSUs are real money. Options are a bet. Neither is complicated once you understand the mechanics.

RSUs (Public Companies)

  • Vest over 4 years, typically quarterly after year 1 cliff
  • Taxed as ordinary income when they vest
  • Price at vesting = your actual comp
  • Refreshes: high performers get new grants annually
  • Rule of thumb: A $200K RSU grant = $50K/year in cash, pre-tax

Options (Private Companies)

  • Right to buy shares at the strike price (usually set at last 409A valuation)
  • Only valuable if the company exits above your strike price
  • ISOs vs. NSOs have different tax treatment — read the difference
  • You often have 90 days post-departure to exercise (or lose them)
  • Rule of thumb: Worth $0 until there's a liquidity event

The honest question to ask before accepting options:

"If this company exits in 5 years at 3× the current valuation, and I exercise at my strike price, what do I actually take home after dilution and taxes?" If you can't answer that, the number in your offer letter is theoretical. Ask the recruiter for the current cap table details, preferred shares outstanding, and last 409A price. Good companies give you this. The answer tells you a lot.

07 / Negotiation

Using This Data in a Negotiation

Benchmarks only matter if you can put them on the table. Here's how.

The data in this report is only useful if you know how to deploy it. Walking into a negotiation and saying "the internet says this role pays $180K" is not a strategy. Here's what actually works.

1

Triangulate from three sources, not one

This report + Levels.fyi (for your exact role/company tier) + a salary-disclosed job posting for a comparable role in your market. Three sources pointing to the same range gives you a defensible anchor. One source is a claim. Three sources is evidence.

2

Lead with total comp, not just base

If you're moving from a company with strong RSU grants to one with fewer, the base has to carry more weight. Frame your current comp as total comp — not just the base — and benchmark their offer on the same basis. This is standard and expected at senior levels.

3

Ask for the band before the offer

Pay transparency laws have normalized this. "Before we get into the details, can you share the comp band for this role?" If they've already asked for your expectations, you can respond with: "I'd rather discuss that once I have a sense of your band — it helps me calibrate." Most companies in 2026 will give you a number.

4

Specialization is a comp argument

If your role sits in a premium specialization (AI/ML, security, infra), name it explicitly. "I've noticed that roles with this specialization typically price at the top end of the generalist SWE band — I'd expect this offer to reflect that." You're not making a demand. You're calibrating their anchor to the right market.

For a full negotiation playbook — scripts, tactics for stalled offers, and handling exploding deadlines — see the Salary Negotiation Playbook (C-1-P) and Exactly What to Say in a Salary Negotiation (C-1-C2).

FAQ

Frequently Asked Questions

I'm a Senior SWE but my company calls everyone "Engineer." How do I know my real level?
Calibrate by scope and impact, not title. Are you driving technical decisions independently? Do you own systems end-to-end? Do you influence architecture choices? Do you mentor more junior engineers without being asked to? If yes to most of these, you're operating at Senior level by any standard definition. Look at Google's career ladder public documentation (they publish it) as a universal reference point — match your actual responsibilities to their level descriptions.
My total comp is $180K but most of that is RSUs. Am I underpaid?
Not necessarily — but you need to look at the full picture. If your RSUs are vesting at a public company with a stable or appreciating stock price, that's real comp. The question to ask: at your level and specialization, where does your total comp land relative to the benchmarks in this report? If your $180K TC is split $120K base / $50K RSU and you're a Senior SWE in SF, you're meaningfully below Tier 1 comp but might be in-band for Tier 2. The more important question: is your current company positioned to refresh those grants, and at what rate?
Do these ranges apply to fully remote roles?
Most large tech companies now pay to your location, not the company's HQ. If the company is SF-based and you're in Austin, you'll likely be paid Austin-tier rates — roughly 15–20% below the full SF range. A minority of companies pay a flat national rate regardless of location. If that's the case (increasingly rare), treat the SF figures as your reference. Always ask explicitly: "Does the comp band vary by location?" before the offer stage.
I'm a self-taught engineer with no CS degree. Does that affect my comp?
At most growth-stage and forward-looking companies: no. Tech comp is almost entirely skill- and output-based, not credential-based. A strong portfolio, demonstrable impact, and the ability to perform in technical interviews will get you the same band as a CS grad. Where it still matters: certain large financial institutions and legacy enterprises with formal HR credentialing requirements. These are also the companies most likely to be in our Tier 4 bracket — where comp is lower across the board anyway.
What's the best move if I'm significantly below the 25th percentile?
Two parallel tracks. First: talk to your manager now. Bring data, frame it as market alignment (not complaint), and ask specifically: "Is there a path to bringing my comp to market rate, and what does that timeline look like?" If the answer is "maybe at your next review cycle" — that's months of compounding gap you're eating. Second: run a passive job search. Get an offer. You don't have to take it, but it recalibrates your manager's conversation and your own confidence. The most reliable path to a market-rate correction at your current employer is often a competing offer.

Key Takeaways

What to do with this data

Benchmark on TC, not base. At Tier 1 companies, base can be less than half the story. Never compare offers on base alone.

Calibrate your level by scope, not title. Your employer's leveling system is not the market's. Find your equivalent using scope signals.

AI/ML and security premiums are real and structural. If you have these skills, price them explicitly — don't wait for a manager to notice.

The IC track and the management track pay the same. Choose based on the work you want to do, not which one you think pays more.

Options are a bet. RSUs are income. Don't let a large option grant replace a competitive base at a stage where the outcome is genuinely uncertain.

Read Next

Salary Benchmarks Series
2026 Salary Report by Role: The Full Picture
Cross-functional overview + the variables that move your number →
Salary Negotiation Series
Exactly What to Say in a Salary Negotiation
Turn this benchmark into an actual offer increase →
Compensation Literacy Series
Understanding Your Compensation Package (2026)
RSUs, bonuses, benefits — fully decoded →