The Remote Work Power Shift: When 76% Would Quit But Big Tech Mandates Office Returns

vp_eng_keisha · March 13, 2026, 5:40pm

I’ve been wrestling with a data point that’s been haunting me for weeks now: 76% of workers say they’d quit if forced back to the office full-time. That’s not a fringe opinion—that’s a supermajority. Yet here we are in 2026, watching Amazon mandate 5 days in-office, Meta and Google holding firm at 3, and Dell going full 5-day weeks.

Something doesn’t add up. Either workers don’t have the leverage they think they do, or we’re about to see the largest talent migration in tech history. I’m betting on the former, and that’s what keeps me up at night as a VP of Engineering trying to build an inclusive, high-performing organization.

The Numbers Tell a Story of Shifting Power

Let me lay out what we know:

Worker sentiment is overwhelmingly pro-remote:

76% would quit if remote work disappeared entirely
64% would immediately start job hunting if their hybrid/remote arrangement ended
57% actively considering leaving over RTO mandates

Yet Big Tech isn’t budging:

Amazon: 5 days/week starting January 2026 (73% of AWS employees protested in writing)
Dell: 5 days/week as of March 2025
Meta/Google: Holding firm at 3 days/week minimum
TikTok: Moving to 5 days/week in 2026

And here’s the kicker: 8 out of 10 companies lost talent to RTO mandates. Companies with strict RTO had 13% higher turnover (169% vs 149%). So why are they doubling down?

The Labor Market Reality Check

I think the answer is uncomfortable but clear: the power dynamic has fundamentally shifted.

In 2026, the ratio of job openings to unemployed workers dropped below 1.0 for the first time since the pandemic. Time-to-hire is lengthening because companies can afford to be picky. Entry-level tech roles are down 29% globally.

Meanwhile, despite the “quit threat” rhetoric, actual resignation rates tell a different story. Workers are complaining, protesting internally, even “rage applying”—but most are staying put. Amazon didn’t reverse their mandate. Neither did Dell. The talent exodus everyone predicted? It’s been a trickle, not a flood.

The Nuance No One’s Talking About

Here’s where it gets complicated: not all tech workers have equal leverage.

At my EdTech startup, we’ve stayed remote-first specifically as a recruiting advantage. It’s working—but only for experienced engineers. Senior engineers with track records at FAANG companies? They have options. They can negotiate. They can choose remote-first companies like ours.

But junior engineers? New grads? They’re taking whatever they can get. And increasingly, “whatever they can get” comes with an office mandate.

This creates a dangerous bifurcation:

Top performers still have leverage and can demand flexibility
Everyone else is accepting terms they hate because the alternative is unemployment

What I’m Seeing on the Ground

On my team of 40+ engineers, here’s what the RTO conversation looks like:

For our senior engineers: Remote work is non-negotiable. If we mandated office time, we’d lose them to competitors. They’ve proven they can ship complex systems from anywhere. Their metrics are excellent. Why would I force a change?

For our mid-level engineers: There’s anxiety. They like remote work but feel vulnerable. They’re watching Big Tech mandates and wondering if the window is closing. Some are actively building skills to ensure they have options.

For our junior engineers and recent hires: They’re the most worried. Many moved to cheaper cities during remote work and can’t afford to relocate. Others are first-time remote workers who never experienced office culture and wonder if they’re “falling behind” without the in-person mentorship.

The Question That Keeps Me Up

Is this power shift temporary or permanent?

Part of me thinks this is cyclical. When the labor market tightens again (and it will), companies will rediscover the value of flexibility as a retention tool.

But part of me worries we’re seeing something more fundamental: executives never really bought into remote work. They tolerated it during the pandemic. They experimented during the Great Resignation when they had no choice. But now that labor market pressure has eased, they’re reverting to what feels comfortable: butts in seats, “collaboration” in conference rooms, and the illusion of control that comes from physical presence.

The data says remote work doesn’t hurt productivity. In fact, companies with flexible policies saw 21% higher revenue growth over three years. But data doesn’t always win arguments when powerful people have strong preferences.

The DEI Angle We Can’t Ignore

Here’s what worries me most: RTO mandates disproportionately impact the people we’ve worked hardest to recruit.

Parents (disproportionately women) who need schedule flexibility
People with disabilities who can’t easily commute
People living in lower cost-of-living areas who moved during remote work
First-generation professionals who don’t have family wealth to subsidize expensive city living
International talent who we could never recruit to expensive US offices

