The Remote Work Backlash: Why Companies Are Forcing Return-to-Office and What It Means for Your Career

Published on BirJob.com · March 2026 · by Ismat

The Paradox Nobody's Talking About

Here's a number that should make you tilt your head: in 2025, 37% of companies enforced a return-to-office mandate, up from 17% in 2024. That's more than double. CEOs wrote stern memos. HR sent calendar invites. Badge-swipe tracking was installed. The message was clear: come back.

And here's the part that makes it absurd: actual office attendance only increased by 1–3 percentage points over the same period, according to data from Archie. Companies doubled their enforcement. Employees barely budged. Mandates went out. Compliance trickled in. The gap between what companies demanded and what workers actually did is one of the most fascinating labor dynamics of the decade, and it tells you everything you need to know about where the real power sits in this negotiation.

I've been watching this unfold with a mix of professional curiosity and personal investment. I run BirJob from Baku, Azerbaijan. My entire operation is remote-first by necessity and by choice. I've worked with developers, designers, and freelancers across multiple countries who have never set foot in an office together. The work gets done. The product ships. The users don't know or care where anyone sits. So when I see a Fortune 500 CEO claim that "innovation requires physical presence," I want to understand: do they have data to support that, or are they just uncomfortable with a world they didn't design?

Let me lay out what's actually happening, who's driving it, what the data says, and what it means for your career — whether you're in San Francisco or Baku.

The Numbers First

The RTO debate generates a lot of heat and not much light. Let's start with the data that matters.

• According to a ResumeBuilder survey, 30% of companies plan to require 5-day in-office work by 2026. This is a significant increase from 2024, when only about 19% required full-time office attendance.
• The same ResumeBuilder report found that 47% of companies plan to terminate employees who don't comply with RTO mandates. This isn't empty talk: AT&T, Amazon, and several financial institutions have already moved non-compliant workers to performance improvement plans or terminated them outright.
• On the flip side, 80% of companies that enforced RTO lost talent as a direct result, according to ResumeBuilder. This isn't surprising: when you take away something people value, they leave. What's surprising is that companies did it anyway.
• Founder Reports compiled data showing that companies with RTO mandates saw employee satisfaction scores drop by 20–30% in the quarters following announcement. Voluntary turnover increased, and the departing employees were disproportionately high performers — exactly the people companies can least afford to lose.
• Global data from FMC Group shows that remote work adoption varies enormously by country: the US, UK, and Netherlands have the highest remote work rates (25–35% of workers), while countries like Japan, South Korea, and much of Southern Europe have much lower rates (5–15%). The cultural component of this debate is real and underexplored.
• Hubstaff's 2024 remote work statistics compilation found that remote workers report being 13% more productive than in-office workers, based on self-reported and manager-assessed metrics. However, the data on collaboration-intensive work (brainstorming, design sprints, strategic planning) is less clear, with some studies showing in-person collaboration is more effective for novel problem-solving.
• Apollo Technical reports that remote workers save an average of $6,000–$12,000 per year on commuting, food, and clothing costs. For many workers, an RTO mandate is functionally equivalent to a pay cut of 5–10%.

These numbers tell a clear story: companies are pushing RTO harder than ever, employees are resisting more than ever, and the result is friction, attrition, and a labor market that's sorting itself into remote-friendly and remote-hostile camps. The middle ground — hybrid — is where most companies are landing, but hybrid has its own problems, which we'll get to.

The Major Companies: Who Went Back and What Happened

The RTO wave didn't happen all at once. It built gradually through 2023–2025, with each major company's announcement giving cover to the next. Here's what happened at the companies that made the biggest headlines.

Amazon

Amazon was the most aggressive among Big Tech. CEO Andy Jassy announced a 5-day-per-week RTO mandate effective January 2025, reversing a previous 3-day hybrid policy. The internal reaction was volcanic. An internal Slack channel opposing the mandate had over 30,000 members. Blind (the anonymous workplace app) was flooded with Amazon employees discussing job searches. According to reporting compiled by Founder Reports, Amazon saw a notable increase in voluntary attrition following the announcement, particularly among senior engineers and managers.

