The best research says remote and hybrid work does not lower overall productivity, and it cuts resignations: Nicholas Bloom's 1,600-person hybrid trial found equal productivity and promotion rates (Stanford) and 33% fewer resignations (NBER w30292). The one real cost shows up in an NBER study of software engineers specifically: sitting near teammates raises coding feedback, mostly for junior engineers, while seniors write less code (Emanuel, Harrington and Pallais, NBER w31880).
The loudest argument for forcing engineers back to the office is productivity. The evidence doesn't support it as a blanket rule.
Key Takeaways
- A controlled study found home work produced a 13% productivity increase (Bloom, Ctrip experiment).
- A 1,600-person hybrid trial found remote workers as productive and as promotable as office peers (Stanford), with resignations down 33% (NBER).
- The variable that decides remote output is management quality, not desk location.
- For software engineers specifically, proximity helps juniors get more feedback, at the cost of less code from seniors (NBER w31880).
What the Research Actually Found
In an early controlled experiment, employees who worked from home showed a 13% performance increase, and their attrition rate halved, as Stanford's Nicholas Bloom reported. A later, larger study of more than 1,600 workers found resignations fell by 33% (NBER working paper), with hybrid employees just as productive and as likely to be promoted as office-based peers (Stanford).
That last number is the one engineering leaders should sit with. A third fewer resignations is a massive saving when replacing a developer costs a multiple of their salary.
What the NBER Software Engineer Study Found
The study most engineering leaders are looking for is "The Power of Proximity to Coworkers" by Natalia Emanuel, Emma Harrington and Amanda Pallais (NBER working paper 31880). They followed software engineers at a Fortune 500 company from 2019 to 2024, using the 2020 office closures and later return-to-office mandates to compare teams that sat together with teams split across buildings.
Sitting near teammates increased coding feedback by 18.3% and improved code quality. The gains went mostly to less-tenured and younger engineers. Experienced engineers wrote less code when they sat near their team, because they spent that time helping.
So the honest reading is narrower than either side of the office debate likes. Remote works well for senior engineers who already know the codebase and the craft. Juniors need deliberate feedback loops, in person or not: code review with real comments, pairing, and someone whose job includes teaching them.
Remote roles for senior engineers. That is also why Ruzora only hires experienced engineers for remote work with US teams. If that is you, see the open Fullstack TypeScript Engineer (React + Node), Python Backend Engineer (Django / FastAPI) and Frontend Engineer (React + Next.js) roles.
Why "Productivity" Was Never the Real Issue
The honest read of the evidence is that location barely moves productivity in either direction. What moves it is how the work is run: clear goals, written context, real-time collaboration when it's needed, and trust measured by output. A badly managed office team underperforms a well-managed remote one every time.
| Factor | Drives output? |
|---|---|
| Office vs remote location | Barely |
| Clear goals + written context | Strongly |
| Manager trust (output, not hours) | Strongly |
| Timezone overlap for collaboration | Strongly |
This is why we argue that timezone overlap matters far more than whether someone is in an office, and why how you manage a distributed team decides the outcome.
What It Means for Hiring
If location doesn't cost you productivity for experienced engineers, the case for paying a US premium purely to have them in a room weakens fast. Senior nearshore engineers, working your hours and managed well, are the group the research says does fine remotely. See available engineers.
Frequently Asked Questions
Does remote work hurt productivity?
The best controlled research says no. Bloom's studies found a 13% gain in one experiment and equal productivity in a large hybrid trial, with sharply lower attrition. For software engineers, an NBER study found juniors get more feedback in person, while seniors write more code remotely.
Then why do companies push return-to-office?
Often for control or real-estate reasons rather than evidence. The data shows management quality, not location, is what drives output.
How do I keep a remote team productive?
Clear goals, written context, trust measured by output, and enough timezone overlap for real-time collaboration. Those beat office mandates.
The Bottom Line
The productivity argument against remote work doesn't survive contact with the research. Run the team well and remote holds or improves output while keeping people longer. That's an argument for hiring the best senior talent wherever it is, not for filling a room.
Engineers: Ruzora hires senior engineers from LATAM for fully remote roles with US teams. See the open fullstack TypeScript, Go backend and engineering manager roles.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
