Software Engineer Salary by State: 2026 Data for All 50 States

Before you read any ranking table, you need to know what you are looking at. Otherwise you will compare numbers that do not belong in the same conversation.

The salary figures on this page come from CareerOneStop's salary finder for Software Developers, occupation code 15-1252. CareerOneStop states that its salary information comes from the U.S. Department of Labor's Bureau of Labor Statistics Occupational Employment and Wage Statistics program and that the wage information on the software developer profile uses the May 2024 estimates. The state values shown here are median annual pay, not entry-level pay, and not top-end compensation from elite public companies.

That distinction matters. Median pay tells you what the middle of the market looks like. It is a better baseline than a cherry-picked total compensation screenshot from a handful of FAANG offers. It also means these numbers are useful to a broad range of developers, not just the top 1% of candidates interviewing for staff-level roles at hyperscalers.

I am also using the Bureau of Economic Analysis regional price parity data for 2024. BEA measures how state price levels compare with the national average. A regional price parity of 110 means the state's prices are about 10% above the national average. A value of 87 means prices are about 13% below it.

That lets us answer a much better question than the usual headline question. Not just where is salary highest, but where does software engineer pay go furthest after local prices are considered.

One more thing. This page is intentionally focused on the broad software developer occupation, not just one niche like backend engineers, machine learning engineers, or mobile developers. If you work in a very specialized slice of the market, your actual pay may run above or below these medians. That is normal. Think of this as the map, not your exact GPS pin.

The national median annual salary in the CareerOneStop table is $133,080. That is already a strong number by any reasonable standard. It is one reason software engineering keeps pulling ambitious people into the field even when the hiring market gets noisy.

But the national figure hides a very wide spread. California sits at $170,910, which is $37,830 above the national median. Washington is close behind at $166,910, and New York lands at $161,260. That is the familiar picture most developers expect to see. Big tech ecosystems, dense concentration of employers, expensive labor markets, and salaries that reflect all of it.

At the other end, South Dakota shows a median of $87,770, Mississippi comes in at $86,460, and Arkansas lands at $96,820. Those are not tiny differences. California's median is nearly double Mississippi's.

That is why state salary content can be useful. It makes the spread visible. But if you stop here, you still do not know enough to make a smart decision.

High salary states often come with higher housing costs, higher taxes, or both. Lower salary states often come with smaller job markets, fewer top-tier employers, or slower career ladders. The number alone cannot tell you whether a move is smart. It can only tell you what the market is paying at the median.

That is also why developers get trapped by bad thinking. They see California at the top, then assume California is automatically the best place to build wealth. Sometimes it is. Sometimes it absolutely is not. If your rent doubles while your salary goes up 25%, you did not really win. You just upgraded your stress.

The job market is still attractive overall, though. The BLS Occupational Outlook Handbook says employment for software developers, quality assurance analysts, and testers is projected to grow 15% from 2024 to 2034. So this is not a dead market. It is a market where location still changes the economics more than most people realize.

Let us start with the states that win the nominal salary race. These are the places where the raw median pay is highest. If you are targeting pure salary ceiling, this is the first table you care about.

Nothing here is shocking, and that is useful in itself. California and Washington still dominate because the market is dense with large employers willing to pay for expensive software problems. New York and Massachusetts stay near the top because finance, enterprise software, health tech, and high-cost metro ecosystems keep compensation elevated.

What is more interesting is the second tier. Maryland, Virginia, Delaware, and the District of Columbia do not always get the same attention in developer salary conversations, but the numbers say they belong in the serious-money category. If you care about high median pay without defaulting to the obvious West Coast story, that corridor deserves a hard look.

There is also a lesson here for remote workers. If your employer benchmarks against California, Washington, or New York, you are likely playing in the premium end of the compensation market even if you do not physically live in those states. That can be a huge advantage if you structure your life well.

Now for the states at the bottom of the table. This is where people usually make the opposite mistake. They see a lower nominal salary and assume the state is automatically a poor choice. That can be just as wrong as blindly worshipping the high-pay states.

The states at the bottom of the nominal table are not necessarily bad places to live or even bad places to build a career. They are just weaker on raw pay.

That can reflect smaller local tech ecosystems, fewer giant employers, less competition for senior talent, and a lower local cost base. If you need dense networking, rapid job switching, or elite-company option value, these states are often weaker bets. If you value lower housing costs, a lower burn rate, and a remote-friendly life structure, some of them become more interesting.

In other words, low salary is a warning flag, not a final verdict. The right question is whether the lower salary is offset by lower living costs or matched by a remote compensation strategy that lets you import a higher-paying market into a cheaper state.

This is where the salary story gets useful.

The Bureau of Economic Analysis says California had a 2024 regional price parity of 110.7. Hawaii was at 110.0. New Jersey was at 108.8. At the low-cost end, Arkansas was at 86.9, Mississippi at 87.0, and Iowa and Oklahoma both at 87.8.

If you divide a state's median salary by its regional price parity index, you get a rough spending-power comparison. It is not perfect, but it is far more honest than pretending every dollar buys the same amount of life in every state.

This is the punchline a lot of developers need to hear. California is still strong after adjustment. It does not magically become a bad market. But the gap shrinks. A state like Iowa can end up looking better than New Jersey on a rough spending-power basis even though Iowa's nominal median is much lower.

