Software Engineer Salary by US City (Adjusted for Cost of Living)

Software Engineer Salary by US City (Adjusted for Cost of Living)

Software engineer salary by city ranges from roughly $150,000–$220,000+ nominal senior base in San Francisco and New York, down to $110,000–$160,000 in lower cost metros like Austin or Raleigh — but the cost-of-living-adjusted ranking often flips the order.

Updated for 2026. Salary figures are indicative ranges and move quarterly — always cross-check against a current source before negotiating.

Nominal vs. Cost-of-Living-Adjusted Table

Nominal figures are indicative senior-level base salary ranges, assembled from Levels.fyi, U.S. Bureau of Labor Statistics metro data, and Glassdoor/Indeed aggregates. The adjusted column applies a typical cost-of-living index relative to a US national baseline of 100 — treat both columns as ranges, not exact figures.

How Two-Career Households Change This Calculation Entirely

Every comparison in this article implicitly assumes a single income evaluating a single city. Households with two working adults face a meaningfully more complex calculation, since a city that offers an excellent salary and job market for one partner's specific field may offer a much thinner or lower-paying market for the other partner's field, and the combined household outcome can favor a city that looks worse on paper for the higher earner alone. Major hub cities generally offer more career depth across a wider range of fields simply through sheer size and economic diversity, which is one of the less-discussed reasons two-career households disproportionately cluster in larger, more expensive metros despite the higher cost of living, even when a single-career household modeling the same numbers might reasonably choose a smaller, cheaper city instead.

Before applying any of the single-income comparisons in this article to a two-career household decision, model both partners' realistic job markets in each candidate city separately, since the total household outcome, not either individual salary figure, is what actually determines whether a move improves the family's real financial position.

How Cost-of-Living Indexes Are Actually Built (and Where They Mislead)

A cost-of-living index compares a fixed basket of goods and services — typically weighted heavily toward housing, with smaller weights for groceries, transportation, healthcare, and childcare — between a target city and a baseline, usually the national average. The weighting choices behind any given index matter enormously and are rarely disclosed in the single number that gets quoted. An index that weights housing at fifty percent of the basket will rank a expensive-rent city very differently than one that weights it at thirty percent, even comparing the exact same two cities.

This matters because most people's actual spending pattern does not match the index's assumed basket. A renter with roommates in San Francisco experiences a very different real cost of living than the index assumes for a median one-bedroom apartment, and a family with two children experiences childcare costs that most general cost-of-living indexes underweight relative to their real impact on a household budget. Treat any single adjusted figure as a rough starting point specific to a "median" household that may not resemble yours, and sanity-check it against actual rent listings and your own likely spending pattern in the specific neighborhood you would live in, not the city average.

How Suburbs and Satellite Cities Change the Math Further

Most city-level comparisons, including this one, use a single figure for an entire metro area, which flattens meaningful internal variation between an expensive urban core and its more affordable surrounding suburbs or satellite towns. An engineer willing to live thirty to forty-five minutes from a downtown core in almost any major metro on this list can typically access meaningfully lower housing costs than the city-center figure implies, while still commuting into the same job market and, increasingly, only needing to make that commute a few days a week under hybrid work arrangements. This single choice — urban core versus a well-connected suburb — often moves the real cost-of-living comparison more than choosing between two entirely different metro areas does.

The trade-off is real and worth naming honestly: longer commutes cost time and, for some people, meaningfully affect quality of life regardless of the financial savings, and a fully remote or strongly hybrid arrangement makes this trade-off far more favorable than a strict five-day in-office expectation would. Anyone doing a serious city comparison should model at least two housing scenarios per city — urban core and reasonable suburb — rather than relying on a single blended metro figure that may not reflect where they would actually choose to live.

Remote Work and the Collapsing City Premium

One of the more significant shifts in US tech pay over the last several years has been the partial decoupling of salary from physical location as remote and hybrid work expanded. Companies that once paid strictly by office city increasingly offer a smaller number of pay tiers — sometimes as few as two or three across the entire country — or, in some cases, a single national rate regardless of where an employee actually lives. This benefits engineers in lower cost cities who can now access big-tech-level compensation without relocating, and it puts modest downward pressure on the traditional premium that expensive hub cities commanded purely for being where the office was.

