Location bands, and the multi-metro premium

Median midpoint by posted location · snapshot 2026-10-26 · 8,049 postings with a range

2,158San Francisco postings
$249,625their median
380multi-city postings
$345,000their median

Salary ranges in this dataset are attached to a location, and the location field is messier than it looks: "San Francisco" and "San Francisco, CA" are separate strings that mean the same market, while "San Francisco, CA | New York City, NY" is a different thing entirely — a posting that pays one band for several metros.

Posted locationPostingsMedianp25p75
san francisco743$252,500$197,500$337,500
united states328$173,737$138,800$213,750
san francisco, ca188$247,875$185,000$345,000
remote177$156,000$117,600$208,708
new york city160$162,250$120,000$216,000
san francisco, ca | new york city, ny156$347,500$287,500$415,000
remote - usa143$202,482$181,022$237,262
new york, new york, united states136$189,560$142,375$229,770
san francisco, california122$210,938$179,000$261,500

The multi-metro effect is the largest single structure in the location data: postings that list several cities have a median of $345,000 against $195,000 for single-location postings — +77%. This is mostly not a premium for flexibility; it is a marker of seniority. Companies list three metros for the roles they have been trying to fill longest, and those are the senior and staff roles with the widest bands.

Read the location table as pay bands attached to postings, not as local cost of living. A "$252,500 in San Francisco" posting means the company put that band on a San Francisco requisition. It does not mean every San Francisco engineer earns it, and it does not adjust for what the same role pays in Austin — most of these companies publish one national band and let the location list signal where they expect to hire.

Related: role families · remote pay · the dataset.

A longer read: One company, one $75,500 gap between role families on dev.to.