The VP of Engineering announced the return-to-office mandate in an all-hands meeting: four days a week in the office, starting next quarter. The company had been fully remote for three years. Now, with a new CEO and a lease on a shiny new headquarters, the policy was changing.
"This is about collaboration and culture," the VP explained. "We've lost something being remote. Being together will make us stronger."
Within three months, 23% of the engineering team had resigned. The departures weren't evenly distributed. The junior engineers mostly stayed—they were newer, had shorter commutes, and saw value in in-person mentorship. But the senior engineers left in droves. Staff engineers. Tech leads. The people with the most options and the most institutional knowledge.
"We knew we'd lose some people," the CEO told the board. "We didn't expect to lose our best people."
The company had stumbled into one of the most contentious issues in tech: return-to-office mandates and their impact on engineering teams. After tracking RTO outcomes across 75+ companies at SmithSpektrum, I've seen the data on what actually happens when companies change their location policies[^1]. The story is more nuanced than either the RTO advocates or the remote work true believers usually admit.
The Current Landscape
The tech industry has largely settled into a hybrid equilibrium, though what "hybrid" means varies enormously.
About 15% of tech companies remain fully remote—no offices at all, or offices used as optional collaboration spaces. Another 20% are remote-first, meaning office attendance is optional and the company's systems and culture are designed for distributed work. The largest chunk, about 40%, describe themselves as hybrid with required office days, typically two to three days per week. And the remaining 25% have moved to office-first policies with four or five days expected.
Company size matters. Startups under fifty employees tend toward remote-first or flexible hybrid—they're competing for talent against larger companies and flexibility is a cheap benefit to offer. Growth-stage companies between fifty and five hundred employees have more variation, often with hybrid policies that aren't strictly enforced. Large tech companies over five hundred employees have increasingly moved toward more office time, with several high-profile mandates making news over the past two years.
Geography matters too. San Francisco companies face particular pressure around RTO because so many employees moved away during the pandemic and can't easily return. New York companies have found hybrid more natural, perhaps because the city itself offers reasons to be present. Austin, Denver, and Miami have absorbed tech workers fleeing coastal cities and have built ecosystems around remote-friendly work.
The Productivity Debate
Both sides of the RTO debate claim productivity data supports their position. Both are partially right and partially wrong.
| Policy Type | Employee Reception | Attrition Risk | Productivity Impact |
|---|---|---|---|
| Full remote | Highly positive | Lowest | Varies by team |
| Hybrid flexible | Positive | Low | Generally positive |
| Hybrid mandated (2-3 days) | Mixed | Medium | Neutral to negative |
| Full return | Negative | Highest | Often negative |
| "Office-first" | Depends on culture | Medium-High | Context-dependent |
Stanford's research on remote work found that remote workers were about 13% more productive than their office counterparts—but this was measured in specific call center work with defined tasks and clear output metrics. Engineering work is harder to measure. Microsoft's internal studies found that hybrid work increased collaboration breadth (talking to more people) but reduced collaboration depth (fewer close working relationships). Neither finding cleanly translates to "productive" or "unproductive."
When I ask engineers directly, most report feeling more productive working remotely, at least for certain types of work. Deep individual work—writing code, designing systems, debugging complex problems—benefits from uninterrupted focus time. Remote work protects that time in ways that open offices never did.
But collaborative work often benefits from presence. Brainstorming sessions, complex problem-solving with multiple people, spontaneous discussion when you notice someone stuck—these happen more easily when people share physical space. The quick question you'd ask by leaning over is harder when it requires scheduling a call or hoping someone responds on Slack.
The honest answer is that productivity impact varies by role, individual, and work type. For senior engineers doing mostly independent work, remote often wins. For junior engineers who need mentorship and osmotic learning, presence often wins. For teams in the design phase where ideas bounce around, presence often wins. For teams in the execution phase where coordination is needed but the work is clear, remote often wins.
Any claim that "remote is more productive" or "office is more productive" as a blanket statement is wrong. The question is what work you're optimizing for and what your team actually needs.
The Attrition Reality
This is where the data becomes clearest: RTO mandates cause significant attrition, and the attrition is not random.
When companies shift from remote to hybrid with two required days, typical attrition spikes are 5-10% above baseline. Move to three days required, and you're looking at 10-15%. Full return to office after extended remote work produces attrition spikes of 15-25%. These aren't subtle effects; they're major workforce disruptions.
More concerning than the numbers is who leaves. Senior engineers with more experience have more options—they can easily find roles at remote-friendly companies. Parents and caregivers who've restructured their lives around remote work find office requirements particularly burdensome. Engineers who relocated during the pandemic, trusting assurances that remote work was permanent, face impossible choices. High performers who can command multiple offers have the most leverage to demand what they want.
The result is adverse selection: the engineers who can most easily find other jobs are the ones most likely to leave. The ones who stay are disproportionately those with fewer options. This isn't universally true—some excellent engineers prefer the office—but it's a statistical pattern that repeats across companies.
The hiring impact compounds the attrition impact. Companies requiring full office attendance see candidate pools 50-70% smaller than remote-first companies for equivalent roles. This means longer hiring timelines, more compromises on candidate quality, and often higher compensation to attract the smaller pool of people willing to accept the constraint.
The Arguments for Office Time
Understanding why companies push for RTO—even knowing the costs—is essential for thinking clearly about this issue.
The collaboration argument has merit, though it's often overstated. Some collaboration genuinely is easier in person: the design session at a whiteboard, the working session where you need rapid iteration, the debugging session where pointing at the screen matters. Remote tools have improved, but they haven't fully replicated the bandwidth of in-person interaction.
The culture argument has merit, particularly for building relationships. Culture transmitted through documentation and Slack channels is different from culture absorbed through daily presence. New hires especially can struggle to understand "how things work here" when they've never seen informal behavior modeled.
The onboarding argument is genuinely strong. Junior engineers and new hires learn faster in person. They can ask quick questions without formal scheduling. They observe how experienced people work. They build relationships that make later collaboration easier. Remote onboarding is possible, but it requires much more deliberate design to work well.
The serendipity argument—that random encounters lead to valuable ideas—is probably real but hard to measure. Some innovations do come from unexpected conversations. Whether this justifies the overhead of office time is harder to say.
The real-estate argument is rarely stated but often operative: companies have expensive leases, and leadership feels pressure to justify that expense. This isn't a good reason for RTO, but it's an honest one that companies rarely acknowledge.
The Arguments for Remote
The talent pool argument is unanswerable: you can hire from anywhere versus hiring only from people willing to commute to your office. Geographic flexibility also enables diversity that local hiring can't match—talent exists everywhere, but opportunity hasn't been evenly distributed.
The productivity argument, particularly for deep work, holds up in practice. Engineers consistently report accomplishing more in focused remote time than in fragmented office time. The meeting interruptions, desk drop-ins, and background noise of offices are real costs.
The employee satisfaction argument shows up in every survey: most engineers prefer some degree of flexibility. Not all want to be fully remote, but very few want full-time office. The preference isn't just about convenience—it's about autonomy, about being treated as an adult who can manage their own work.
The cost argument is straightforward: remote work is cheaper for companies (less real estate) and for employees (no commute costs, no need to live in expensive metro areas).
Making the Decision
There is no policy that optimizes for everything. You're choosing trade-offs, not finding the right answer.
If you optimize for collaboration and culture, you'll require more office time. You'll pay for that in attrition, hiring difficulty, and reduced talent pool. But you'll get more serendipitous interaction and easier onboarding.
If you optimize for talent pool and flexibility, you'll allow full remote. You'll pay for that in harder culture transmission, more deliberate collaboration requirements, and challenges with junior development. But you'll access talent you couldn't otherwise reach and satisfy employee preference.
Most companies end up somewhere in the middle—hybrid policies that try to capture some benefits of both while accepting some costs of both. The risk of the middle is pleasing no one perfectly: remote advocates resent required days, office advocates find it insufficient, and the overhead of supporting both modalities is real.
Whatever you choose, be honest about the trade-offs. Don't pretend that RTO is purely about productivity when the real estate costs are driving it. Don't pretend that remote is cost-free when collaboration suffers. And don't promise things you won't deliver—engineers who were promised permanent remote work and then faced RTO mandates are the angriest, most likely to leave, and most likely to badmouth your company.
If You're Implementing RTO
If you've decided to require more office time, execution matters enormously.
Give long notice periods. Engineers who need to relocate, who've arranged childcare around remote work, or who need to renegotiate their living situations need time. Three months minimum; six months is better. Short notice feels punitive and maximizes resentment.
Honor commitments made. If you hired people with promises of remote work, grandfather them. Yes, this creates complexity. But broken promises destroy trust and create legal risk. The engineers you hired remote will leave anyway if you force them back; letting them stay remote at least maintains the relationship.
Explain the rationale honestly. "We believe collaboration will improve" is a legitimate reason. "We want to justify our real estate" is honest, if unpopular. "Because I said so" is the worst—it signals that leadership doesn't respect engineers enough to provide reasoning.
Make the office worth coming to. If engineers commute forty-five minutes to sit on video calls in an open floor plan, you've failed. Design office days around the things that benefit from presence: collaborative sessions, team meetings, social events. Protect remote days for focus work.
Don't monitor badge swipes. Treating adults like children to be surveilled poisons the culture you're trying to build. If you can't trust engineers to show up when expected without checking, you have larger management problems.
If You're Staying Remote
Staying remote or remote-first has its own requirements for success.
Invest heavily in onboarding. The osmotic learning that happens naturally in offices must be deliberately designed in remote environments. Structured buddy programs, explicit documentation, scheduled shadowing sessions, and frequent check-ins during the first months.
Create synchronous collaboration time. Pure async works for some teams, but most need some regular video time—for building relationships, for complex discussions, for the bonding that makes async collaboration feel human rather than transactional.
Bring people together periodically. Annual or quarterly off-sites, team gatherings, regional meetups—some physical presence creates the relationship foundation that makes remote work sustainable. Pure remote with no in-person time is harder to sustain.
Be deliberate about culture. Document your values and practices explicitly. Create rituals that maintain connection. Recognize that culture transmission requires active effort rather than passive absorption.
Support junior development specifically. Remote work is harder for people early in their careers. More structured mentorship, more frequent check-ins, more explicit feedback, more opportunities to learn through pairing. Don't assume junior engineers will figure it out the way seniors can.
The company that lost 23% of its engineering team to RTO? They eventually adjusted. They reduced the requirement to three days, created grandfather clauses for employees hired remote, and offered relocation assistance for those who'd moved during the pandemic.
The attrition slowed. The hiring improved. But the engineers they'd already lost—the staff engineers, the tech leads, the people with the deepest institutional knowledge—were gone. They'd found remote roles elsewhere within weeks of resigning.
"The policy change was probably necessary," the VP of Engineering admitted a year later. "But we implemented it terribly. We treated it as a policy to announce rather than a change to manage. We lost people we didn't need to lose."
RTO policy is a major strategic decision with real talent implications. Make it deliberately, implement it carefully, communicate it honestly, and understand that whatever you choose, you're choosing trade-offs, not solutions.
References
[^1]: SmithSpektrum RTO impact tracking, 75+ companies, 2022-2026. [^2]: Stanford, "Working from Home Research," Bloom et al. [^3]: Microsoft Work Trend Index, 2024-2025. [^4]: Blind, "Return to Office Surveys," 2024-2025.
Navigating RTO policy decisions? Contact SmithSpektrum for talent strategy and retention guidance.
Author: Irvan Smith, Founder & Managing Director at SmithSpektrum