We spent years building programs to increase diversity. We eliminated geographic barriers. We proved that talent is distributed but opportunity isn’t. And now we’re… what? Just reversing all that because executives miss hallway conversations?

At my company, we’ve made remote-first a competitive advantage. But I’m honest enough to admit: that strategy only works if we’re in the minority. If everyone goes remote-first again, we lose the differentiation. If everyone mandates RTO, we can’t sustain the stance alone.

So What Do We Do?

I don’t have all the answers, but here’s what I’m thinking:

For individual contributors: Build skills that give you leverage. The engineers who can negotiate remote work are the ones who are indispensable. Prove your value independent of location.

For managers: Track actual productivity data. When executives come with “back to office” mandates, you need metrics showing what you’ll lose. Turnover costs, recruiting timeline impacts, productivity comparisons—make the business case with data.

For executives: Be honest about what you’re optimizing for. If you want people in the office because you prefer it, own that. But don’t hide behind productivity claims the data doesn’t support.

Questions for Discussion

I’m genuinely curious what others are seeing:

Is the “76% would quit” number real or aspirational? Are people actually quitting over RTO mandates, or just complaining?
How do you balance team preferences with business needs? If your team wants remote but your culture/customers/executives prefer on-site, who wins?
Is this power shift permanent? Or are we one recession away from companies begging for talent again and rediscovering remote work benefits?
What’s the end game? Do we settle into a new hybrid equilibrium, or are we headed for a full reversal to pre-pandemic norms?

I really want to hear from other leaders navigating this. What’s working? What’s failing? How are you thinking about the next 1-3 years?

Sources: Founder Reports RTO Statistics, Robert Half Remote Work Trends, IMD Workplace Trends 2026

eng_director_luis · March 13, 2026, 5:42pm

Keisha, this hits home hard. I’m leading 40+ engineers across three offices (Austin, SF, and distributed remote), and our 3-day mandate went into effect last quarter. The data you’re sharing tracks with what I’m seeing—but with a twist that I think makes it even more complicated.

The DEI impact you mentioned is real, and it’s worse than the aggregate numbers suggest.

Our retention challenge isn’t evenly distributed. We’re holding onto senior engineers just fine. But the people we’re losing? Disproportionately:

Latino and Black engineers who moved to lower CoL cities during remote work
Working parents (mostly women) who structured childcare around flexibility
First-generation college grads from El Paso, Fresno, and other cities who can’t afford SF/Austin rents

These are exactly the engineers we spent 5+ years recruiting through SHPE partnerships, targeted university outreach, and deliberate pipeline building. And now we’re… just letting them go? Or forcing them into financial hardship with relocation to expensive markets?

The Geographic Privilege Problem

You mentioned the bifurcation between senior engineers with leverage vs everyone else. I’d add another dimension: geographic privilege.

My engineers in Austin have it easiest—office nearby, relatively affordable city, strong tech scene. If they hate the mandate, they have local options.

My SF-based engineers are stressed but managing—high cost of living, but also tons of alternatives if they want to jump ship.

But my distributed engineers? The ones in Boise, Nashville, Denver? They’re stuck. Either relocate to an expensive market (losing their housing cost advantage), find a new remote job (harder in 2026’s market), or quit tech entirely.

The “quit if remote disappears” statistic feels very different when you’re a single parent in Nashville vs. a 26-year-old in SF with no kids and roommates.

What I’m Tracking (That Executives Aren’t Looking At)

Since the mandate, I’ve been obsessively tracking metrics that tell the real story:

1. Retention by demographics:

White/Asian engineers: 92% retention
Latino engineers: 78% retention
Black engineers: 71% retention
Parents with kids under 5: 73% retention

We just undid half a decade of diversity progress in one quarter.

2. Recruiting pipeline impact:

Time-to-fill for senior roles: +18 days (candidates negotiating remote terms)
Offer acceptance rate for diverse candidates: Down 23%
Geographic diversity of applicants: Collapsed (everyone local now)

3. Mentorship breakdown:
I mentor first-gen Latino engineers through SHPE. Three of my mentees left in the past 4 months—not because they wanted to, but because they couldn’t afford SF on junior engineer salaries after their leases expired. They’re now working in completely unrelated fields.