That said, this shift is uneven. Some employers reversed course and reinstated stricter location-based pay after initially loosening it, and in-office or hybrid-mandate policies at several large employers have partially restored the geographic premium for roles requiring physical presence. Check an employer's specific, current remote-pay policy directly rather than assuming either the fully flexible or fully location-locked model applies — this detail alone can be worth a meaningful percentage of total compensation for an engineer who could otherwise live anywhere.

Why the Same Job Title Pays So Differently by City

• Concentration of large tech employers. More competing employers in one metro pushes offers up regardless of local cost of living.
• Housing cost dominates the adjustment. Housing typically drives 40–60% of the difference in a cost-of-living index, far more than groceries or transit.
• State and local tax structure. Cities in states with no income tax (e.g. Texas, Washington) retain more take-home pay per nominal dollar than the raw salary figure alone suggests.
• Remote-pay policy. Some employers apply a location-based pay adjustment for remote workers; others pay one national rate — this single policy detail can matter more than the city itself.

A Closer Look at Three Common City Comparisons

San Francisco Bay Area vs. Austin. This is one of the most frequently discussed comparisons in tech, largely because Austin absorbed a wave of relocations from California over recent years. The nominal salary gap favors San Francisco by a wide margin, but Austin's substantially lower housing costs and Texas's lack of state income tax close much of the real-terms gap. The trade-off Austin does not fully close is job market depth: San Francisco still hosts a denser concentration of large tech employers and a faster-moving internal promotion market at the largest companies, which matters more for engineers early in their careers building toward a specific specialization.

New York City vs. Raleigh-Durham. New York's nominal premium is real but comes with among the highest housing costs of any major US metro, meaningfully eroding real income for anyone renting or buying within a reasonable commute of a Manhattan-based office. Raleigh-Durham has grown as a secondary tech hub anchored by several large employers and a strong local university pipeline, offering a real-terms outcome that often outperforms New York for engineers not specifically pursuing finance-adjacent tech roles concentrated in New York.

Seattle vs. Denver. Seattle's large-employer concentration (notably in cloud infrastructure and e-commerce) sustains a nominal premium over Denver, but Washington State's lack of income tax narrows the real gap versus states with higher income tax rates. Denver has grown steadily as a hub for remote-friendly and mid-size tech employers, with a materially lower cost of living than Seattle, making it a common landing spot for engineers prioritizing lifestyle and cost over maximum nominal pay.

How State Income Tax Changes the Real Comparison

State income tax is one of the most underweighted factors in casual city salary comparisons, and it can shift a real-terms ranking meaningfully on its own. States with no state income tax — including Texas, Washington, Florida, and Nevada — let an engineer retain a larger share of nominal pay than an equivalent salary earned in California or New York, where combined state and sometimes local income tax can exceed ten percent of income at higher salary bands. This does not mean no-income-tax states always win a real-terms comparison, since these states often fund services through other taxes (sales tax, property tax) that partially offset the income tax savings depending on your specific spending pattern, particularly homeownership.

The practical takeaway is to model state and local tax specifically for your own income level and likely spending pattern, rather than relying on a single "no income tax equals better deal" heuristic. A renter with no plans to buy property experiences a different real tax burden than a homeowner in the same no-income-tax state.

What These Numbers Do Not Include

• Individual housing choices. Renting a shared apartment far from the city core versus buying downtown produces wildly different real costs within the same city.
• State/local tax nuance. Property tax, sales tax, and local tax credits vary within a state, not just between states.
• Career optionality. Thinner job markets in cheaper cities carry more risk if a layoff happens, which a salary table cannot price in.
• Equity and bonus. Larger at big tech employers concentrated in expensive hubs, which narrows the real gap the adjusted column suggests.
• Family-specific costs. Childcare and school costs vary by city far more than the general cost-of-living index captures.

Secondary Costs That Change the Real Comparison Between Cities

