Compensation Benchmarks: SF vs NYC vs Remote in 2026

The salary conversation in tech has never been more complicated—or more consequential. Remote work normalized cross-geography hiring, then a wave of RTO mandates tried to claw that back, and now in 2026 the market has settled into a genuinely fragmented landscape where two engineers with identical titles and skill sets can have total compensation that differs by $150,000 depending on where they live and who they work for. If you're job hunting or negotiating a raise right now, operating on vibes and outdated data will cost you real money. This guide cuts through the noise with current benchmarks, the real mechanics behind location-based pay, and a clear framework for deciding which market to target.

The Raw Numbers: What Each Market Is Actually Paying in 2026

Let's start with what you actually came here for. The figures below represent total compensation (base + target bonus + annualized equity at current fair value) for software engineers at well-funded private companies and public tech firms. These are not entry-level figures; they reflect mid-to-senior individual contributor roles.

San Francisco Bay Area (in-office or hybrid, SF/South Bay)

• Senior Software Engineer (L5 equivalent): $280,000–$380,000 TC
• Staff / Principal Engineer (L6 equivalent): $380,000–$550,000 TC
• Engineering Manager (6–10 reports): $320,000–$480,000 TC

New York City (in-office or hybrid)

• Senior Software Engineer: $260,000–$350,000 TC
• Staff / Principal Engineer: $350,000–$500,000 TC
• Engineering Manager: $300,000–$450,000 TC

Remote-first roles (US-based, no geographic restriction from employer)

• Senior Software Engineer: $200,000–$320,000 TC
• Staff / Principal Engineer: $300,000–$450,000 TC
• Engineering Manager: $260,000–$400,000 TC

Remote roles with geo-adjusted pay (e.g., Tier-2 city or non-US)

• Senior Software Engineer: $140,000–$220,000 TC (USD equivalent)
• Staff / Principal Engineer: $200,000–$320,000 TC

The gap between SF and remote is real but has compressed since 2022. The bigger gap is between companies that pay market rate and those that don't—that spread dwarfs any location differential at the senior level.

Why SF Still Pays More (And Why That Gap Is Shrinking)

San Francisco's pay premium has never purely been about cost of living. It's about concentration of capital, density of high-margin businesses, and labor market competition. FAANG and their direct competitors have historically used compensation as a retention weapon, and because they're all headquartered within 50 miles of each other, they've bid up the market for decades.

That dynamic is weakening for two reasons. First, the 2022–2024 tech contraction reduced headcount and chilled the bidding wars. Second, remote-first companies—particularly in fintech, infrastructure tooling, and developer tools—have demonstrated they can attract L6+ talent without office mandates, and they've priced accordingly.

That said, the top of the SF market remains the highest absolute dollar figure you'll see in software engineering outside of finance. If you're targeting TC above $400,000 at the senior IC level, SF (or a remote role at a SF-headquartered company that pays SF rates regardless of location) is still your most reliable path.

The location premium debate misses the point. The company tier premium is 2–3x larger than any city premium. A Staff Engineer at Stripe remote earns more than a Senior Engineer at a Series A startup in SoMa.

NYC Is Not Just "SF Lite"—It Has Distinct Advantages

New York's tech market in 2026 has meaningfully matured. It's no longer a consolation prize for engineers who couldn't land a Bay Area role. A few things NYC does better:

1. Finance-adjacent roles pay a significant premium. If you're building trading infrastructure, risk systems, or anything touching financial data at a bank, hedge fund, or fintech, NYC compensation regularly exceeds SF equivalents at the same level. A Senior SWE at a major hedge fund's technology arm can see $350,000–$500,000 TC—and some of that is cash-heavy, which matters if you're skeptical of illiquid equity.
2. The startup ecosystem has depth in specific verticals. Media tech, adtech, climate tech, and healthtech are all well-funded in NYC. If your interests align, you'll find competitive comp without competing against the density of candidates that SF roles attract.
3. Cost of living math is different but not simpler. Manhattan rents are brutal, but NYC's broader metro (Brooklyn, Jersey City, Hoboken) offers more optionality than the Bay Area's commute geography. Net purchasing power for a senior engineer in Brooklyn vs. South Bay is closer than the gross comp gap suggests.
4. Remote from NYC is increasingly viable. Many NYC-headquartered companies have accepted hybrid as the new baseline post-2024. You can earn NYC-tier comp while living somewhere cheaper within a 2-hour radius.