That’s not a “personal choice.” That’s a structural barrier we eliminated with remote work, then brought back because… why exactly? Hallway conversations?

The Uncomfortable Question: Who’s This Really For?

Here’s what I keep asking in leadership meetings (and getting unsatisfying answers):

If productivity metrics are flat or up during remote work, and retention is worse after RTO mandates, who actually benefits from this policy?

The answers I hear:

“Culture is built in person” (OK, measure it. Show me the culture score improvement.)
“Innovation happens in hallways” (Show me the innovation metrics. Where’s the data?)
“Junior engineers need mentorship” (I’m mentoring more juniors remotely than I ever did in-office. Scheduled 1:1s > random hallway bumps.)
“Real estate commitments” (Finally, honesty. But let’s not pretend this is about productivity.)

What I suspect but can’t prove: executives prefer the illusion of control that comes from physical presence. It feels productive to walk around and see people working. It doesn’t feel productive when people are in Zoom rooms or Slack DMs all day.

But feelings aren’t metrics. And we’re making multi-million dollar retention decisions based on executive comfort, not business outcomes.

The Trap You Identified

You nailed it when you said: “If everyone goes remote-first again, we lose the differentiation. If everyone mandates RTO, we can’t sustain the stance alone.”

This is the prisoner’s dilemma of talent strategy. If a few companies stay remote-first, they get a recruiting advantage. But if everyone goes remote, the advantage disappears.

The problem is we’re not playing a coordination game—we’re following Big Tech because “if Amazon does it, we can too.” That’s not strategy. That’s herd mentality.

What I’m Doing (And What I Wish I Could Do)

What I’m actually doing:

Tracking granular retention and productivity data by team, role, and demographics
Building the business case with real numbers: turnover costs, recruiting delays, diversity impact
Advocating loudly for exceptions (parents, caregivers, people with disabilities, exceptional performers)
Helping engineers navigate remote job searches when they decide to leave

What I wish I could do:

Run a real experiment: Keep 2 teams remote, bring 2 back. Compare productivity, retention, and innovation metrics over 12 months.
Tie executive comp to diversity retention metrics, not just headcount targets
Make the business case using financial services compliance costs—we have secure remote infrastructure for regulatory reasons, why not use it for retention?

To Answer Your Questions

1. Is the “76% would quit” number real or aspirational?

It’s aspirational for most, real for some. The people who can quit (senior engineers, people in high-demand specialties) are quitting. The people who want to quit but can’t (juniors, people with financial constraints, visa holders) are staying and suffering.

2. How do you balance team preferences with business needs?

I’d flip this: what if remote flexibility is a business need? Retention is a business need. Diversity is a business need (especially in financial services where we serve diverse customers). Lower real estate costs are a business need.

The question assumes team preferences and business needs are opposed. What if they’re aligned and we’re just measuring the wrong things?

3. Is this power shift permanent?

I think it’s cyclical, but the cycle might be longer than we hope. If we hit a recession and tech hiring freezes, this could last 3-5 years. That’s long enough to lose an entire generation of diverse talent.

4. What’s the end game?

I’m betting on a messy middle: flexible policies for top performers, mandates for everyone else. Which means we institutionalize a two-tier system where leverage determines your working conditions.

Not great for culture. Not great for equity. But probably where we’re headed unless leadership changes course.

Keisha, I appreciate you naming the DEI impact explicitly. Too many leaders are pretending this is “just” a work arrangement question when it’s fundamentally about who gets to participate in tech.

If you’re tracking metrics on this at your company, I’d love to compare notes. I’m trying to build a retention dashboard that tells the real story, not just the aggregate headcount numbers executives want to see.

product_david · March 13, 2026, 5:43pm

Coming at this from the product/business side, and I have to say: the disconnect between what engineers want and what executives/customers are asking for is creating some really uncomfortable strategic tensions.

Luis, your point about executives wanting the “illusion of control” resonates. But I’ll add a dimension that makes this messier: our enterprise customers are also asking questions about our remote setup.

The Customer Perspective (That No One’s Talking About)

In the past 6 months, I’ve been on 12 sales calls where the customer brought up our team structure unprompted. Here’s what they’re asking:

“How often is your engineering team in the office together?”
“Can we visit your office and meet the team working on our integration?”
“We’re concerned about security with distributed teams—how do you handle that?”
“Your competitor has everyone co-located in Austin—doesn’t that make them faster?”

