Developer salary ranges by city
RoleWeek lists 5,587 developer roles posted Oct 20–27, 2026. 3,919 of them (70%) list a salary. These pages show what those employers posted: for 34 cities and remote roles and 99 role types within them, the median and middle half of the posted yearly ranges, with the roles behind them.
They are employers’ posted ranges, not offers, not what people are paid and not a market average. A page exists only when 15 or more roles list a yearly range. Data as of .
By city
| City | Roles with a yearly range | Median bottom | Median top |
|---|---|---|---|
| Remote (US or Canada) | 637 | $133K | $190K |
| San Francisco Bay Area | 609 | $175K | $250K |
| Washington DC | 583 | $120K | $190K |
| New York | 481 | $156K | $215K |
| Elsewhere in the US & Canada | 432 | $96K | $146K |
| Seattle | 301 | $145K | $215K |
| Boston | 225 | $130K | $200K |
| Los Angeles | 213 | $134K | $200K |
| Dallas-Fort Worth | 191 | $110K | $189K |
| Denver-Boulder | 165 | $114K | $190K |
| Chicago | 164 | $115K | $187K |
| Toronto | 150 | CA$103K | CA$144K |
| Austin | 126 | $135K | $203K |
| Atlanta | 107 | $112K | $190K |
| Philadelphia | 89 | $114K | $200K |
| Minneapolis-St. Paul | 80 | $110K | $176K |
| Phoenix | 80 | $108K | $199K |
| San Diego | 74 | $126K | $202K |
| St. Louis | 65 | $105K | $198K |
| Tampa | 63 | $103K | $170K |
| Charlotte | 62 | $115K | $201K |
| Raleigh-Durham | 61 | $122K | $200K |
| Columbus | 57 | $111K | $190K |
| Detroit | 53 | $110K | $193K |
| Houston | 51 | $103K | $202K |
| Nashville | 47 | $110K | $202K |
| Miami | 46 | $120K | $202K |
| Hampton Roads | 45 | $92K | $127K |
| Portland | 45 | $132K | $205K |
| Salt Lake City | 44 | $107K | $186K |
| Huntsville | 42 | $106K | $162K |
| Pittsburgh | 42 | $113K | $202K |
| Colorado Springs | 41 | $113K | $170K |
| Vancouver | 34 | CA$114K | CA$140K |
| Dayton | 28 | $111K | $170K |
Amounts are in the currency the role lists: CA$ for the Canadian cities, $ for the rest. Cities are in order of roles that list a yearly range.
City by role type
| City | Software Engineering | Backend | Full-Stack | Data | Machine Learning & AI | DevOps & SRE | Security | QA & Testing | Embedded & Firmware | IT & Infrastructure |
|---|---|---|---|---|---|---|---|---|---|---|
| Remote | 184 | 17 | 20 | 82 | 80 | 59 | 96 | 23 | · | 54 |
| San Francisco Bay Area | 242 | 24 | · | 55 | 124 | 39 | 50 | · | 25 | 16 |
| Washington DC | 142 | · | 32 | 68 | 44 | 45 | 107 | 15 | · | 104 |
| New York | 165 | · | 24 | 70 | 74 | 37 | 49 | · | · | 29 |
| Elsewhere in the US & Canada | 138 | · | 19 | 39 | 22 | 23 | 51 | 16 | · | 100 |
| Seattle | 131 | · | · | 39 | 38 | 23 | 32 | · | · | · |
| Boston | 77 | · | · | 38 | 39 | · | 24 | · | · | · |
| Los Angeles | 69 | · | · | 25 | 23 | · | 28 | · | · | 27 |
| Dallas-Fort Worth | 63 | · | · | 24 | 28 | · | 27 | · | · | · |
| Denver-Boulder | 50 | · | · | 19 | 18 | · | 27 | · | · | 21 |
| Chicago | 49 | · | · | 43 | 18 | · | 19 | · | · | 15 |
| Toronto | 48 | · | · | 15 | 24 | · | 15 | · | · | 15 |
| Austin | 37 | · | · | 19 | 21 | · | 24 | · | · | · |
| Atlanta | 35 | · | · | 20 | 15 | · | · | · | · | · |
| Philadelphia | 27 | · | · | 17 | · | · | · | · | · | · |
| Minneapolis-St. Paul | 28 | · | · | 15 | · | · | · | · | · | · |
| Phoenix | 27 | · | · | 16 | · | · | · | · | · | · |
| San Diego | 21 | · | · | 15 | · | · | · | · | · | · |
| St. Louis | 22 | · | · | · | · | · | · | · | · | · |
| Tampa | 15 | · | · | 18 | · | · | · | · | · | · |
| Charlotte | 18 | · | · | 16 | · | · | · | · | · | · |
| Raleigh-Durham | 18 | · | · | · | · | · | · | · | · | · |
| Columbus | · | · | · | · | · | · | · | · | · | · |
| Detroit | 15 | · | · | · | · | · | · | · | · | · |
| Houston | · | · | · | 15 | · | · | · | · | · | · |
| Nashville | · | · | · | · | · | · | · | · | · | · |
| Miami | · | · | · | · | · | · | · | · | · | · |
| Hampton Roads | · | · | · | · | · | · | · | · | · | · |
| Portland | · | · | · | · | · | · | · | · | · | · |
| Salt Lake City | 17 | · | · | · | · | · | · | · | · | · |
| Huntsville | 16 | · | · | · | · | · | · | · | · | · |
| Pittsburgh | · | · | · | · | · | · | · | · | · | · |
| Colorado Springs | 16 | · | · | · | · | · | · | · | · | · |
| Vancouver | · | · | · | · | · | · | · | · | · | · |
| Dayton | · | · | · | · | · | · | · | · | · | · |
Roles that list a yearly range, per page. A dot means the city has fewer than 15 for that role type, or repeats the city page.
How these numbers are made
- Source: the yearly salary ranges employers publish in their own job postings, for roles RoleWeek lists as posted in the last 7 days. They are what employers advertise, not offers, not what people are paid, and not a market average. RoleWeek lists a share of all developer roles, and an employer decides whether to post a range at all.
- One role is one card: an opening listed for several places counts once on a page. A role listed in several cities counts on each city’s page.
- Bottom and top of each posted range are summarised separately: the median, and the 25th and 75th percentiles (half of the roles fall between them). A role that posts a single figure counts as both its bottom and its top.
- Yearly ranges only, in one currency per page: CA$ for the Canadian cities, $ for US cities and remote roles. Pay by the hour, day, week or month is never converted or mixed in.
- A page exists only when 15 or more roles list a yearly range; a level gets a row at 10. The numbers are rebuilt every day from the roles posted in the last 7 days.