Beyond housing and income tax, several secondary costs move the real comparison between cities more than most casual analyses account for. Commute costs and time vary enormously: a city with cheaper housing further from the office core can quietly erase much of its cost advantage through longer commutes, vehicle costs, or the opportunity cost of hours spent traveling that a shorter commute in a pricier city would return to you. Childcare costs vary by a wide margin between metros and are frequently underweighted in general cost-of-living indexes relative to how large a share of an actual family budget they consume, particularly in cities with high childcare-worker wages driven by the same cost-of-living pressures affecting housing.

Healthcare costs, where relevant beyond an employer's insurance plan, and state-level differences in out-of-pocket costs for common procedures also vary by state in ways a simple index rarely captures well. None of these secondary costs will individually change a city ranking as dramatically as housing does, but stacked together they can meaningfully shift a marginal comparison between two closely-ranked cities, particularly for engineers with families rather than single engineers early in their careers.

How to Read Employer-Provided Relocation Packages

When an offer includes a relocation package, read the specific terms closely rather than treating "relocation assistance" as a uniform benefit across employers. Some packages cover a lump sum intended to offset moving costs broadly, letting the employee decide how to allocate it; others cover specific itemized costs like a moving company and a limited number of temporary housing nights, which can fall well short of actual costs in an expensive destination city. A small number of employers include a cost-of-living-adjusted signing bonus specifically intended to bridge the gap during the first year in a new, more expensive city, tapering afterward, and it is worth asking directly whether any offered bonus is one-time or recurring, since the two are easy to conflate when reading an offer letter quickly.

Also ask whether the relocation package includes any clawback provision requiring repayment if you leave within a certain window, a common but not always prominently disclosed term that can matter if your circumstances change sooner than expected after a move.

The Five Mistakes

1. Comparing nominal salary across cities without any cost-of-living adjustment. This is the single most common error in city salary comparisons shared online.

2. Using a generic cost-of-living index without checking the housing assumption behind it. A single-person renter and a family buying a house experience very different real costs in the same city.

3. Assuming remote pay is city-agnostic. Many employers apply location-based adjustments; confirm the specific policy before assuming a nominal national range applies.

4. Ignoring state and local tax differences. No income tax states can meaningfully close a nominal salary gap versus a higher-paying, higher-tax state.

5. Underweighting career optionality when choosing a cheaper city. Long-term promotion speed and job market depth matter as much as this month's cost-of-living math.

How Career Stage Changes the Right City Decision

The right city trade-off looks different depending on career stage, and a single blanket recommendation misses that. Early in a career, proximity to a dense concentration of employers matters more than it will later, since the ability to change jobs quickly if a first role turns out poorly, or to gain exposure to varied projects through internal mobility at a large employer, compounds into meaningfully faster skill growth than the same years spent isolated in a market with only one or two realistic employers. This favors accepting a somewhat lower real-terms outcome in a major hub city during the first several years of a career, in exchange for the optionality and exposure that market provides.

Later in a career, once an engineer has an established reputation, a strong professional network, and enough seniority to negotiate remote or hybrid arrangements, the calculation often flips: the marginal career benefit of physical hub-city presence shrinks, while the cost of hub-city living remains high or grows further, particularly for engineers starting families and needing more space. This is a major reason why cheaper, family-friendly metros have absorbed a wave of relocations from more senior engineers over recent years, even as those same cities remain a less obvious first choice for someone just starting out.

A Practical Way to Compare Two City Offers

When comparing two real offers in different cities, skip the generic index and build a rough personal comparison instead. Start with each offer's nominal base salary, subtract an estimate of your actual likely rent or mortgage payment in each city for housing you would genuinely accept (not a city median you would never choose), subtract your best estimate of state and local income tax for each location, and compare what remains. This "residual income" comparison, even done roughly on the back of an envelope, is usually more useful than any published cost-of-living index because it reflects your actual housing choice rather than an assumed basket.

Add one more check specific to tech careers: look at how many other relevant employers exist in each city for your specific specialization, not just the total tech employer count. A city with fewer overall tech jobs but a genuine concentration in your specific niche — for instance a city known for fintech or gaming — can offer better long-term optionality than a larger, more generic tech market where your specific skill is a smaller slice of local hiring.

🔗 For the international version of this comparison, see software engineer salaries around the world, or return to Tech Salaries Ranked.