Now, are these questions fair? Not necessarily. Are they based on actual productivity data? Definitely not. But they’re real, and they’re affecting deal velocity.

I had a $2.3M enterprise deal stall last quarter specifically because the buyer (a large financial institution) had internal concerns about our “distributed team model.” They didn’t say no—they said “we need to think about it.” We eventually closed it, but it took an extra 6 weeks and required our CTO to fly to their office for an in-person security review.

Would that have happened if we were “5 days in-office like the big guys”? I don’t know. But it introduced friction that our competitors didn’t have.

The Investor Pressure Is Real (And Contradictory)

Keisha, you mentioned your EdTech startup staying remote-first as a recruiting advantage. We tried the same thing at our Series B fintech. Here’s what our board said:

Q4 2024: “Remote-first is great! Lower burn rate, access to global talent, distributed resilience—smart strategy.”

Q2 2025: “We’re concerned about culture and execution velocity. Have you considered bringing people together more often?”

Q4 2025: “Your peer companies are implementing RTO mandates. How are you thinking about this? Investors want to see strong culture, and that happens in-person.”

Wait, what? The same investors who praised our capital efficiency are now concerned we’re too distributed?

What changed? Macro environment shifted. Suddenly “growth at all costs” became “prove you can execute efficiently.” And apparently “efficient execution” means… office space and commutes? The logic doesn’t track, but the pressure is real.

The Framework I’m Using (Trying To Use)

As a product person, I try to think about this as a build-vs-buy decision with clear trade-offs:

Remote-First Strategy

Pros:

Recruiting advantage with senior engineering talent
Lower burn rate (office space, perks, geographic salary adjustments)
Geographic diversity in hiring
24/7 follow-the-sun development possible

Cons:

Harder to build culture with new hires
Async communication overhead (slower decisions)
Customer perception challenges in enterprise sales
Investor skepticism in 2026 market

Office-First Strategy

Pros:

Faster synchronous collaboration (in theory)
Easier to build culture and onboard new hires
Customer/investor perception of “seriousness”
Spontaneous innovation (in theory)

Cons:

Retention risk with senior engineers
Higher burn rate (office costs + geographic premium)
Geographic constraints on hiring
Diversity impact (as Luis detailed)

The problem is: these trade-offs aren’t equal across all roles, all teams, or all company stages.

The Nuance By Function

Here’s what I’m seeing across our company:

Engineering: Overwhelmingly wants remote. Productivity metrics support it. Retention suffers with mandates.

Sales: Wants to be remote (because they’re traveling anyway), but customers want to “meet the team” occasionally.

Product: Split. Senior PMs want remote for deep work time. Junior PMs want in-office for osmosis and learning.

Customer Success: Actually performs better remote (more time with customers, less time commuting).

Executive team: Wants everyone in-office because “culture” and “collaboration,” but provides zero metrics to support the claim.

The Question I Keep Asking: What Are We Optimizing For?

Keisha, you asked “how do you balance team preferences with business needs?” I think the question assumes we know what the business needs are. I’m not convinced we do.

Are we optimizing for:

Productivity? (Metrics say remote is fine or better)
Retention? (Remote wins for senior talent)
Recruiting? (Remote wins for engineers, office wins for some execs/customers)
Cost efficiency? (Remote wins)
Culture? (Define culture. Measure it. Then we can talk.)
Customer perception? (Office might win, but is perception reality?)
Investor expectations? (They don’t know what they want either)

The problem is we’re trying to optimize for ALL of these simultaneously, and they conflict. So we end up with incoherent policies that make everyone equally unhappy.

The “Hybrid” Trap

Our company tried hybrid. We mandated 2 days/week in-office. Here’s what happened:

Week 1-2: People showed up. Complained about commutes but complied.

Week 3-8: Attendance dropped to ~60% on mandated days. No enforcement.

Week 9: Leadership “strongly encouraged” compliance. Attendance jumped to 85%.

Week 10-12: Back to ~60%. Some people coming Mon/Tues, others Wed/Thurs. Offices empty some days, overcrowded others.

Week 13: Leadership gave up on enforcement. Hybrid became “do whatever you want” again.

The result? We got the worst of both worlds.

