The Glass Wall in Global Tech Pay

Remote work went global. Compensation did not.

Remote work promised a more open market for talent. Geography, at least in theory, would matter less.

What actually emerged was a more selective version of globalization: companies expanded the geography of labor supply while keeping compensation tied to local pricing logic. The work crossed borders. The pay often did not.

That is the glass wall.

It is "glass" because nothing about it looks openly hostile. No one says the quiet part out loud. There is no email that says, "we think your work is worth less because you live in Australia." There is just policy. Benchmarking. Compliance. Employer of Record arrangements. "Local market rates." "Cost of labor."

And yet the outcome can be stark: two people on the same team, solving the same problems for the same company, can be paid on fundamentally different scales because one lives in Australia and the other is based somewhere in the United States.

Consider the following comparison diagram:

How the wall gets built

A US company that wants to hire in Australia usually has three options:

• open a local entity
• use an Employer of Record
• hire through a contractor arrangement

None of those paths are inherently unethical. In fact, they are often operationally sensible. Cross-border employment is real work. Payroll, tax, benefits, and labor law do not disappear just because the team works in Slack and GitHub.

The problem is what these mechanisms make easy.

Once a company has a local payroll wrapper around an international employee, compensation starts to get narrated as a local matter. The company directs the work, sets the bar, evaluates the output, and captures the value globally. But the pay discussion gets pulled back down into local market benchmarks.

Employer of Record structures are especially important here. They solve a real business problem, but they also act like a wage membrane: the work flows through globally, while the pay is filtered through local pricing logic.

In other words, the physical place matters when the place is part of the job. But when the output is the same, the buyer is the same, and the value accrues in the same business, local pay bands start to describe pricing power the company exerts over its current and potential employees more than productive value.

That is the central point. I am not arguing that every company is behaving maliciously. I am arguing that a polite policy can still produce an unfair result.

The case that makes the disparity visible

Lets continue the illustrative example we used at the beginning of this post:

• Melbourne: about A$200,000
• US-based teammate: about US$200,000
• Same company, same team, same class of problems

At a glance, some people will look at those numbers and think they are in the same neighborhood. Next we'll analyze how and why they are not.

Note: This section uses live market rates

1. At market exchange rates, these salaries are nowhere near each other

Using a fallback exchange rate of US$0.7042 per A$1 (A$1.4200 per US$1), A$200k converts to about US$141k.

Against US$200k, that means the US-based teammate is making about 42 percent more in cash salary.

To close that gap on cash alone, the Melbourne salary would need to be closer to A$284k, not A$200k.

2. A rough PPP check still does not rescue the Australian number

Purchasing-power parity, or PPP, is a cost-of-living lens. Instead of asking what currency markets say A$1 is worth, it asks what that money buys locally. The OECD defines PPP as a conversion rate that equalizes the purchasing power of different currencies by accounting for price-level differences between countries. Here I am using the Economist's 2026 Jan Big Mac data as a simple proxy for that idea, not as a formal PPP dataset. .

On that lens, A$200k works out to about US$144k in purchasing-power terms. However, while this is gentler than the market exchange-rate view (i.e. its closer to parity by a few thousand), it still leaves the Australian figure at only about 72 percent of the US$200k salary.

In other words, even after adjusting for local prices, the Australian role still lands materially behind. To match US$200k on this rough PPP basis, the Melbourne salary would still need to be closer to A$278k.

3. Cost of living has to do an implausibly large amount of work

To justify the cash gap on standard-of-living grounds, the US location would need to be roughly 1.47x to 1.50x as expensive as Melbourne.

That is a very large difference. It is not the kind of gap you get from an ordinary "different city, different rent" explanation. It requires a genuinely extreme US cost of living — think peak San Francisco — to carry all the moral weight here.

And most US tech roles are not in peak San Francisco.

4. Even total employer cost leaves a large gap

This is where cross-country salary conversations often get muddy, so it is worth being precise.

Australia has compulsory superannuation. At the 12 percent Superannuation Guarantee rate used in this article, A$200k as base salary becomes A$224k in employer cost. Using the fallback exchange rate, that converts to about US$158k.

On the US side, US$200k also costs more than base salary once employer payroll taxes are included. Using Social Security and Medicare employer taxes only, that adds about US$14,339, bringing total employer cost to about US$214,339 before health insurance or any retirement match.