The stated reason: "We believe that the advantages of being together in the office are significant," Jassy wrote in a memo. The unstated reasons are more complex, and I'll get to them.

JPMorgan Chase

JPMorgan CEO Jamie Dimon has been the most vocal anti-remote executive in corporate America. He mandated full-time office work for all managing directors in 2023 and expanded the mandate to most employees by 2025. When employees pushed back, Dimon's response was blunt: "If you don't like it, you have a choice." JPMorgan is one of the few companies with the labor market power to take that position and survive it. Most companies don't.

Goldman Sachs

Goldman Sachs was among the first to mandate RTO, with CEO David Solomon calling remote work an "aberration" as early as 2021. By 2025, Goldman's 5-day mandate was firmly established and actively enforced, with badge-swipe data used to track compliance. The company's culture has always been intense and in-person, so the transition was less disruptive internally than at companies where remote work had become deeply embedded.

AT&T

AT&T mandated 5-day RTO in 2024 and simultaneously closed several regional offices, forcing thousands of employees to either relocate or resign. This is the most controversial version of RTO: requiring office attendance while reducing the number of offices. Critics called it a "stealth layoff" — a way to cut headcount without paying severance. AT&T denied this, but the optics were terrible. Employees who had been hired as remote workers during the pandemic were told to report to offices hours from their homes.

Samsung

Samsung mandated a 6-day work week for executives in 2024, going even further than most Western companies. While this is specific to Korean corporate culture (which has historically emphasized long hours and physical presence), it reflects a broader global trend of companies reasserting control over where and when work happens. The backlash, even in Korea's traditionally compliant corporate culture, was significant enough to make international news.