We still pay for office space (fixed cost)
We still have distributed team communication patterns (because not everyone is there on the same days)
We lost the recruiting advantage of being “remote-first”
We annoyed people who wanted full remote AND people who wanted full in-office

Hybrid in theory is a compromise. Hybrid in practice is just expensive and confusing.

What I Wish We’d Measure (But Don’t)

If we’re going to make this a data-driven decision, let’s actually measure:

1. Productivity by work mode:

Feature velocity (story points, cycle time)
Bug rates and production incidents
Customer satisfaction scores
Engineering engagement scores

2. Retention and recruiting impact:

Offer acceptance rates (remote vs hybrid vs on-site)
Turnover by level, function, and demographics
Time-to-fill for open roles
Quality of hire (performance reviews at 6/12 months)

3. Business outcomes:

Deal velocity (does remote affect sales cycles?)
Customer satisfaction (do customers care?)
Investor sentiment (actual funding impact, not vibes)

4. Cost impact:

Real estate costs vs geographic salary adjustments
Turnover costs (recruiting, onboarding, lost productivity)
Productivity gains/losses quantified

The problem is most companies (including mine) don’t have good instrumentation for this. So we make million-dollar decisions based on executive intuition and “what Amazon is doing.”

My Uncomfortable Prediction

I think we’re headed toward exactly what Luis predicted: a two-tier system where leverage determines your working conditions.

Senior engineers, in-demand specialists, top performers: Negotiate remote or hybrid on their terms
Everyone else: Take the mandate or leave

This is bad for:

Culture: Creates resentment between “remote privileged” and “office required” employees
Diversity: Disproportionately impacts exactly the people Luis mentioned
Morale: Nothing kills morale like visible unfairness

But it’s efficient from a business perspective. You keep the people you can’t afford to lose happy, and you enforce compliance from everyone else. Cynical? Yes. Likely? Also yes.

To Answer Keisha’s Questions:

1. Is the “76% would quit” number real or aspirational?

It’s real for top 25%, aspirational for everyone else. And companies know this. They’re willing to lose the bottom 75% if it means they can mandate compliance for the majority.

2. How do you balance team preferences with business needs?

We don’t. We pretend to balance them, but really we’re following whatever Big Tech does because it’s “safe.” No one gets fired for copying Amazon’s policy, even if it’s wrong for our company.

3. Is this power shift permanent?

Permanent-ish for 3-5 years. Next talent crunch (and there will be one), companies will rediscover remote as a recruiting tool. But we might lose a generation of talent in the meantime.

4. What’s the end game?

Messy hybrid policies with inconsistent enforcement, a two-tier system based on leverage, and continued tension between what workers want and what executives feel comfortable with. Not satisfying, but probably realistic.

The frustrating part is we have all the data we need to make this decision rationally. We just… aren’t using it. Instead we’re making decisions based on vibes, investor pressure, and copying whatever Amazon does.

As a product person, if I shipped features this way—no user research, no metrics, just “let’s do what Google does”—I’d be fired. But apparently it’s fine for workforce strategy.

mobile_maria · March 13, 2026, 5:44pm

Reading this discussion from São Paulo, and I need to add a reality check: the “76% would quit” statistic and the entire RTO debate is very US-centric. The global picture is completely different.

Geographic Privilege in the Remote Work Debate

Luis, you mentioned geographic privilege within the US (SF vs Nashville). Let me extend that to the global context, because what’s happening at Uber right now illustrates the problem.

Uber’s RTO mandate is global, but the leverage is not.

When our 3-day office mandate rolled out earlier this year:

SF/NYC engineers: Complained loudly. Some quit and found remote jobs at startups. Some negotiated exceptions. Most complied but with leverage to push back.

São Paulo engineers (my team): Showed up 3 days/week. Didn’t complain publicly. Didn’t negotiate exceptions. Why? Because the alternative isn’t “find another remote job”—it’s “lose access to US-level compensation and US tech experience.”

Bangalore/Hyderabad engineers: Same story. Office mandate = compliance. The leverage just isn’t there.

The “quit threat” assumes you have alternatives. For engineers in emerging markets, Uber/Google/Meta ARE the alternatives. You don’t leave Big Tech for a remote startup—you leave Big Tech to start your own company or take a massive pay cut for local work.

The Data No One’s Tracking: Performance by Location

I lead mobile platform engineering across iOS and Android, with teams in SF, São Paulo, and Hyderabad. Here’s what the RTO mandate did to our metrics:

