The Glass Wall in Global Tech Pay
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 Melbourne and the other is based somewhere in the United States.
A$200k in Australia and US$200k in the United States look symmetrical on paper. They are not.
International talent is allowed to do the work, but often not allowed to set the price.
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.
If the work is global but the pay policy is local, then a single global labor market has not actually formed.
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
Consider an illustrative anonymous comparison:
- Melbourne: about A$200,000
- US-based teammate: about US$210,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.
They are not.
1. At market FX, these salaries are nowhere near each other
Using the Federal Reserve's March 2026 AUD/USD range of roughly US$0.70 to US$0.715 per A$1, A$200,000 converts to about US$140,000 to US$143,000.
Against US$210,000, that means the US-based teammate is making about 47 percent to 50 percent more in cash salary.
To close that gap on cash alone, the Melbourne salary would need to be closer to A$294,000 to A$300,000, not A$200,000.
2. A rough PPP check still does not rescue the Australian number
Purchasing-power adjustments are worth checking because employers often imply that a lower Australian salary is reasonable once local prices are considered.
That argument still comes up short.
Using the Economist's January 2026 Big Mac data as a rough PPP proxy, A$200,000 works out to about US$144,000 in purchasing-power terms. That still leaves the Australian figure at roughly 69 percent of the US$210,000 salary.
This is important because it shows the issue is not just currency optics. Even after a rough purchasing-power adjustment, the Australian role is still materially behind.
FX and PPP are different lenses. Both point in the same direction: the gap is large enough that it cannot be waved away as a rounding error, a tax footnote, or a misunderstanding about local prices.
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. In the 2025-26 financial year, the Superannuation Guarantee rate is 12 percent. If A$200,000 is base salary and super sits on top, the employer's cost becomes A$224,000. At the same March 2026 exchange-rate range, that is about US$157,000 to US$160,000.
On the US side, a US$210,000 employee also costs more than base salary once employer payroll taxes are included. Using 2026 Social Security and Medicare rates, employer-side payroll taxes add roughly US$14,484, bringing total employer cost to around US$224,484 before health insurance or any retirement match.
So even on an employer-cost basis, the US-based teammate still costs roughly 40 percent to 43 percent more.
And if the A$200,000 figure is actually a total package inclusive of super, not base plus super, then the Australian cash salary is lower again and the disparity gets worse.
Different tax and benefits systems complicate comparisons. They do not rescue this one.
The part that makes this system durable: the arbitrage band
There is a second layer to this that makes the pattern even more persistent.
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
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.
This is why the disparity survives so easily. The company is not forced to underpay by Australian standards in order to gain a discount relative to the US. It can pay above Melbourne market, win the candidate, and still capture a large labor-cost advantage.
That is a more sophisticated problem than simple "cheap labor" framing.
This is not always a story of companies paying 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.
The system works best for employers when the offer is high enough to feel like a win locally, but low enough to remain a discount globally.
See it for yourself
The numbers above establish the pattern. The lab below lets you stress-test it.
Start by clicking "Set same sticker number" — give both workers identical nominal pay — then watch the gap appear once market FX is applied. Adjust the exchange rate. Change the salaries. Move the Melbourne market anchor. The shape stays the same: the Australian offer sits above local market and well below US parity, and the company is comfortable in the middle.
Start with Melbourne market pay, then see how the Australian offer stacks up against US parity.
This panel is built to answer one specific question clearly: how can an Australian offer look strong relative to Melbourne market pay and still leave a large gap versus comparable US compensation, even after super is included?
Set the local market, the actual offer, and the FX rate
This column defines the scenario. The rest of the lab shows what those inputs mean after Australia and US pay are converted into the same frame.
Typical Melbourne market pay
Use this as the local benchmark for an equivalent role in Melbourne. It is the market anchor, not the actual offer.
Australian offer versus US comparable pay
Set the actual Australian offer and the comparable US base salary for the same class of work.
Copies the Australian offer into the US salary field so you can compare, for example, A$200k versus US$200k directly.
Exchange rate
Use live ECB reference FX or move the slider manually. Every US-to-AUD comparison below uses this rate.
Latest FX loads from Frankfurter using ECB reference data.
Everything restated in Australian dollars
Read this from left to right: typical Melbourne market pay, the actual Australian offer, the Australian employer-side cost after super, then the US salary and US total comp converted into Australian dollars.
Assumes the Australian number is base salary with super on top. If the Australian figure is package inclusive of super instead, the employer-cost gap grows further.
The Australian offer is A$35k above local Melbourne market, but A$98k short of US cash parity.
After adding Australia's 12% super and US employer payroll taxes, Australia is still A$95k short of US employer-side total comp.
Market FX versus burger PPP
Australia's market exchange rate and the burger-implied PPP rate do not move together. That is why PPP can soften the story without eliminating the disparity.
Both lines show how many Australian dollars you need to buy one US dollar — higher means a weaker AUD. The blue line is the actual market exchange rate. The amber line is the rate implied by burger prices: if a Big Mac costs A$8.50 in Australia and US$6.12 in the US, the implied PPP rate is 8.50 ÷ 6.12 ≈ 1.39. The blue line sits above the amber in most years, which means the AUD trades weaker on forex markets than its local purchasing power would suggest. For an Australian worker, this makes the market-FX conversion the more punishing lens — their salary converts to fewer US dollars than PPP would give them. The two lines converging would mean fair value; the persistent gap above means the AUD is undervalued at market rates.
Australia versus US burger price in US dollars
Converted at market FX, Australia's burger price sometimes nearly catches the US and sometimes falls well below it. The spread is a simple proxy for cross-country purchasing-power drift.
Both lines show the price of a Big Mac in US dollars. The purple line is what Americans actually pay at the counter. The blue line is what Australians pay — after converting from AUD at the prevailing market exchange rate. If the two countries were at true purchasing-power parity, the lines would sit on top of each other. They don't. The gap below the purple line is the empirical basis for cost-of-living arguments: Australian goods are genuinely somewhat cheaper in USD terms. But look at the size of that gap — roughly US$0.40–0.60 in recent years on a ~US$6 item, a discount of around 5–10%. That is nowhere near the 40–50% salary difference this post is examining. Cost of living is real; it just is not doing nearly enough work to justify the pay gap.
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.
Remote work was supposed to make talent more portable. Too often it has mostly made talent more sourceable.
The numbers do not capture the full cost
The salary comparison above is already unfavorable. But 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.
The pay gap is the headline. The hidden costs are the fine print. Together they make the case for walking away.
What better companies should do instead
A 40 percent-plus same-role pay gap does not become fair because it came out of a spreadsheet. 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.
A better model would look something like this:
- Set global compensation bands by role and level, not by worker geography.
- Separate base pay from mandatory employer-side costs such as Australian super or US payroll taxes.
- If location factors are used, cap them tightly and publish them.
- Add a purchasing-power floor so "localization" cannot drift into extreme underpayment.
- 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:
the market is not truly global at all.
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.
Different price for that labor. Because of where the worker lives.
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 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