A new study from Harvard Business School put a number on something that engineering leaders have been sensing for a while. Researcher Zoë Cullen found that tech workers would sacrifice up to 25% of their total compensation to avoid commuting five days a week. At the average tech salary of $239,000, that works out to nearly $60,000 a year.
That's not a preference. That's a revealed valuation — the kind economists pay attention to because it reflects what people actually prioritize, not just what they say in surveys. And it's 3 to 5 times higher than previous estimates suggested.
Read those three numbers together and a problem comes into focus: most companies are posting fully on-site roles while most engineers would rather take a significant pay cut than commute five days a week. Something has to give — and right now, it's usually the company's ability to hire and retain the people they actually want.
Why this number matters more than it seems
The $60,000 figure is striking on its own. But what makes it strategically important for hiring leaders is what it implies about the effective compensation gap between remote and on-site roles.
If a senior engineer values remote work at $60,000 per year, then a fully on-site role at $200,000 is effectively competing against a remote role at $140,000 — from the engineer's perspective. A company that mandates office attendance isn't just making a workplace policy decision. It's making a compensation decision, whether it intends to or not.
Most companies haven't done this math explicitly. The ones that have are either adjusting their location policies or significantly increasing compensation for on-site roles. The ones that haven't are losing candidates to competitors who offer flexibility — often without realizing that's the reason.
The return-to-office pressure is real — and so is the pushback
This data lands in a market that is already under significant RTO pressure. Major employers across tech have reduced or eliminated remote options since 2023. Amazon, Google, and others have implemented multi-day in-office requirements. Around 30% of organizations say they plan to reduce or eliminate remote work in 2026.
But the engineering talent market isn't responding the way those mandates might have hoped. The engineers who have the most leverage — the senior, high-demand, hard-to-find ones — also have the most options. They can be selective about where they work, and increasingly, location flexibility is a primary filter.
The talent that's hardest to hire is also the talent most likely to walk away from an RTO mandate. Mid-level engineers with fewer alternatives may comply. The ones companies most want to retain — and attract — are the ones who can afford not to.
What this means for how companies hire
The practical implication for hiring leaders is that location policy is now a talent strategy decision, not just an operations one. A few things follow from that.
Geographic flexibility expands the candidate pool dramatically. Companies that hire without location constraints access engineers across time zones, markets, and compensation bands. The structural advantage of remote-first hiring isn't just about flexibility — it's about reach. You're not competing for the same engineers as every other on-site employer in your city.
Compensation benchmarking needs to account for location value. A salary competitive for an on-site role may not be competitive for a remote one — and vice versa. Companies setting compensation based purely on role and seniority, without accounting for location expectations, are likely mispricing their offers in ways that show up as candidate drop-off and unexplained rejection rates.
Retention risk is concentrated among the most flexible employees. The engineers most capable of finding a remote role elsewhere are also the ones most likely to do so if their current situation changes. For companies implementing RTO policies, the retention risk isn't evenly distributed — it's heaviest among the people they can least afford to lose.
The companies getting this right
The engineering leaders navigating this most effectively aren't necessarily the ones offering fully remote work — some genuinely need on-site presence for the nature of their product. What they have in common is clarity and honesty about what they're offering and why, combined with compensation that genuinely reflects what they're asking for in return.
They're also increasingly looking globally. At AWWCOR, we work with companies that have built distributed engineering teams across 150+ countries — not because it's trendier, but because it works. The engineers are out there. The compliance infrastructure to engage them properly exists. The companies that have built the systems to hire globally don't face the same location-constrained talent pool as those that haven't.
The bottom line
When Harvard puts a $60,000 number on remote work, it stops being a culture conversation and becomes a math problem. The companies that solve it — by adjusting their location policy, their compensation, or their hiring geography — will have a structural advantage in building engineering teams. The ones that don't will keep wondering why their best candidates keep disappearing.