Before mandate (fully remote, Q4 2025):

Sprint velocity: 92 story points/sprint (average across all teams)
Incident rate: 2.1 P0 incidents per month
Pull request merge time: 18 hours median
Team satisfaction score: 8.2/10

After mandate (3 days in-office, Q1 2026):

Sprint velocity: 89 story points/sprint (-3.3%)
Incident rate: 2.4 P0 incidents per month (+14%)
Pull request merge time: 22 hours median (+22%)
Team satisfaction score: 6.8/10 (-17%)

What happened? We lost asynchronous collaboration advantages and gained nothing in synchronous productivity.

My iOS team in SF, Android team in São Paulo, and platform team in Hyderabad used to follow the sun. A pull request opened in SF got reviewed in São Paulo during their morning, then handed to Hyderabad for their workday. 24/7 progress without anyone working nights.

Now? Everyone’s in office on the same 3 days (Mon/Tues/Weds), which means:

SF team is in office when São Paulo is ending their day
Hyderabad is in office when no one else is available for sync
We’ve recreated all the timezone pain of distributed work WITHOUT keeping the async benefits

We traded 24/7 productivity for… what exactly? “Collaboration”? My teams are on different continents. They weren’t going to whiteboard together anyway.

The Mobile-Specific Angle

For mobile engineering specifically, the RTO mandate makes even less sense:

Mobile development is inherently distributed:

App Store review happens in Cupertino (Apple)
Google Play review happens in Mountain View (Google)
Our users are global (190+ countries)
Our testing happens on real devices in multiple geographic regions
Our on-call rotation is 24/7 because incidents don’t respect timezones

Being in an office in São Paulo doesn’t make me closer to App Store review. It doesn’t help me debug an issue affecting users in Indonesia. It just adds 90 minutes of commute to my day and removes 90 minutes I could spend shipping features.

The performance data backs this up:

I tracked mobile app metrics before/after RTO:

App crash rate: No change (still 0.08%)
Feature release velocity: Slightly slower (2.1 weeks per release vs 1.9 weeks)
App Store rating: No change (4.7 stars)
User-reported bugs: Slight increase (+8%)

Office presence didn’t improve any mobile-specific metrics. But it did increase commute time, decrease deep work hours, and hurt team morale.

The Bandwidth Reality (That SF Engineers Don’t Think About)

Here’s something David touched on with customer concerns about “distributed team security,” but missed: the infrastructure assumption.

US engineers assume:

Everyone has gigabit fiber at home
Everyone has backup power
Everyone has a quiet, dedicated workspace
Everyone has high-end hardware

In São Paulo? My home internet is 100 Mbps (good by Brazilian standards, but not SF-level). Power outages happen. My apartment is smaller. My MacBook Pro is the same, but my home monitor setup is what I could afford locally.

Does that mean I’m less productive at home? Actually, no—because I adapted. I work async. I download large files during off-peak hours. I time my deep work for when power is stable.

But the RTO mandate assumes the office is better than home for everyone. For SF engineers with expensive rent and long commutes, maybe home is better. For São Paulo engineers, the office actually has more reliable infrastructure.

Yet the policy is the same for everyone. One-size-fits-all mandate for geographically diverse team = bad policy.

Luis’s DEI Point, Extended Globally

Luis documented the DEI impact in the US (Latino, Black, women, parents). Let me add the global dimension:

The RTO mandate disproportionately impacts:

Engineers in lower cost-of-living countries who moved even further from the office during remote work
Women in countries with less robust childcare infrastructure (which is most countries outside the US)
Engineers with disabilities in countries with poor accessibility infrastructure
Engineers who joined during remote work and never lived near an office

In São Paulo, several engineers on my team moved to smaller cities (Curitiba, Florianópolis) during remote work. Lower cost of living, better quality of life, closer to family. Now they’re forced to either:

Relocate back to São Paulo (expensive, disruptive)
Commute 2-3 hours each way on mandated days (unsustainable)
Quit and lose Uber compensation (huge financial hit)

Most are choosing option 2 and burning out. That’s not a “work preference”—that’s a forced choice between financial security and personal wellbeing.

To Answer Keisha’s Questions (From a Global Lens):

1. Is the “76% would quit” number real or aspirational?