Remote Work Compensation in 2026: The Honest Assessment

Remote comp has bifurcated sharply. There are now two distinct categories, and conflating them is a mistake.

Category 1: Location-agnostic remote pay. A minority of companies—mostly developer-tools companies, crypto-native firms, and some infrastructure businesses—pay the same rate regardless of where you live. These roles advertise openly that they pay "market rate" or "top of band regardless of location." If you land one of these while living in a low cost-of-living area, the purchasing power arbitrage is extraordinary. A $280,000 TC role in Austin or Vancouver is a different financial life than the same number in San Francisco.

Category 2: Geo-adjusted remote pay. The majority of large companies that offer remote work apply location-based pay bands. Google, Meta, Amazon, and most Fortune 500 employers will reduce your offer by 15–30% if you're not in a Tier-1 metro. If you're in Canada (like many of Amazon's Vancouver engineers), the discount relative to US rates can be even more pronounced once you factor in currency, tax treatment, and benefits differences.

For Canadian-based engineers specifically: your USD-equivalent comp at a US employer will depend heavily on whether the role is structured as a US or Canadian position. US-structured roles with Canadian employment tend to pay 20–35% less than equivalent SF roles when converted at current exchange rates, but your tax rate and cost of living often make the net position competitive.

The remote market rewards specialization. If you have rare skills—distributed systems at scale, ML infrastructure, security engineering—you can negotiate location-agnostic pay even at companies that don't advertise it. The leverage shifts when you're hard to replace.

Equity vs. Cash: How to Think About It by Market

This is where most compensation guides get lazy and just say "it depends on your risk tolerance." Here's a more useful framework:

• SF pre-IPO equity has a highly bimodal outcome distribution. The expected value math looks great on paper; the median outcome is much less exciting. If you're joining a Series B or later company with strong signal (top-tier lead investors, clear path to profitability), the equity is worth modeling seriously. If you're joining a Series A with a $500M valuation in a down market, discount it aggressively.
• Public company RSUs in SF or NYC are effectively deferred cash with a vesting schedule. Treat them as cash at current price minus a liquidity discount (typically 10–15% to account for blackout windows and forced selling constraints).
• Remote-first companies often have more cash-heavy packages, particularly those that are bootstrapped or late-stage private. This is a feature, not a bug—if you're remote and optimizing for lifestyle stability, a higher base with lower equity exposure is often the right trade.
• Canadian-employed roles typically don't include US equity structures. Stock options for a Canadian subsidiary of a US parent can have complex tax treatment; always model the after-tax value, not the face value.

The Negotiation Lever That Matters Most in 2026

Everyone focuses on the initial offer. The bigger money is in knowing what band you're in and negotiating toward the top of it—not just accepting the midpoint. Here's what's changed in 2026 that works in your favor:

1. Pay transparency laws have expanded. California, New York, Washington, and Colorado all require salary range disclosure. More states are following. This means you walk into negotiations with more information than you had three years ago.
2. Competing offers are still your most powerful lever. A documented offer from a comparable employer moves you from a conversation about your worth to a conversation about matching market rate. These are different conversations and the second one is much easier to win.
3. Equity acceleration and signing bonuses are negotiable when base is constrained. If a company is at the top of their base band, you can often negotiate a larger refresh grant schedule, accelerated cliff vesting, or a signing bonus that effectively front-loads your compensation.
4. Remote candidates have structural negotiation leverage they underuse. If you're applying to a role that's been open for more than 60 days and you're a strong fit, the cost of re-posting and re-interviewing is real. You have more leverage than your remote status might make you feel.

Most engineers accept the first offer because they're relieved to have it. That's the single most expensive mistake in a software engineering career.

The Practical Purchasing Power Picture

Gross compensation is a vanity metric if you're trying to build wealth. Here's a simplified after-tax, after-housing purchasing power comparison for a Senior Software Engineer earning near the midpoint of each market's range:

• SF ($320K TC): After state + federal taxes (~38% effective rate) and median 2BR rent ($4,200/month in South Bay): ~$145,000 discretionary income annually
• NYC ($300K TC): After state + city + federal taxes (~40% effective rate) and median 2BR rent ($4,000/month in Brooklyn): ~$128,000 discretionary income annually
• Remote in Austin, TX ($250K TC): After federal taxes only (~33% effective rate) and median 2BR rent ($1,900/month): ~$144,000 discretionary income annually
• Remote in Vancouver, BC ($200K USD-equivalent TC): After Canadian federal + BC provincial taxes (~35% effective rate) and median 2BR rent ($2,800 CAD/month, ~$2,000 USD): ~$110,000 discretionary income annually

The punchline: a remote role in a no-income-tax US state at $250K TC is roughly purchasing-power-equivalent to an SF role at $320K TC. Vancouver-based engineers take a real net hit compared to US peers at equivalent title levels, which is why targeting US-structured remote roles or negotiating hard on comp matters more, not less, if you're Canadian.

Next Steps

If you've read this far, you're serious about getting paid correctly. Here's what to do in the next seven days:

1. Audit your current compensation against these benchmarks. Pull your current TC (base + actual bonus paid last year + annualized RSU value at current price) and compare it to the ranges above for your level and location. If you're below the 25th percentile for your market, you have a concrete case to make—either internally or by going external.
2. Check levels.fyi and Glassdoor for your specific company and title. These are imperfect but directionally useful. Cross-reference at least three data points before drawing conclusions. Pay particular attention to offers received in the last six months—data older than a year reflects a different market.
3. Identify three companies in your target tier that are actively hiring for your profile. Apply even if you're not actively looking. Real offers are the only data point that matters in a negotiation, and the interview process gives you market signal you can't get any other way.
4. If you're remote and geo-adjusted, research which companies in your space pay location-agnostic rates. Stripe, Cloudflare, HashiCorp, and a cohort of developer-tools companies have historically done this. One job change to a location-agnostic employer can be worth $40,000–$80,000 in annual TC with no change in where you live.
5. If you're Canadian-based, model your after-tax, after-FX position explicitly. The gap between feeling well-compensated and actually being at market is widest for Canadian engineers at US companies. Run the numbers in USD, convert at current rates, and compare to what a US-resident peer in a similar LCOL area would net. That delta is your negotiation target.

Related guides

• Dual-state tax for remote work in 2026 — when you owe two states and how to plan — Remote tech workers can trigger tax obligations in more than one state. This guide explains residency, nonresident wages, convenience rules, withholding, credits, and the planning steps to take before a remote move.
• Parental Leave at Tech Companies in 2026 — Benchmarks, Policies, and How to Negotiate — Parental leave policies in tech vary widely by company stage, country, caregiver type, and manager culture. This guide gives 2026 benchmarks, policy questions, and negotiation scripts for expecting parents and candidates.
• Remote Work in 2026: What the Market Actually Pays — A no-fluff breakdown of remote tech salaries in 2026, who's hiring, what roles command premiums, and how to negotiate without leaving money on the table.
• 401(k) match norms in tech in 2026 — by company size and stage — A guide to 401(k) match norms across tech companies in 2026, including startup vs public-company patterns, vesting schedules, true match value, mega backdoor Roth availability, and offer-stage questions.
• The 83(b) Election in 2026 — When to File, Deadlines, and What Happens if You Miss It — The 83(b) election can save startup employees and founders from painful vesting-date taxes, but the 30-day deadline is unforgiving. Here is when it applies, how to file, and what to do if you miss it.