Between April and September 2026 we recorded 3,646 remote software engineer postings. 1,873 of them, 51.4%, said what the job pays. This is what those postings say.
The short answer
| Annual, USD | |
|---|---|
| 25th percentile | $126,108 |
| Median | $170,000 |
| 75th percentile | $202,500 |
Half of all remote software engineer postings that name a figure sit between $126,108 and $202,500. That is a wide middle, and almost all of the width is explained by two things: where the company will let you live, and which word it put in the job title.
Neither of those is a skill.
Where you live
| Location the role is tied to | Postings with pay | Median |
|---|---|---|
| United States | 939 | $192,510 |
| Anywhere | 226 | $176,450 |
| Canada | 208 | $139,503 |
| United Kingdom | 44 | $128,182 |
| Spain | 44 | $98,590 |
| Poland | 34 | $75,600 |
A US-only remote software engineer role advertises 2.5 times what a Poland-only one does. $192,510 against $75,600, for the same job title, done over the same connection, usually with the same stack.
The row I find most interesting is the second one. Roles open to applicants anywhere pay $176,450 at the median, which is 92% of the US figure and well above every single-country market outside it. Companies that refuse to care where you live are not using that freedom to pay less. They are paying close to American rates and hiring from everywhere.
The UK, Spain and Poland rows rest on 44, 44 and 34 postings. That is enough to show the shape and not enough to quote to two decimal places.
Seniority
| Level | Postings with pay | Median |
|---|---|---|
| Junior / entry level | 25 | $47,840 |
| Mid-level | 506 | $146,048 |
| Senior | 828 | $170,000 |
| Lead and above | 514 | $210,000 |
The ladder is worth $23,952 from mid to senior and $40,000 from senior to lead. That is the reverse of the usual advice that the big jump is into senior: in what gets advertised, the money accelerates after it.
Ignore the junior row. Twenty-five postings over six months is not a market, it is a rounding error, and it says more about how few entry-level remote engineering jobs exist than about what they pay. Our September report found junior roles at 2.4% of all remote postings, which is the same story from the other direction.
Note also that senior is the largest group at 828 postings. The median remote software engineering job being advertised is a senior one.
The title is worth more than most skills
This is the finding I did not expect to be this large.
| Title the posting uses | Postings with pay | Median | States a salary |
|---|---|---|---|
| Software Engineer | 1,873 | $170,000 | 51.4% |
| Software Developer | 102 | $118,250 | 21.7% |
| Developer | 938 | $81,034 | 20.1% |
A posting that says "software engineer" advertises 2.1 times one that says "developer". It is also two and a half times as likely to tell you the number at all.
I want to be careful here, because this one has a real confound. These are text matches on the job title, so "developer" also catches business developer, developer advocate and developer relations, and it skews toward markets and companies that pay less in general. The gap is not purely linguistic.
But it is not purely compositional either. If you are choosing what to put in your own title, or deciding which search to run, the two words lead to visibly different sets of jobs. Searching one and not the other leaves money on the table.
Specialisations
| Role | Postings with pay | Median | States a salary |
|---|---|---|---|
| Machine Learning Engineer | 161 | $212,750 | 56.1% |
| Platform Engineer | 492 | $182,500 | 54.1% |
| Security Engineer | 332 | $172,750 | 48.8% |
| Software Engineer | 1,873 | $170,000 | 51.4% |
| Data Engineer | 412 | $157,500 | 35.3% |
| Frontend Engineer | 111 | $133,590 | 56.1% |
| Backend Engineer | 567 | $112,420 | 56.0% |
Machine learning engineers top the table at $212,750, $42,750 above a general software engineer. Platform engineering at $182,500 is the quieter surprise: unglamorous infrastructure work pays better than most product engineering on this board.
The backend row needs a warning rather than a conclusion. $112,420 sits below frontend, which is the opposite of what most engineers expect, and its middle half runs from $86,575 all the way to $182,690 — the widest spread in the table. That is not one market. It is at least two, mixed together by a title that is used very differently in different countries, and I would not draw anything from it until we can split it by location.
How often does a remote engineering job even name a number
51.4% for software engineer, against 36.5% across all remote postings in our September report. Engineering is one of the more transparent corners of this market, and roles with a specific specialisation are more transparent still: frontend, backend and machine learning all sit above 54%.
The exceptions are instructive. Data engineer discloses in only 35.3% of postings, and the two "developer" variants in about a fifth. If you are applying to one of those, assume you will be the one who has to raise the subject.
What I make of it
This section is the author's read on the numbers above, and it is the part you should argue with.
The two largest levers in this data are not technical. A US passport or address is worth more than any framework on your CV, and the word in your job title is worth more than most individual skills. Neither of those is a satisfying thing to find in a dataset about engineering.
What I would actually do with this, if I were job hunting: search the title variants separately rather than assuming a search engine treats them as synonyms, and treat the anywhere-roles as their own market rather than a consolation prize. $176,450 at the median and no requirement to live anywhere in particular is the best combination in this table, and it is available in 226 of the postings we measured.
The thing I would not do is read the seniority ladder as a career plan. The money accelerates after senior, but so does the competition: lead and above was 514 postings against 828 senior ones, in a market where our September report found senior and lead roles falling faster than any other level.
Methodology
Figures cover remote job postings gathered by Brenxor with a posting date between 1 April and 30 September 2026, a six-month window chosen so that per-country slices have enough postings to mean something.
Role matching. A role is a full-text match on the job title, not a tagged field, so "software engineer" catches senior software engineer and software engineer II, and "developer" catches titles that are not engineering roles at all. Titles are matched independently, so a posting can appear under more than one role.
Sample gates. A role is published only with 30 or more postings that state a salary, and a slice of one — a seniority band or a country — only with 10 or more. Rows near those floors are shown because they establish shape, not because they are precise.
Salaries are annual USD. Where a posting states a range, we use its midpoint; where it states a single figure, that figure. Ranges outside $10,000–$1,000,000 a year are dropped as parsing errors. Every figure here describes postings that publish a number, which is 51.4% of software engineer postings and as little as 20.1% of developer ones — those employers are not a random sample of all employers, and nothing here should be read as what people are actually paid.
Seniority is detected from the job title. A posting with no detectable level counts as mid-level, so that bucket reads as "mid-level and unstated".
Aggregator boards are excluded, as in every report here: two companies in our database re-post other employers' jobs under their own name.
Counts include postings that have since been filled or closed. This is a record of what was advertised, not of what is open today.