So even on an employer-cost basis, the US-based teammate still costs about 36 percent more. And if the A$200k figure is actually package-inclusive of super, not base plus super, then the Australian cash salary is lower again and the disparity gets worse.

The part that makes this system so difficult to combat: The Arbitrage Band

There is a second layer to this that makes the pattern even more persistent we can call the arbitrage band.

In Melbourne, the local market for comparable software roles is often nowhere near the US-equivalent number.

That matters because it creates a very stable middle zone for employers:

• pay well above what many Australian candidates can get locally
• still pay far below what the same work would cost in the US - even though it is in the same virtual place

This is the real trick.

The offer can be genuinely attractive to the Australian worker and still be structurally discounted from the company's point of view.

What the Melbourne market appears to support

Salary datasets vary by title, company type, and whether they measure base salary or total compensation. Titles are also noisy. A "senior" at one company can be doing staff-shaped work at another.

Even with that caveat, the broad shape is clear across multiple independent sources:

• SEEK (citywide average from job ads): A$115,000 for software engineer
• Hays FY24/25 (Victoria, exclusive of super): A$140,000 senior developer — A$160,000 technical lead — A$180,000 development manager
• Levels.fyi (Greater Melbourne, updated March 2026): A$168,000 median total comp for senior software engineer; 25th–75th percentile range of A$142,000–A$196,000
• Onset FY24/25: A$180,000–A$230,000 for principal and staff engineers

So if someone says a role comparable to that US$210,000 US job might go for something like A$150,000 in Melbourne, that is not a crazy claim. It sits squarely inside the range suggested by current local-market guides for senior-to-lead software roles.

Why this strengthens the argument, not weakens it

At first glance, this can sound like a defense of the employer: "But the Australian offer is already above local market."

That is exactly the point.

If local Melbourne market pricing for a strong senior or lead engineer is something like A$150,000 to A$180,000, then an offer around A$200,000 can feel meaningfully above-market to the worker while still being dramatically below US parity.

That means the company does not need to choose between:

• paying Australian-market rates
• paying US-market rates

It can sit comfortably in between.

And that middle position is powerful.

It lets the company present the offer as generous in Australia, competitive internally, and financially efficient relative to the US. All three can be true at once.

That is a more sophisticated framing of the problem than simple "cheap labor" framing where companies outsource to pay rock-bottom salaries.

Often it is a story of companies paying just enough above local market to feel exceptional, while still anchoring far below the rate implied by the global value of the work.

Why the usual defenses do not settle the fairness question

There are several employer-side arguments that sound reasonable here.

Cross-border hiring is complex. EORs reduce risk. Local benchmarking is standard practice. Compensation teams need a system. Finance wants predictability.

All of that can be true.

It still does not answer the fairness question.

Compliance is real. It is not a moral justification.

Jurisdictional complexity is a company operating cost. It is the price of hiring beyond your home border. It should not quietly become a permanent discount applied to the worker.

If a company is happy to capture the benefit of global talent, it should be willing to carry the complexity that comes with hiring globally.

"Local market rates" mostly measure leverage, not value

When a company says it pays by "cost of labor" rather than "cost of living," what it usually means is that pay is anchored to what the worker's local market can be made to accept.

That is a bargaining-power statement. It is not a clean statement of contribution, difficulty, or business value.

Two people can create the same leverage for a company while living in places with very different salary norms. Localized pay treats that asymmetry in local bargaining power as if it were morally neutral.

It is not.

Geography is often constraint, not preference

People do not choose location in a vacuum. Partners, children, visas, aging parents, healthcare, citizenship, and community all matter. A compensation model that treats geography as a simple consumer preference often ends up penalizing constraint.

That matters because "you can always move" is not a serious fairness principle.

The numbers do not capture the full cost

This section arguably should be featured at the forefront of this post - because its the most most real component of what would drive australian based high achieving talent out of the US market:

The salary comparison above is already unfavorable - and it only measures money.

Working for a US company from Melbourne is not the same job as working for a US company from Austin. It carries hidden costs that never appear in the compensation comparison — and they compound the unfairness of the gap.

Timezone. Australian east coast time sits 15 to 17 hours ahead of US Pacific time. The collaboration window is in the early morning or late evening. Calls that are 9 AM in San Francisco are 2 AM or 3 AM in Melbourne — or a 7 AM start if you are fortunate. Someone pays that tax. It is usually the Australian end.

