What Your Salary Says About Your City's Economy

In January, a recruiter in Columbus posted the same software-engineering role twice: once for her own office, once for a client in San Jose. The duties were identical and so was the seniority; the posted ranges were not. Neither hiring manager blinked at a gap of more than $50,000, because pay has been a local number for as long as anyone has measured it, and the distances between metros have only grown.

The Bureau of Labor Statistics' metropolitan wage survey, published every spring, finds the same occupation paying 40 percent more in one metro than in another. Among large metros, the gap between the highest and lowest median wages is about $49,000 a year: San Jose-Sunnyvale-Santa Clara sits near $89,000, while McAllen, Texas, hovers around $40,000. Cleveland, Detroit, and Pittsburgh occupy the middle, where a solid wage buys more than the number suggests.

This article explains how that map is drawn, why a software engineer's pay can differ by tens of thousands of dollars between two cities 200 miles apart, and what the data mean for remote workers who can now choose a metro before they choose a job.

The data behind the map

The map starts with the Occupational Employment and Wage Statistics program, a survey the Bureau of Labor Statistics runs with state workforce agencies. Each year it samples roughly 200,000 establishments and estimates employment and pay for about 800 occupations in nearly 380 metropolitan areas — every place with at least 50,000 people and a recognizable economy. The results, released each spring, are the closest thing the country has to a wage census.

Two technical details matter. The survey reports median wages, not averages, so a handful of seven-figure executives cannot distort a city's number. And "metro" means something precise: a core city plus the surrounding counties that share its labor market, as defined by the Office of Management and Budget. San Francisco's metro includes Oakland and Berkeley; Washington's reaches into Virginia and Maryland.

Read with care, the numbers separate two things that are easy to confuse. A metro's wage level — the median across all jobs — tells you about its economy. Its occupational wages, occupation by occupation, tell you what a particular skill is worth in that market. The two often move together, but not always, and the difference is where the interesting stories hide.

The national median, for scale, was about $48,060 in May 2024, the most recent full release at the time of writing, and roughly a third of metros sit above it. The program also publishes the data by state and by industry, so a worker can compare not just cities but the industries within them. None of it is hard to read; the tables sort by occupation and by area. The methodology page explains how the figures on this site are compiled from the same sources.

The premium metros

At the top of the map sit a small group of metros where pay runs far ahead of the national median of roughly $48,000. The list is stable and familiar: San Jose, San Francisco, Seattle, New York, and Washington. What distinguishes them is not size but industry. Each is home to a cluster of high-productivity employers — software, finance, biotech, professional services — that compete for a limited supply of talent and bid wages up.

Median annual wage for all occupations, May 2024 estimates, and 2023 regional price parity (U.S. average = 100). Sources: BLS Occupational Employment and Wage Statistics; BEA regional price parities.

Metro	Median annual wage, all occupations	Regional price parity
San Jose-Sunnyvale-Santa Clara	about $89,000	120.4
San Francisco-Oakland	about $81,000	117.5
Seattle-Tacoma-Bellevue	about $76,000	110.9
New York-Newark-Jersey City	about $73,000	115.1
Cleveland-Elyria	about $49,000	91.2
Detroit-Warren-Dearborn	about $51,000	96.1

The same table, read with price data attached, is more complicated than it looks. The Bureau of Economic Analysis publishes regional price parities — an index of what a standard basket of goods and services costs in each metro, with the national average set at 100. San Jose's parity of about 120 means goods and services run roughly 20 percent above the national average, and housing runs far above that. Cleveland's parity near 91 means the same basket costs about 9 percent less.

The concentration is extreme at the top. In San Jose, roughly 1 in 5 workers is employed in a computer or mathematical occupation, and the median wage for those jobs exceeds $140,000. In the national economy the share is closer to 1 in 25. A metro's median wage is in large part an arithmetic product of that mix — which is why the same company can pay a $130,000 salary in one of its offices and an $80,000 salary in another without anyone calling it unfair.

What prices do to the premium

Put the two columns together and the premium shrinks in real terms. A $90,000 salary in San Jose buys what roughly $68,000 buys in Cleveland, once prices are adjusted. The reverse is also true: a Cleveland salary moved to San Jose without adjustment loses about a quarter of its purchasing power. This is why economists say wage gaps are partly real and partly an accounting of what it costs to live where the jobs are.

