How Much Does a Developer Cost Per Hour in the UK vs the US?

A software developer costs a UK employer between $44.27 and $66.84 per productive hour, and a US employer between $101.68 and $147.73 — once payroll tax, pension, insurance and paid leave are added and divided by the hours you actually get. The two ranges do not overlap. London, the most expensive region in Britain at $66.84, costs 66% of Houston, the cheapest major US metro at $101.68.

Every "how much does a developer cost" article quotes a salary, usually sourced from recruiter marketing. A salary is the smallest component of the answer and the only one anyone publishes.

What an employer actually spends is the salary plus payroll tax, pension, insurance and supplemental pay — and what it buys is not a year, because a meaningful share of the paid year is leave. The number that matters is total employer cost divided by productive hours, and it is not in any recruiter's report.

So we built it from wage microdata: 15 US metropolitan areas from the BLS Occupational Employment and Wage Statistics, 11 UK regions from the ONS Annual Survey of Hours and Earnings, loaded with the measured on-costs for each country. The full dataset is available as CSV.

The two countries do not overlap

This is the finding, and it was not the expected one. Not "the UK is somewhat cheaper on average." There is no region of Britain as expensive as the cheapest large American metro, and no American metro as cheap as the most expensive British region.

The internal spreads are almost identical — 1.45x across US metros, 1.51x across UK regions. Geography prices developers about as unevenly in both countries. The countries themselves are simply on different shelves.

American employment costs more, not less

The assumption we started with, and the one most people carry, is that European employment is the expensive one — heavy social contributions, long statutory leave, difficult dismissal. On the cost side that is the wrong way round.

The US figure is not an estimate. It is the ratio the BLS itself measures: $32.60 in wages and $14.01 in benefits per hour worked across private industry, first quarter of 2026. Employer-paid health insurance is most of the gap, and it has no British equivalent.

A detail that falls out of the arithmetic and runs against intuition: a UK developer's on-cost percentage goes down as their salary goes up. The 3% pension minimum is charged only on qualifying earnings between £6,240 and £50,270, so a developer earning well above the cap attracts proportionally less. London's on-costs are 15.7%; Wales' are 16.1%.

What this does and does not tell you about hiring offshore

The obvious use of a table like this is to argue that a cheaper rate elsewhere wins. It is worth being precise about what that argument actually requires, because the naive version of it is wrong.

An external rate is never the whole cost. Someone internal specifies the work, reviews it, and carries the context — and that person's time is charged at the loaded rates above. So the honest question is not "is the rate lower" but "how much internal time can the arrangement consume before the saving is gone?"

That has a clean answer. If an external rate is A and the in-house cost is C, the advantage disappears when internal management time reaches a fraction f = 1 − A/C of a full-time equivalent:

Read the table honestly and it cuts both ways. Against a San Francisco team, a $40/hr arrangement can absorb an enormous amount of management overhead and still win. Against London, a $60/hr arrangement is gone at ten per cent — barely half a day a week of someone's attention — and at $80/hr it is already more expensive than hiring.

The variable that decides it is not the rate. It is how much internal time the work consumes, which is a function of how well the scope is specified and how much context has to be transferred.

Method

• US wages: BLS Occupational Employment and Wage Statistics, 2025, occupation 15-1252 (Software Developers), 15 metropolitan areas plus national. 144 series requested, all returned data.
• US on-costs: BLS Employer Costs for Employee Compensation, 2026 Q1, private industry — $32.60 wages and $14.01 benefits per hour worked, a 43.0% load. Using ECEC avoids assembling a stack of assumptions about insurance and retirement.
• UK wages: ONS Annual Survey of Hours and Earnings 2025 provisional, Table 14 (national) and Table 15 (region), SOC 2020 code 2134, gross hourly pay, full-time.
• UK on-costs: employer National Insurance at 15% above the £5,000 secondary threshold for 2026-27, plus the 3% auto-enrolment pension minimum on qualifying earnings of £6,240–£50,270.
• Productive hours: US 1,872 (2,080 paid less 26 days' leave); UK 1,740 (1,950 paid less 28 days' statutory leave). The employer buys the paid year and uses part of it.
• Conversion at $1.27 to the pound. The UK figures stand on their own in sterling in the dataset.

Limitations

These are means, not offers. OEWS and ASHE describe the existing employed population, which skews toward established staff. A hiring manager competing for a specific senior candidate in a specific month will not pay the mean.

The UK figure is a statutory floor. There is no British equivalent of ECEC, so we used the minimum legal on-costs. Many UK employers pay above the pension minimum or offer private medical cover, both of which would narrow the transatlantic gap. The direction of that error is known: we are understating UK cost, not overstating it.

Leave assumptions differ by design. The UK figure uses the statutory 28 days; the US figure uses a typical 26 days of holidays and PTO, because the US has no statutory minimum at all. That is a real difference between the countries rather than a modelling choice, but it does move the per-hour numbers.

One cell is missing: ONS suppresses web developer figures for some regions, and BLS suppressed web developer wages for Miami. Software developers are complete for every location shown.

A note on how hard this was to read

This is public data that the public cannot easily get. `bls.gov` and `download.bls.gov` return HTTP 403 to any scripted request — which is very likely why the developer-cost articles all quote recruiter marketing instead of the wage statistics. The API at `api.bls.gov` serves the same OEWS series, metro level included, with no key required.

The ONS side is open but awkward: the current tables still live under a URL containing `soc2010` while carrying SOC 2020 codes, and each release is a zip of twenty-odd workbooks with the useful sheet named for an employee subgroup. None of this is secret. It is just tedious enough that almost nobody does it.

If you are making this decision

The number to carry out of this is not a rate. It is that the comparison is decided by specification quality, not by geography. Work that is well-scoped survives being done anywhere; work that requires constant clarification consumes internal time at $100 or more an hour, and that meter runs whichever side of the Atlantic the developer sits on.

Which makes it worth being honest about the shape of the work before choosing who does it. A defined build with a clear boundary is a different proposition from an open-ended stream of changes, and it is the kind of thing worth settling at the start of a custom software engagement rather than discovering three months in.