How to compare software developer salaries across countries
How to read software developer salary pages without mixing countries, regions, currencies, years or salary definitions.
Start with country and year
Software developer is one of the clearest examples of why salary comparison needs context. A national salary row, a state salary row and a city salary row can all describe software work, but they should not be read as the same market. The same is true for salary year: a 2025 value should not be mixed with an older source unless the page is explicitly showing a trend.
World Career Atlas keeps country, region, source year and local title attached to each salary row. That makes it possible to compare Norway, the United States, Germany or the United Kingdom while still seeing which values came from national releases, state-level data or other official tables.
Use salary metric labels
Some sources publish averages, some publish medians, and others publish quartiles or deciles. For software developer roles, the difference can be large because seniority, sector and location can stretch the upper end of the salary distribution.
When comparing across countries, median values are often easier to read than averages because very high salaries can pull averages upward. If the median is missing, the average can still be useful, but it should be labelled clearly and compared with caution.