That is a big deal. It means developers should stop treating salary rankings as a one-column sport. Once prices enter the picture, some states that look average become quietly excellent for wealth-building, especially if you are remote, dual-income, or optimizing for savings rate rather than status.

This is also why Hawaii looks rough in salary discussions. The nominal median is decent at $119,880, but the price level is so high that the cost-adjusted picture gets weaker fast. Lifestyle can still make it worth it for some people, but the raw economics are not doing you favors.

Here is the full median annual pay table for all 50 states plus the District of Columbia. If you just want the raw state-by-state comparison in one place, this is the part you will bookmark.

If you scan this full list, a few patterns stand out. First, the middle of the country is not uniformly cheap and low-paid. States like Texas, North Carolina, Georgia, Illinois, Utah, Arizona, and Minnesota all sit in a healthy middle-to-upper band. Second, some small-state markets hold up surprisingly well. New Hampshire, Delaware, and Vermont are not giant software markets, but their median pay is absolutely respectable.

The other pattern is that the national middle is stronger than social media makes it sound. There is a huge difference between a weak local developer market and a weak developer career. Many states with six-figure medians still offer very solid economics if your expectations are realistic and your skills are strong.

This is the part that matters more than the ranking tables.

If you are early in your career, state salary data should influence you, but it should not dominate your life choices. Your first job is more about building skill density, shipping experience, and a credible resume than perfectly optimizing geography. A fast-growth environment in a middling-pay state can still beat a weak opportunity in a higher-pay market.

If you are mid-career, the equation changes. You probably have enough leverage for geography to matter more. At that point, the smartest play is often one of three options.

• Work in a premium market if you want the highest upside, denser networks, and more opportunities to jump companies.
• Live in a lower-cost market with remote compensation if you want to maximize savings rate and quality of life.
• Use high-pay-state data as negotiation leverage even when you are not moving there, especially if your work competes in a national talent market.

If you are senior, this table becomes a filtering tool. You are no longer just asking where salaries are high. You are asking where your specific specialty gets paid well enough to justify the local tradeoffs. A distributed-systems engineer, security engineer, machine learning engineer, or staff-level backend developer can often outperform the median so dramatically that the broad state number becomes just the floor of the conversation.

There is also a psychological trap to avoid. A lot of developers assume moving to the highest-paying state is automatically ambitious. Sometimes it is. Sometimes it is just expensive conformity. Ambition is not about moving to the loudest market. It is about putting yourself in the best position to build skills, income, options, and a life you actually want.

That is why I like cost-adjusted salary analysis. It forces you to think like an adult instead of a headline addict. Salary is part of the game. Lifestyle burn, savings rate, taxes, commute, opportunity density, and burnout risk are part of the game too.

The right answer depends on your career stage, your family situation, your appetite for risk, and whether you are optimizing for cash now or long-term upside later. But whatever your answer is, this data gives you a much better starting point than the usual lazy salary list.

There is another practical use for this table that developers often overlook. It gives you a reality anchor for negotiations. If you are interviewing for a job in Virginia, Colorado, Texas, or North Carolina, you now have a market frame that is more grounded than whatever random number a recruiter throws out first. You may not get the exact state median, especially if you are junior or switching stacks, but you can see whether an offer is landing in the right neighborhood or whether someone is trying to underprice you.

It also helps you separate good remote offers from fake-good remote offers. A company paying national-market rates can look generous if you live in a low-cost state. The same company can look mediocre if it expects you to sit in San Francisco or New York while pretending cost of living is irrelevant. Remote work did not erase geography. It just changed who gets to arbitrage it.

If I were using this page for an actual career decision, I would not ask a single yes-or-no question like, "Should I move to California?" I would ask a tighter set of questions. Which states have enough opportunity density for my specialty? Which ones fit the life I want outside work? Which ones let me keep more of what I earn? And which ones give me enough optionality that I am not trapped if the current employer goes sideways?

That last point matters a lot. Salary is not the only economic variable. Optionality is economic power too. A place with five serious employers can be worth more than a place with one, even if the one employer pays slightly above median. Your leverage in the next negotiation depends on having alternatives.

So use this table the way a smart developer uses any metric. Not as a decision made for you, but as a constraint, a signal, and a tool for sharper thinking. The people who get the most out of salary data are not the ones who memorize the ranking. They are the ones who combine it with strategy.

And one more thing. Do not confuse state medians with your ceiling. Great developers can outperform the market almost anywhere. If you build scarce skills, communicate well, and work on expensive problems, you can create your own local market instead of passively accepting the average one. The median is useful because it shows the baseline. Your job is to build enough leverage that baseline numbers become context, not destiny.

• CareerOneStop Salary Finder, Software Developers, state and national median wage table, accessed April 2026. CareerOneStop states its salary information comes from the U.S. Department of Labor's Bureau of Labor Statistics Occupational Employment and Wage Statistics program, using May 2024 wage estimates.
• CareerOneStop Occupation Profile, Software Developers, source note stating wage information uses the Bureau of Labor Statistics Occupational Employment and Wage Statistics May 2024 estimates.
• U.S. Bureau of Economic Analysis, Regional Price Parities by State and Metro Area, 2024 release published February 19, 2026.
• U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Software Developers, Quality Assurance Analysts, and Testers, showing projected 15% employment growth from 2024 to 2034.

If you want broader compensation context, also see our Software Developer Salary Statistics, Programming Language Salary Statistics, and Remote Work Statistics for Developers.