It’s a US statistic reflecting US market conditions. Globally, the number is much lower because leverage is much lower. Engineers in emerging markets can’t credibly threaten to quit because alternatives are limited.

2. How do you balance team preferences with business needs?

What if geographic context is a business need? My São Paulo team is cost-efficient, highly productive, and serves the Latin American market better than a US-based team could. Forcing them into an office doesn’t improve business outcomes—it just makes them less happy.

3. Is this power shift permanent?

For US engineers, probably cyclical. For global engineers, the power imbalance was always there. Remote work briefly leveled the playing field (my São Paulo team could compete directly with SF engineers for the first time). RTO mandates restore the geographic hierarchy.

4. What’s the end game?

Two-tier system globally:

Tier 1: US/Europe engineers with leverage to negotiate remote/hybrid
Tier 2: Emerging market engineers who comply or leave

This isn’t new. It’s just a return to pre-pandemic norms where geography determined opportunity.

What I’m Doing (And What I Wish Leadership Would Understand)

What I’m actually doing:

Tracking granular productivity metrics by location and work mode
Advocating for location-specific policies (let São Paulo team stay remote if metrics support it)
Building async-first collaboration practices (because timezones aren’t going away)
Helping my team navigate burnout from unsustainable commutes

What I wish leadership would understand:

Mobile engineering doesn’t benefit from physical proximity. We’re shipping apps to global users, not building hardware in a lab.
Geographic diversity is a feature, not a bug. My distributed team ships 24/7. Co-located teams ship 8 hours/day.
One-size-fits-all mandates are lazy. SF and São Paulo have different realities. Policy should reflect that.
The “quit threat” only works if you have leverage. Stop pretending global engineers have the same negotiating power as US engineers.

I appreciate this discussion because it’s naming the tensions that most companies won’t acknowledge. But let’s not forget: the US remote work debate is a privileged conversation. Most of the world’s engineers never had the option to quit over office mandates.

The real question isn’t “is talent leverage shifting back to employers?” It’s: who ever had leverage in the first place, and who are we leaving behind?

priya_security · March 13, 2026, 5:45pm

Jumping in from the security side, and I want to challenge an assumption that’s embedded in this whole debate: the idea that distributed teams are inherently less secure than co-located teams.

David mentioned customers asking about security concerns with distributed teams. I’ve heard this too. And frankly, it drives me crazy because it’s security theater, not actual security analysis.

The RTO-as-Security-Argument Doesn’t Hold Up

Let me be blunt: if your security model depends on everyone being in the same physical office, your security is already broken.

Here’s why:

1. The office perimeter is not a security boundary.

Modern threats don’t care about physical proximity:

Phishing attacks work just as well on office wifi as home wifi
Supply chain compromises affect SaaS tools regardless of where employees sit
Insider threats exist whether someone is in SF or São Paulo
Cloud infrastructure means production systems aren’t “in the office” anyway

2. Remote work actually forced better security practices.

When everyone went remote in 2020, companies that survived learned to implement:

Zero-trust architecture (verify every request, not just office network access)
Hardware security keys (MFA that actually works)
Endpoint detection and response (visibility into every device, not just office machines)
Encrypted communication by default (because everything is now “untrusted network”)

Those are all improvements over the old “trusted office network” model. Going back to office-first doesn’t mean you can revert these—it means you need to maintain them AND deal with office security too.

3. The real security risks are organizational, not locational.

In my experience doing security architecture at Auth0, Okta, and now fintech, the biggest risks are:

Developers with excessive production access (doesn’t matter where they sit)
Lack of automated security scanning in CI/CD (unrelated to office vs remote)
Poor incident response processes (actually harder to coordinate when everyone’s in different meeting rooms)
Shadow IT and ungoverned SaaS adoption (happens in-office too)

None of these are solved by RTO mandates. In fact, some are worse in office environments because of the false sense of security.

Maria’s Bandwidth Point, From a Security Lens

Maria mentioned infrastructure assumptions (gigabit fiber, backup power). Let me extend that to security:

The office is not inherently more secure than home.

In São Paulo, Brazil’s office security might be better than Maria’s home (backup power, better internet). But in other locations? I’ve seen:

Office wifi with weak WPA2 passwords shared across 200 people
Cleaning crews with physical access to unlocked laptops overnight
“Visitor” networks that aren’t actually isolated from corporate networks
Open floor plans where anyone can shoulder-surf anyone else’s screen