"A metro's wage is mostly a statement about its industries, not about how hard people work," said a regional labor economist who has studied metro pay data for two decades and asked not to be identified. "Put the same accountant in San Jose and in Columbus and the San Jose version will be paid more, because the firms around her are richer and need her more."

The economist's point is visible in the day-to-day numbers. A two-bedroom apartment in San Jose rents for a median of more than $3,000 a month; the same apartment in Cleveland rents for about $1,300. Groceries differ less — the federal data put food costs maybe 10 percent higher in the expensive metros — but housing alone is enough to reorder the comparison. This is why the Census Bureau's real median household income numbers, adjusted for regional prices, show a much flatter country than the raw wage tables do.

The steady middle

Below the premium metros sits a broad middle band where wages are ordinary by national standards but prices are lower, and the combination produces a comfortable life. Cleveland, Detroit, Pittsburgh, St. Louis, and Milwaukee pay median wages in the high $40,000s to low $50,000s. Their economies are older — manufacturing, health care, higher education, logistics — and their employers are less likely to be bidding against the world for talent.

The stability shows up in the data as a narrower spread between occupations. In Cleveland, a nurse, an electrician, and an office manager earn within a band of roughly $20,000; in San Jose the same three roles can span $60,000. Union density is part of it — Detroit's auto plants still set a floor under skilled trades pay — and so is the absence of a speculative housing market that forces wages to chase rents.

The practical consequence is that a middle-band city can beat a premium city for a worker with an ordinary occupation. An accountant earning $75,000 in Cleveland keeps more after housing and taxes than one earning $95,000 in San Francisco, once the price parity adjustment is applied. Plenty of families have figured this out; the metros with the fastest recent growth in working-age population are mid-priced places with good hospitals and schools.

Same job, different number

Occupation-level data make the point most sharply. The Bureau of Labor Statistics publishes wages for about 800 occupations in every metro, and the same title can sit at opposite ends of the country's pay scale. Registered nurses in the San Francisco metro earn a median above $160,000, among the highest in the nation; in a mid-size Southern city the median for the same license is about $75,000. Software developers show an even wider range, from roughly $90,000 in some Rust Belt metros to more than $180,000 in San Jose.

None of this is a secret to employers, which is why a growing share of job postings carry location-specific ranges. Pay transparency laws in California, Colorado, New York, and Washington require many employers to post them, and the posted numbers have made the geography of pay visible to workers who once had to guess. A recruiter in Austin who has placed candidates in nine states said the range on a posting is now routinely the first thing a candidate asks about — and the second is whether the range moves with the zip code.

The comparison shopping cuts both ways. A worker in a low-wage metro who can do the job remotely has a strong incentive to point to the high-metro range; an employer with a national footprint has an equally strong incentive to pay the local rate. The outcome of that negotiation is one of the liveliest questions in the current labor market.

The 40 percent figure from the Bureau's data is an average across all occupations, which hides the extremes. For some jobs the gap approaches 2 to 1. A customer-service representative in a call-center metro might earn $38,000 while the same role in a financial district pays $62,000. A high-school teacher, by contrast, shows a much flatter curve — teaching pay is set by local budgets rather than global markets, which is why teachers in high-cost metros struggle with housing that their wages were never designed to reach.

What actually drives the differences

Economists who study the map tend to land on the same short list of causes. Industry mix comes first: a metro full of firms that sell to the whole country or the world, like software and finance, pays more than one full of firms that sell only to local customers, like restaurants and salons. Productivity follows. When workers in a metro produce more per hour — because of better technology, denser clusters of expertise, or simply more capital behind each desk — employers can afford to pay more, and competition for those workers forces them to.

Cost of living is on the list, but as a follower rather than a leader. Wages rise first in a booming metro; rents and prices rise afterward, as workers move in and landlords raise prices to match the new incomes. The University of California economist Enrico Moretti made this argument in his 2012 book on the geography of jobs, and the pattern has repeated since: the metros that gained the most in wages during the 2021–2023 boom were also the ones where housing costs rose fastest.