The Real Reasons Behind RTO (It's Not About Productivity)

Every CEO who mandates RTO gives the same reasons: collaboration, culture, innovation, mentorship. These sound reasonable. Some of them are even partially true. But they're not the main reasons. Let me walk through what's actually driving these decisions.

Reason 1: Commercial Real Estate

This is the one nobody wants to say out loud. Many large companies signed 10–15 year commercial real estate leases between 2015 and 2020, committing billions of dollars to office space. When remote work became the norm, those offices sat empty — but the rent payments continued. If your company is paying $50 million per year for a headquarters that's 30% occupied, there's enormous financial pressure to fill those seats, regardless of whether it makes workers more productive.

Some companies have taken the rational approach: sublease the unused space, negotiate lease exits, or downsize to smaller offices designed for collaborative work rather than individual desk work. Others have taken the irrational approach: force everyone back to fill the seats you're already paying for. The second approach is what you're seeing at most RTO companies. It's a sunk cost fallacy playing out at corporate scale.

Reason 2: Control and Visibility

There is a management philosophy — more common in traditional industries than in tech — that equates visibility with productivity. If I can see you at your desk, you're working. If I can't see you, I'm not sure. This is, of course, absurd. The most productive remote workers I know are disciplined, focused, and output-driven. Some of the least productive workers I've encountered were people who sat at their desks for 10 hours a day, attended every meeting, and produced almost nothing of value. But the "butts in seats" mentality is deeply ingrained, especially among executives who built their careers in pre-pandemic office culture.

Hubstaff's data shows that companies that measure output rather than hours see no productivity difference between remote and in-office workers. Companies that measure hours and "engagement" (a euphemism for presence) consistently find that in-office workers appear more productive, because they're measuring the wrong thing.

Reason 3: Middle Management Justification

This is the uncomfortable one. Remote work made a lot of middle management roles visibly unnecessary. When your team communicates asynchronously through Slack, documents decisions in Notion, and coordinates through project management tools, the role of "person who walks around checking on people" becomes redundant. RTO restores the environment in which middle management is most useful: the physical office with its meetings, hallway conversations, and visible hierarchy.

I want to be fair here: not all middle management is unnecessary. Good managers provide mentorship, clear obstacles, coordinate between teams, and make personnel decisions. These functions are needed regardless of work location. But the style of management that's optimized for physical offices — the checking-in, the drive-by desk visits, the "let's discuss this in the conference room" meetings — is genuinely less useful in a remote context. Some managers adapted. Many didn't.

Reason 4: Culture Is Actually Hard to Build Remotely

I'm going to be honest about something that the remote work maximalists don't like to hear: building team culture is genuinely harder when everyone works from home. It's not impossible — companies like GitLab and Automattic have proven that — but it requires deliberate, sustained effort that most companies aren't willing to invest in.

In an office, culture happens by accident. You chat with someone at the coffee machine, discover a shared interest, and form a bond that makes future collaboration smoother. You overhear a conversation about a project problem and offer a solution you wouldn't have known about otherwise. A new hire absorbs team norms by watching how people interact. Remote work requires all of this to be intentional rather than accidental: scheduled coffee chats, documented norms, explicit onboarding processes, virtual social events. Many companies tried and gave up because it felt forced. It does feel forced. But so does brushing your teeth, and you still do it.

What RTO Means for Developers Specifically

Software developers are in a unique position in the RTO debate because the nature of development work is better suited to remote work than almost any other knowledge work. Deep focus, asynchronous communication, code review, and deployment can all happen without physical presence. The exceptions — pair programming, whiteboard architecture sessions, team retrospectives — can be effective remotely with the right tools, or can be handled with occasional in-person meetings.

The data supports this. A Stack Overflow 2024 survey found that 42% of professional developers work fully remote, and another 42% work hybrid. Only 16% work fully in-office. Developers are the most remote-friendly profession on earth, and the gap between developer remote rates and average worker remote rates has been growing.

What this means practically: if you're a developer, you have more leverage to negotiate remote work than almost any other profession. The talent shortage in software engineering, while less acute than 2021, is still real. Companies that require full-time RTO for developers are voluntarily excluding themselves from ~85% of the developer talent pool. Some companies (Goldman Sachs, Amazon) are large and prestigious enough to absorb that hit. Most are not.

Remote-Friendly Companies for Developers (2025–2026)

If you're a developer looking for companies that have committed to remote work (not just tolerating it, but structurally supporting it), here are the most prominent:

Beyond these well-known names, thousands of smaller companies and startups are remote-first or remote-friendly. The reality is that for developers, the remote job market is enormous even in the RTO era — it's just no longer every company the way it briefly seemed to be in 2021.

The Hybrid Problem

Most companies that aren't going fully RTO or fully remote are landing on "hybrid" — typically 2–3 days per week in the office. On paper, this sounds like the best of both worlds. In practice, it's often the worst.

The core problem with hybrid is coordination cost. If half the team is in the office on Tuesday and the other half is remote, every meeting becomes a hybrid meeting with one group around a conference table and the other group on a screen. These meetings are terrible for the remote participants. They can't read body language, they get talked over, and the in-room people naturally default to speaking to each other rather than to the screen. Research compiled by Hubstaff shows that remote participants in hybrid meetings report feeling "less included" and "less likely to contribute" compared to in-person participants.

The second problem is the "anchor day" fallacy. Companies designate Tuesday/Wednesday/Thursday as in-office days, expecting organic collaboration to happen. What actually happens: people come in, sit at their desks with headphones on, join the same Zoom calls they would have joined from home, eat lunch at their desk, and go home. The commute cost is real. The collaboration benefit is marginal. One viral post summarized it as: "I commuted 45 minutes each way to sit on Zoom calls in a louder room."

The companies that make hybrid work well are the ones that design the in-office days intentionally: team workshops, design sprints, planning sessions, social events. The office becomes a place for collaborative work, and home becomes the place for focused work. This requires genuine effort from management to restructure how work happens. Most companies don't bother, which is why most hybrid arrangements feel like neither fish nor fowl.

Salary Impact: Remote vs Hybrid vs In-Office

One of the least-discussed aspects of the RTO debate is its impact on compensation. The data here is nuanced and sometimes contradictory.

The salary geography arbitrage is the most interesting dynamic here. A developer in Baku earning $60,000/year from a US remote job has a higher purchasing-power-adjusted income than a developer in San Francisco earning $150,000/year. This isn't a secret — it's the foundational premise of the global remote hiring boom — but it has implications for the RTO debate. Companies that mandate RTO are essentially limiting themselves to local talent pools, which are both more expensive and more competitive. Companies that embrace remote work access a global talent pool that's cheaper and deeper.

How to Negotiate Remote Work in an RTO World

If your company is mandating RTO and you want to keep working remotely, here's what I've seen actually work (and what doesn't).

What Works

• Make yourself indispensable first, then negotiate. The single strongest negotiating position is: "I am so valuable that losing me costs more than accommodating my work arrangement." If you're a replaceable mid-level developer, you have less leverage. If you're a senior developer who owns a critical system and would take 6 months to replace, you have a lot.
• Propose a trial period. Don't demand permanent remote work. Ask for a 3–6 month trial: "Let me work remotely for the next quarter. Let's measure my output against the team average. If my performance drops, I'll come back." This is hard to refuse because it's data-driven and reversible.
• Offer to come in for specific purposes. "I'll be in the office every Tuesday for team meetings and every other Thursday for planning sessions. The rest of my time is more productive at home." This demonstrates flexibility and gives the manager in-person contact without full RTO compliance.
• Document your productivity. If you've been productive while remote, have the receipts: PRs merged, features shipped, bugs fixed, pages on-call without incident. Numbers are harder to argue with than feelings.
• Be willing to take a different role. Some companies allow individual exceptions. Some have specific teams or projects that remain remote. If your current role requires in-office, explore whether there's a similar role with different requirements.

What Doesn't Work

• Citing studies about remote work productivity. Your CEO has already read these studies (or summaries of them). They're enforcing RTO anyway. The decision was not made based on productivity research, so productivity research won't reverse it.
• Organizing employee resistance. Signing petitions, creating Slack channels, writing open letters. These occasionally work at very large companies where public embarrassment is a lever. At most companies, they just flag you as a troublemaker.
• Quiet non-compliance. "Coffee badging" (swiping your badge, being seen, then leaving) or showing up but doing nothing. Companies are getting better at tracking actual attendance, and being caught gaming the system is worse for your career than openly negotiating.
• Threatening to quit without being prepared to follow through. Empty threats destroy credibility. If you're going to use "I'll leave" as leverage, have another offer in hand. Otherwise, don't say it.

The Companies That Doubled Down on Remote

While the headlines focus on RTO, there's a counter-trend that deserves equal attention: companies that have committed more deeply to remote work as competitors retreat. These companies see the RTO wave as a talent acquisition opportunity.

GitLab has been all-remote since its founding in 2014 and has over 1,500 employees in 65+ countries. Their all-remote handbook is the most comprehensive guide to remote work ever published, covering everything from async communication protocols to how to handle time zone differences to how to fire someone you've never met in person. When other companies started mandating RTO, GitLab's CEO Sid Sijbrandij published a blog post welcoming their displaced workers. Smart move.

Automattic (the company behind WordPress.com, Tumblr, and WooCommerce) has been remote since 2005 — before remote work was cool, before Slack existed, before Zoom existed. Their approach: hire the best people regardless of location, communicate asynchronously by default, and get together in person 1–2 times per year for "grand meetups." CEO Matt Mullenweg has been one of the most vocal advocates for remote work, calling office-first companies "legacy" operations.

Zapier has been remote since 2011 and uses a transparent location-based pay formula. They publish their compensation philosophy openly and adjust salaries based on cost-of-labor data for each employee's location. This has attracted talent globally and allowed them to maintain a smaller team (around 800) that punches above its weight.

Deel is particularly interesting because they're a remote company that builds tools for other remote companies. They provide global payroll, compliance, and HR infrastructure for companies hiring internationally. Their own workforce spans 100+ countries. They're not going to mandate RTO because their entire business model depends on remote work being viable. The incentives are aligned perfectly.

These companies share common characteristics: they invested heavily in asynchronous communication (writing over meetings), documentation (decisions are recorded, not lost in hallway conversations), and intentional culture-building (regular virtual events, annual meetups, transparent communication). Remote work isn't their backup plan — it's their competitive advantage.

The Impact on Emerging Markets

For workers in Azerbaijan, Turkey, Eastern Europe, and other emerging markets, the RTO backlash has a specific and significant implication: the talent pool of remote-friendly Western companies may shrink, but the remaining companies are hiring more globally than ever.

Here's the dynamic. When Amazon mandates 5-day RTO, every Amazon developer who values remote work starts looking for a new job. Many of them end up at remote-first companies like the ones I listed above. Those companies grow. They hire more. And because they're remote-first, they hire globally. A senior developer who leaves Amazon for GitLab might be replaced by a senior developer in Sao Paulo or Baku or Lagos, paid 60% of a Bay Area salary but 400% of their local market rate. Everyone wins except the in-office-mandate company, which loses talent.

The practical implication: if you're a developer in an emerging market, the RTO wave in the US is actually good for you. It's accelerating the trend of Western companies hiring globally for remote positions. The competition for these roles is increasing (more US-based developers are looking for remote work), but so is the supply of roles (more companies are going all-in on remote to attract the talent that RTO companies are pushing away).

To position yourself well: invest in English fluency (written more than spoken — remote work is text-heavy), build a portfolio of work that demonstrates remote work habits (async communication, documentation, self-direction), and target companies that have a track record of international hiring rather than companies that are "open to remote" but have never actually hired outside their home country.

What the Research Actually Says About Productivity

I've been saving this section because it requires nuance, and nuance is the enemy of viral takes.

The honest summary of the research: fully remote work is equally or slightly more productive than in-office work for individual-focused tasks (coding, writing, data analysis, customer support). It is slightly less effective for collaborative, creative, and mentorship-intensive tasks (brainstorming, design sprints, onboarding new employees). Hybrid approaches can capture the best of both, but only with intentional design.

The most rigorous study on this topic is a 2022 Stanford study by Nicholas Bloom et al., which found that hybrid work (3 days office, 2 days home) had no negative impact on productivity or career outcomes over a two-year period at a large technology company. In fact, it reduced attrition by 35% — a finding with enormous financial implications.

A Hubstaff analysis of remote work data found that remote workers work an average of 1.4 more days per month than in-office workers (partly because commuting time gets converted to work time, and partly because the flexibility to work during peak energy hours increases total output).

But here's what the pro-remote advocates don't like to cite: a 2022 Nature paper studying Microsoft's workforce found that remote work reduced cross-team collaboration by 25% and made networks more siloed. Workers communicated more within their immediate team but less with colleagues in other groups. This is a real cost. Cross-pollination of ideas between teams is one of the genuine advantages of physical co-location, and remote-first companies have to work hard to replicate it.

My read of the totality of the research: the productivity argument for RTO is weak, but the collaboration and culture arguments are real. Companies should be honest about which one is driving their decision. If it's "we need people in the office because our real estate lease demands it," just say that. If it's "we haven't figured out how to onboard new employees remotely and our junior developers are struggling," that's a solvable problem, and mandating RTO is the lazy solution.

What I Actually Think

I'll be direct.

Most RTO mandates are not about productivity. They're about control, real estate, and a management class that was trained in a pre-remote world and doesn't know how to lead in a post-remote one. The CEOs enforcing 5-day RTO are overwhelmingly older men who built their careers in offices and genuinely believe that the hallway conversation is the pinnacle of knowledge work. They're not wrong that hallway conversations have value. They're wrong that the value of those conversations exceeds the cost of forcing thousands of people to commute daily.

Hybrid is the sustainable equilibrium for most companies, but only if done intentionally. "Come in Tuesday through Thursday" is not a strategy. It's a calendar entry. Real hybrid means: in-person for collaboration, remote for focus. In-person for onboarding, remote for execution. In-person for team building, remote for deep work. This requires managers to actually think about when and why physical presence adds value, rather than mandating it by default.

The companies mandating full RTO will lose the long game. Not because remote work is always better — it's not — but because the labor market is global and talent is mobile. A company that requires 5-day office attendance in Manhattan is competing for talent against companies that hire the same caliber of developer from anywhere in the world at 60% of the cost. The math doesn't work. The RTO companies will either reverse course in 2–3 years or gradually lose their best people to remote-first competitors. Some, like JPMorgan and Goldman Sachs, will survive because their brand and compensation are strong enough to attract talent anyway. Most will not.

If you're a developer, the best career insurance is the ability to work remotely. Not because remote work is inherently better for everyone — some people genuinely thrive in offices — but because having the option to work remotely gives you 10x more opportunities than being location-dependent. Build async communication skills. Write well. Be self-directed. Maintain a portfolio that demonstrates independent execution. These skills make you employable anywhere in the world, regardless of what any CEO's memo says.

For emerging-market developers, this is the best hiring environment in history for remote work. The same RTO pressure that's pushing talented developers out of Big Tech is pushing remote-first companies to hire globally. Companies like Deel, GitLab, Zapier, and hundreds of startups are actively hiring in regions they've never recruited from before. If you're in Baku, Istanbul, Tbilisi, or anywhere in the global majority, your competition for remote roles is increasing, but so is the supply of those roles. The net effect is positive. Position yourself well, and the RTO backlash becomes your opportunity.

Decision Framework

Choose to fight for remote if:

• You're a senior developer or above with demonstrable high performance
• Your role is primarily individual-contributor focused (coding, writing, analysis)
• You have a home setup that supports deep work
• You're disciplined about boundaries and don't struggle with isolation
• You're willing to change jobs if your current company won't accommodate you

Choose hybrid if:

• You value in-person interaction for mentorship and team building
• You're early in your career and benefit from osmotic learning (absorbing knowledge by being around experienced people)
• Your role involves significant cross-team collaboration
• You live close enough to an office that commuting isn't a major burden
• Your company implements hybrid thoughtfully (not just "come in and sit on Zoom")

Choose full in-office if:

• You genuinely prefer working in an office (this is valid and more common than remote-work advocates admit)
• You struggle with isolation, distraction, or boundary-setting at home
• You're at a company where in-person culture is a genuine competitive advantage (trading floors, creative agencies, hardware companies)
• The compensation premium or career acceleration of in-office roles at your company justifies it

Choose to relocate and go full remote if:

• You're in an emerging market and can earn 3–5x your local salary remotely
• You have strong written English and async communication skills
• You're self-motivated and can manage your own schedule without external structure
• You're willing to invest in a proper home office setup
• You can handle the social isolation that comes with being the only remote person in your time zone

Sources

• ResumeBuilder — Return to Office Report (2024–2025)
• Founder Reports — Return to Office Statistics
• Archie — Return to Office Statistics
• FMC Group — Working From Home Statistics
• Hubstaff — Remote Work Statistics
• Apollo Technical — Statistics on Remote Workers
• Stack Overflow 2024 Developer Survey — Remote Work
• GitLab — All-Remote Guide
• Stanford / NBER — Hybrid Work Study (Bloom et al.)
• Nature — The Effects of Remote Work on Collaboration (Microsoft Study)

I'm Ismat, and I build BirJob — Azerbaijan's job aggregator that scrapes 90+ career pages so you don't have to. Whether you work from an office in Baku or your kitchen table in Sumgait, we list the roles so you can find them.