Meanwhile, a properly configured home setup:

Dedicated work device with full disk encryption
Hardware security key for MFA (can’t be phished)
Separate network segment for work devices (or VPN to corporate network)
Physical security controlled by one person (you), not shared with 500 office workers

Which is more secure? It depends entirely on the configuration, not the location.

The Financial Services Compliance Excuse

Luis mentioned using financial services compliance to justify remote work. Let me flip that: compliance requirements actually support remote work, if done properly.

I work in fintech. We’re regulated. Here’s what compliance actually requires:

SOC 2 Type II: Controls for data access, not physical location. Remote work is fine if you have:

Endpoint management and monitoring
Access logging and review
Background checks for employees
Encrypted data at rest and in transit

PCI DSS: Card data security. Requires:

Network segmentation (regardless of office vs home)
Regular security testing (can be done remotely)
Access controls based on role, not location

GDPR/CCPA: Privacy regulations. Require:

Data processing agreements
Data minimization and access controls
None of this requires physical proximity

The dirty secret? RTO mandates make some compliance harder, not easier.

Example: Audit logs. In a fully remote setup, everything is logged (every login, every access, every change). In an office, you have:

Physical access that’s not logged (who walked up to whose desk?)
Whiteboard discussions that aren’t captured (what PII was written on that board?)
Shoulder surfing and verbal sharing that bypasses access controls

From a compliance perspective, remote work forces you to build audit trails. Office work lets you skip them because “trust me, we talked about it in the hallway.”

What I Wish Leadership Would Understand About Security & RTO

1. “Office = secure” is outdated thinking.

The perimeter security model died in 2015. If you’re still designing security around “trusted office network,” you’re vulnerable whether people are remote or not.

2. Remote work can be MORE secure if done right.

Zero-trust, hardware MFA, EDR, SIEM—these are all technologies that work better in remote environments because they force you to verify everything, not assume trust based on network location.

3. Security concerns about remote work are often proxies for other fears.

When executives say “we’re concerned about security with distributed teams,” what they often mean is:

“We don’t trust employees we can’t see”
“We don’t have visibility into what people are doing”
“We’re afraid of losing control”

Those are management problems, not security problems. And mandating office presence doesn’t solve them—it just papers over the lack of trust with physical proximity.

The Real Security Trade-offs

That said, let me be fair: there ARE legitimate security considerations for remote vs office work.

Office advantages:

Easier to enforce physical security for truly sensitive systems (airgapped networks, HSMs, etc.)
Faster incident response if everyone’s physically co-located
Easier to do security training and awareness in person

Remote advantages:

Forces implementation of zero-trust architecture
Better audit trails (everything is logged)
Reduced physical attack surface (no walk-up access to workstations)
Geographic distribution reduces single-point-of-failure risk (fire, natural disaster, etc.)

For most companies, remote advantages outweigh office advantages IF you invest in proper security infrastructure.

For companies handling truly sensitive data (defense contractors, critical infrastructure), office work might be necessary—but that’s <1% of tech companies, not the majority using “security concerns” as RTO justification.

To Answer Keisha’s Questions (Security Lens):

1. Is the “76% would quit” number real or aspirational?

From a security hiring perspective, it’s real. I recruit security engineers. They have leverage because there’s a massive shortage. If I mandated office work, I’d lose candidates to competitors who don’t.

Security talent shortage + RTO mandate = retention disaster.

2. How do you balance team preferences with business needs?

Security IS a business need. And proper security works just fine remotely. If leadership says “office for security reasons,” ask them to document specific threats that office presence mitigates. Most can’t.

3. Is this power shift permanent?

For security roles? No. The talent shortage is structural and long-term. We’ll always have leverage. For other roles, probably cyclical per David/Luis’s predictions.

4. What’s the end game?

I hope we end up with location-agnostic security practices—because that’s the only model that actually works in 2026. But I fear we’ll get two-tier security: robust for distributed teams, lazy for co-located teams who think proximity equals safety.

Final thought: If your company is using “security concerns” to justify RTO, ask them to do a threat model. Document specific threats, mitigations, and why office presence reduces risk.

Most companies won’t do this because the real driver isn’t security—it’s executive preference for physical proximity. And that’s fine! Just be honest about it instead of hiding behind security as justification for policies that don’t actually improve security posture.

/End security rant