Travel. Many US-headquartered tech roles carry an expectation of regular visits — all-hands meetings, offsites, team onsite weeks. The flight from Melbourne to the US east or west coast runs 17 to 22 hours each way. A week-long trip is 10 days door-to-door. It is not a weekend inconvenience. It is days of physical recovery and family disruption on top of the professional obligation.

Visibility. Career advancement in most companies is relational as much as meritocratic. If the people who make promotion decisions are in San Francisco and you are in Melbourne, you are structurally less visible than the person two desks away from them. A large pay gap is hard enough to close. Closing it from a different hemisphere while bearing a timezone and travel load the US team does not carry adds another layer of difficulty.

None of this shows up in the salary line. None of it is priced in.

So the real question is not just "am I paid fairly versus my US teammates?" It is: "am I being paid enough of a premium over what I could earn locally to justify the early calls, the long-haul travel, and the structural disadvantage?"

Melbourne-based senior and staff engineering roles exist today that pay in the neighborhood of A$200,000 to A$210,000. They come without the timezone tax. Without the travel burden. Without the visibility disadvantage that comes from being 16 time zones from where decisions get made.

For a US company paying 40 percent less in real USD terms — and not compensating for any of these additional costs — the deal is not just unfair. It is objectively worse.

What better companies should do instead

Companies do not need to reach perfect global parity overnight. They do need to stop treating structured arbitrage as if it were a principled compensation philosophy, because that is where the gap stops looking incidental and starts looking tacitly exploitative.

A better model would look something like this:

1. Set global compensation bands by role and level, not by worker geography.
2. Separate base pay from mandatory employer-side costs such as Australian super or US payroll taxes.
3. If location factors are used, cap them tightly and publish them.
4. Add a purchasing-power floor so "localization" cannot drift into extreme underpayment.
5. Treat EOR and compliance overhead as company cost, not as evidence that the worker's contribution is worth less.

That would still leave room for practical constraints, but it would move the system toward honesty.

Because right now the language is cleaner than the reality. We call it benchmarking. We call it localization. We call it cost of labor.

But when two people are doing the same work on the same team and one of them is sitting behind a 40 percent-plus compensation wall, the system is telling us something very plain:

for globally integrated remote work, geography is shaping the wage policy more than the value of the work itself.

The point

What this Melbourne-versus-US comparison reveals is not an edge case. It is the underlying shape of a compensation regime that wants the benefits of global hiring without paying the price that global hiring ought to require.

That is why the disparity feels so wrong even when the paperwork is immaculate.

The wall is hard to see when we talk in abstractions. It becomes obvious the moment we compare the people standing on either side of it.

Same company. Same team. Same problems. One of them is also absorbing 16 hours of timezone displacement and flying to America twice a year.

At some point the calculus tips. A$210,000 at a Melbourne-based company — for a role that does not come with the early morning calls, the long-haul travel, or the structural disadvantage of being remote from leadership — is a better deal than a US-company salary that looks similar on the sticker but loses 40 percent once FX is applied. Especially when you add back everything the salary comparison conveniently leaves out.

The rational response to a bad deal is to find a better one. When talented Australian engineers start choosing local employers — not because they cannot land US-company roles, but because the US-company deal is objectively worse after the numbers are run — companies paying location-discounted rates will feel it.

The wall works until people stop walking into it.

If companies want to say they hire from a global talent market, the compensation logic needs to start behaving like talent is actually global.

Otherwise globally remote work is not flattening opportunity. It is just widening the catchment area for discounted excellence — until the people being discounted decide they have done the math.

Method notes and sources

All figures referenced here are based on data current as of April 6, 2026.

• Federal Reserve H.10 historical exchange rates for the Australian dollar
• The Economist Big Mac Index interactive
• The Economist Big Mac data repository
• Australian Taxation Office: Super guarantee rate
• Australian Taxation Office: How much super to pay
• Social Security Administration: 2026 contribution and benefit base
• IRS: Social Security and Medicare withholding rates
• SEEK: Software Engineer salary in Melbourne
• Hays Salary Guide FY24/25
• Levels.fyi: Senior Software Engineer salary in Greater Melbourne Area
• Onset FY24/25 Tech Salary Guide