How much does a software engineer make in 2026?
A software engineer in the United States earns a typical base salary between $95,000 and $185,000 per year, with a national median hovering around $140,000. Total compensation — the number that actually lands on offer letters at competitive employers — is usually 15% to 60% higher once bonus, equity, and sign-on are included. At large public technology companies (often called FAANG or MAG7), total compensation for mid-level engineers frequently crosses $250,000, and staff-plus engineers routinely see $400,000 to $700,000 all-in. Outside of those tier-one employers the story is different: a mid-career engineer at a mid-sized SaaS company will usually land between $150,000 and $210,000 total, and engineers at agencies, consultancies, or non-tech enterprises tend to earn less in cash but more in stability.
The 2026 market has continued the correction that started in 2023. After the zero-interest-rate hiring boom of 2021-2022, base salaries stopped climbing at the top of the market, and equity refresh grants across public tech companies dropped by roughly 20% to 40% depending on stock performance. What that means practically: the sticker price on senior offers looks similar to two years ago, but the total-compensation curve is flatter. Junior and mid-level pay has stayed remarkably resilient because the pipeline of new-grad hiring never fully recovered — the shortage of proven mid-career engineers keeps their prices firm.
Regional and remote pay policy is the other big story. Companies that promised 'pay anywhere' during the pandemic have almost all moved to geo-tiered bands, usually anchored on three to five zones (e.g. Zone 1 = SF/NYC/Seattle, Zone 2 = other US metros, Zone 3 = rest of US, Zone 4 = international). If you are negotiating a fully remote role in 2026, always ask the recruiter which zone your ZIP code sits in before you talk numbers — the same job title can pay 25% differently on either side of a county line.
Software engineer salary by seniority
Seniority is the single biggest driver of software engineer pay, more than city, more than employer, more than programming language. The industry has converged on a fairly consistent ladder: Intern → Junior (L3 / SDE I / E2) → Mid (L4 / SDE II / E3) → Senior (L5 / SDE III / E4) → Staff (L6 / E5) → Principal / Senior Staff (L7 / E6) → Distinguished / Fellow (L8+). Different companies use different letters and numbers but the substance is the same: at each level you own a broader scope, a longer time horizon, and more leverage on other engineers.
Junior engineers (0-2 years of experience) generally start between $95,000 and $130,000 base in the US. Total comp lands between $110,000 at a small startup and roughly $200,000 at a top-tier public company, mostly because of new-grad sign-on bonuses and initial equity grants. This is the level where you are still being trained; expect closer mentorship and code review, and treat the first two years as an apprenticeship — the compounding value of learning good habits early is enormous.
Mid-level engineers (3-5 years) typically make $130,000 to $170,000 base. Total comp ranges from $160,000 in a boot-strapped shop to $350,000 at a big-tech employer. This is where most engineers spend a large chunk of their career. Companies expect you to own features end-to-end, pair with product on tradeoffs, and mentor at least one junior. The salary curve steepens here, but it steepens most for engineers who take on visible cross-team work.
Senior engineers (6-9 years) command $160,000 to $200,000 base and $250,000 to $500,000 total. The best senior engineers get paid this much because they compress delivery risk. They see around corners, catch design mistakes in review, and coach the mid-level teammates who do most of the day-to-day building. Recruiters will often push senior candidates hard on system-design interviews for this reason; the level bar is dominated by 'can this person be trusted with a large system?'
Staff and principal engineers (10+ years) span an enormous range — $200,000 to $350,000 base, $400,000 to $900,000+ total. At this level, cash rarely differentiates offers; equity, refresh cadence, and grant cliff structure do. If you are negotiating at this level, ask specifically about the refresh grant policy (annual, biennial, based on rating?) and the vesting cliff (four-year with a one-year cliff is standard, but some public companies do a monthly-from-day-one schedule which is materially better).
Software engineer salary by US metro
Location matters, but less than it used to. The San Francisco Bay Area still tops the charts — a mid-level engineer there earns roughly 30% more than the national median, and Seattle and New York are within a few points of the Bay. Boston, Los Angeles, and Washington DC sit at a 10% to 15% premium. Austin, Denver, and Chicago hover close to the national median. Cost-of-living-adjusted, the picture flips: Austin engineers routinely take home more usable income than San Francisco engineers making 30% more on paper.
For remote engineers, the metro your recruiter uses to price you is usually the metro you actually live in — companies pull data from Zillow and local salary APIs and set your band accordingly. If you plan to relocate, tell your employer before you sign the lease; some companies (notably Meta, Airbnb, and Coinbase) will grandfather you in for six to twelve months at the higher band, others will re-anchor the day you move.
Second-tier tech hubs like Raleigh-Durham, Salt Lake City, and Minneapolis have been the biggest gainers in the past three years. Their salary bands are within 5% to 10% of Austin, but housing costs are dramatically lower and the local ecosystems (large employers, well-funded startups, decent university pipelines) have thickened up meaningfully. If you are early-career and want an outsized cost-adjusted salary, those metros are worth serious consideration.
Software engineer salary by specialization
Not every engineering discipline pays the same. Machine-learning and infrastructure engineers command the highest premiums right now, on the order of 15% to 25% above generalist backend engineers at the same level. This premium is real and durable — companies compete for a small pool of people who can train, deploy, and reason about large models in production, and for engineers who can operate globally distributed systems.
Frontend engineering pay has caught up considerably in the past few years. A senior frontend engineer with deep React, accessibility, and performance experience will typically match a senior backend engineer at the same company, especially at consumer-facing employers where UX is the moat. Full-stack engineers land in the same band as their strongest half; if you are strong on both ends, price yourself as a backend or frontend engineer depending on which side the team you interview with is optimizing for.
Embedded, firmware, and games engineering pay less than web / cloud engineering — usually 10% to 25% less at the same level. That gap is closing at companies where the differentiation is hardware (Apple, Nvidia, Rivian, SpaceX), but for mainstream employers it remains real. Security engineering pays a premium of roughly 10% to 20%, and site-reliability / production engineering pays roughly on par with senior backend.
Salary by company stage and funding
Startup equity is worth a real conversation. At seed and Series A companies you will typically see 0.10% to 1.0% of the company as an ISO grant vesting over four years, and cash pay 15% to 40% below public-company benchmarks. This is a trade: you accept less cash today for a chance at large equity gains later. The math almost never works out — the base rate of startup exits large enough to make an engineer's grant worth millions is very low — but the option is real, and the learning curve at a young company is uniquely fast.
Series B and C companies begin to close the cash gap. By Series C, cash is usually within 10% of public-company benchmarks and grants are smaller but on a much clearer valuation curve. This is often the best-value stage for engineers who want meaningful equity upside without accepting a large cash haircut.
Public companies pay the highest cash. Bonus targets range from 5% (small-cap or older tech) to 25% (large-cap FAANG-tier) of base, and equity is granted as RSUs — real, tradeable, taxable-at-vest units. Total-comp visibility is much higher: you can see refresh grant sizes on levels.fyi, Blind, or Glassdoor with reasonable accuracy, and offer negotiation is largely about landing in the top quartile of the visible band.
Bonuses, equity, and total compensation math
Do not compare offers on base salary alone. A $180,000 base at a Series B startup with 0.15% equity vesting over four years, and a $180,000 base at a public company with a $300,000 four-year RSU grant, are not the same offer. Build a four-year total-compensation model for every offer you take seriously. Include base × 4, target bonus × 4 (probability-weighted), RSU grant vesting schedule, expected refresh grants (usually 20% to 40% of new-hire grant per year), and, for private companies, a heavily-discounted estimate of equity value that reflects the base rate of exits at that stage.
Refresh grants are where a lot of engineers get quietly underpaid. A big new-hire grant at year 0 tapers off by year 4 as vesting completes, so the total-comp number your employer quoted when you joined starts falling around year 3 unless they refresh you competitively. If your recruiter cannot articulate the refresh policy in a specific way ('everyone at your level gets a refresh grant equal to X% of new-hire every 12 months, adjusted for rating'), assume the worst and price accordingly.
Sign-on bonuses are usually one-time and clawback-protected — if you leave before the 12- or 24-month anniversary you pay back a prorated amount. They are a good tool for closing a gap when the base or equity band is capped, but they are not real recurring income; do not compare them alongside base in the same column.
International software engineer pay
Software engineer pay outside the US has been rising quickly, but the gap remains substantial. Canada tracks at roughly 70% to 80% of US pay for equivalent roles. The UK, Germany, and Netherlands are in the 65% to 75% range for base cash, though total-comp gaps at big-tech are wider because equity grants are usually smaller. Switzerland is the exception in Europe: base cash for senior engineers at UBS, Google Zurich, or ETH-spinout startups can equal or exceed US levels.
Ireland has become a strong secondary tech hub, largely because of the concentration of US-headquartered employers with Dublin offices. Pay bands are usually indexed to European rather than US benchmarks, but Dublin cost-of-living has climbed to near-London levels, so the deal is not as good as it once was.
In APAC, Singapore leads on both cash and total-comp. Australia is competitive at the senior and staff level, less so at the junior level. Japan has begun to un-cap pay for foreign engineers as demand for AI talent grew, but the base band for local engineers is still capped around ¥18-25M for senior engineers. India, the Philippines, and Vietnam are the largest offshoring destinations; pay for senior engineers at US-headquartered captive centers can equal or exceed the local Big-Four consulting salary at the director level.
For remote-first international employers (GitLab, Deel, Zapier, Automattic, Elastic), the pay policy is usually 'US-anchored with a country multiplier'. That multiplier is where your negotiation happens; recruiters will not volunteer it, but they will confirm or deny a number you name.
Interview leverage and negotiation strategy
The single highest-leverage moment in a software engineer's compensation is the two-week window between passing the on-site and signing the offer. Every dollar you push into the base at that moment compounds through the next several years of raises. Do the work: know the levels.fyi and Blind ranges for your target company and level; know the ranges for two credible competing employers; ask the recruiter what the top of the band is at your level; and always counter, politely, in writing, once.
Do not lead with a number. When a recruiter asks about compensation expectations, deflect once ('I am optimizing for the right role and team; what does the band look like for this level?'), then let them name a range. If pressed, give a wide range that starts at your current total comp plus 20% and ends 10% above the top of the levels.fyi range for your target level. This is not aggressive; it is a normal negotiation starting point at a mature technology company.
Multiple concurrent offers are worth more than any other negotiating tool. If you are actively interviewing, keep processes running in parallel and be transparent with recruiters about timing. Recruiters will often accelerate a late-stage process if they know a competing offer is imminent, and equity ceilings that seemed non-negotiable will suddenly move if the alternative is losing you to a rival.
How Connecting Odds benchmarks salary data
The numbers on this page are triangulated from three source categories that are safe to publish and cite: (1) US Bureau of Labor Statistics OES data (occupation code 15-1252, Software Developers), which gives a legally-audited annual median and percentile band; (2) publicly available compensation reports from Levels.fyi, Glassdoor, Payscale, and the Stack Overflow Developer Survey — we take medians only, never individual points; (3) our own aggregate of publicly-listed salary bands in job postings on Connecting Odds and partner boards. We refresh the underlying dataset every six months and log the refresh timestamp on this page.
We deliberately do not scrape paywalled sources, resell proprietary datasets, or infer salaries from PII. Every band you see here is either from a source that publishes on their own site for public use, or from job postings whose employers chose to publish the band. If you spot a range that looks materially wrong for your market, please email data@connectingodds.com — corrections from active practitioners are the most useful signal we get.