Three smaller forces matter too. State policy sets a floor: the metros with the highest minimum wages and the strongest overtime rules tend to have higher wages at the bottom of the distribution. Unions compress the middle. And amenities — weather, universities, transit, culture — pull in workers who might otherwise cost less, which is part of why sun-belt metros can pay below the national median and still fill jobs.

The pandemic added a wrinkle. When remote work exploded in 2020, some economists predicted rapid convergence — wages in low-cost metros rising toward the national level as employers hired from anywhere. It happened, but slowly and unevenly. The metros that gained the most remote workers in 2021 and 2022, from Boise to Nashville, did see wage growth above the national average, and the premium metros kept their lead. Convergence, such as it is, has come from the middle rising, not the top falling.

What it means for remote workers

For remote workers, the map is now a menu. In 2021 and 2022, a wave of companies tried "pay by zip code" — adjusting salaries to the worker's location, sometimes cutting pay for anyone who left a high-cost metro. By 2024 the pendulum had swung partway back. Some large employers moved to location-agnostic pay bands, arguing that a remote worker's output does not change with their address; others kept discounts but narrowed them.

The stakes are visible in survey data. Remote-work platforms report that a majority of remote job postings still list a salary range, and that the ranges increasingly say "national" rather than naming a city. Meanwhile, pay-transparency laws are spreading, and several of the new state rules require employers to disclose whether a range depends on location. The direction of travel is toward more disclosure and less geographic arbitrage — though the discounts have not disappeared.

For a worker choosing where to live, the arithmetic has three parts. Start with the offered salary, then adjust it with the price parity for the metro in question, then subtract the difference in state and local taxes — a factor that can be worth several percent of pay. The salary inflation calculator can convert an old salary into its current-dollar equivalent, and the salary calculators on this site apply the same logic in reverse, turning a number from one city into the number that keeps your purchasing power intact in another.

The fine print of moving

State income taxes vary from zero in Texas and Florida to more than 13 percent in California, and the local housing market can swallow or amplify whatever the tax code leaves alone. A remote worker who keeps a San Francisco salary while living in Boise is capturing the difference; one who accepts a Boise salary while paying San Francisco rent is subsidizing the employer. The data let you know which one you are.

Taxes add a layer of fine print. Most states tax income where the work is performed, so a New Yorker who moves to Florida but keeps working for a New York employer can still owe New York tax under the state's convenience-of-the-employer rule. A handful of states have reciprocity agreements that let commuters file in one state only. The details are exactly the kind of thing that changes a year-end refund by thousands of dollars, and they are worth checking before the moving van, not after.

The good news is that the tools for this arithmetic are cheap. State tax calculators are free, the Bureau's price parities are public, and the Census publishes adjusted income by metro. Ten minutes with those three sources will tell you, within a few thousand dollars, what a move actually does to your standard of living — which is more precision than most salary negotiations ever get.

How to use the map

The practical questions are answerable in an afternoon. To price an offer in a new metro, look up the occupation's median wage in both cities on the Bureau of Labor Statistics' Occupational Employment and Wage Statistics page, then apply the Bureau of Economic Analysis price parity for each. To value a raise against local inflation, the inflation calculator does the conversion in one step. To compare offers with different structures, convert everything to annual cash equivalents first; the salary converter and the overtime calculator handle the hourly-to-annual math.

The same exercise, repeated once a year, becomes a habit with a payoff:

• Check your metro's median wage against the national median; a metro that falls is a signal, not a verdict.
• Check your occupation's local median, not the national one, before you negotiate.
• Re-price your salary when you move, even within the same company.
• Watch the state laws; a transparency rule in your state changes what you can ask.

What to watch in the next few years: whether the premium metros keep their lead or the middle band catches up as remote work lets high-cost employers hire anywhere; whether the remaining location discounts quietly disappear, as several large employers have signaled; and whether the Bureau's data — already the best in the world at this scale — gain an annual update on remote pay. The map will change. Your salary is a data point on it, and unlike the weather, the map is published, free, and legible to anyone who spends an afternoon with it. The cities that pay more will keep charging more for the privilege of living in them, and the cities that pay less will keep proving that the number alone is not the whole story. Read the data once, and the difference between the two stops being a mystery and becomes a choice.