Key Takeaways
- Return-to-office mandates do not mean remote work has disappeared: the evidence shows remote, hybrid, and in-person engineering work coexisting.
- Fully remote and hybrid are different arrangements. Neither label tells you which countries you can work from or what travel is required.
- Evaluate productivity, employee satisfaction, and retention separately rather than treating any one of them as proof of the others.
- Before accepting an offer, get location expectations, time-zone overlap, travel requirements, and policy-change procedures in writing.
Remote work is likely to remain a meaningful option for software engineers, even as some employers require more office attendance. The share of software postings that mention remote or hybrid work has been slipping since 2023; our software job market tracker charts it monthly. That is our reading of the developer survey, hiring, and research evidence—not a prediction that every employer will offer it or that finding a remote job will be easy.
2026 update: This edition replaces sweeping predictions with dated evidence, distinguishes remote from hybrid work, and adds practical questions for evaluating an offer.
Is Remote Work Going Away?
No—but “remote work exists” and “remote jobs are plentiful” are different claims.
In Stack Overflow’s 2026 work-setting results, 34.8% of the 24,602 respondents to that question selected remote, while 17.6% selected in-person. The survey reported hybrid arrangements and employee-choice arrangements separately. Its methodology describes recruitment through Stack Overflow’s sites and email list, so treat these as findings about a self-selected developer sample, not a representative estimate of every software engineer.
Return-to-office policies are also real. Amazon announced a five-day office expectation effective January 2, 2025, with exceptions for extenuating circumstances and approved remote arrangements. Its April 1, 2026 HQ2 update continued to describe that five-day policy.
Amazon’s original memo also acknowledged occasional remote work before the pandemic. Occasional permission to work from home is not the same as a standing remote or hybrid arrangement. The useful question is what your prospective team actually requires—not whether the entire industry has chosen one model.
Remote vs Hybrid Work: Know What the Offer Means
Use these working definitions when comparing roles. Then ask the employer to spell out its own terms.
| Arrangement | Attendance expectation | What to verify |
|---|---|---|
| Fully remote | No routine office attendance. | Required offsites, onboarding visits, customer travel, and approved work locations. |
| Hybrid | A recurring mix of office and remote work. | Required days, designated office, team overlap, and who controls the schedule. |
| Office-first | The office is the normal workplace; remote days are exceptions. | Whether flexibility is documented or needs individual approval. |
| Remote within a geographic region | Remote work restricted to specified countries, states, or regions. | Whether your residence qualifies and whether relocation needs approval. |
The last row is a geographic restriction, not a separate attendance model. A role can be fully remote and still exclude your location: when reviewed for this update, GitLab’s Intermediate Backend Engineer, AMER listing specified remote work in Canada and the United States. One listing establishes an opportunity, not the size of the market.
What Is the Future of Remote Work?
The sensible expectation is continued variation, not a single industry-wide destination. Remote work gives employers another way to organize teams and gives candidates another factor to weigh alongside compensation, learning, and stability. Whether a particular arrangement succeeds deserves a more specific answer than “the office is obsolete” or “everyone must return.”
What the Productivity Evidence Actually Says
A 2024 randomized trial at Trip.com assigned 1,612 employees to either five office days or a hybrid schedule allowing two home days. The six-month experiment, conducted in 2021–2022, found improved satisfaction and a one-third reduction in quitting, without damage to performance grades. That supports the tested hybrid arrangement—not every fully remote setup.
There is evidence for office-related benefits too. The Power of Proximity to Coworkers, revised in June 2026, studied software engineers at one Fortune 500 firm. It found that proximity increased coding feedback and improved code quality, with gains concentrated among younger and less-tenured engineers; experienced engineers wrote less code when near teammates.
These findings are not contradictory. Individual output, mentoring, retention, and team performance are different outcomes. Neither study supplies a universal answer for your team.
To evaluate a location policy, choose measures before changing it: delivery time, review waiting time, production defects, onboarding progress, and retention. Compare similar work and account for staffing or project changes. Do not use lines of code, online status, or badge attendance as your entire definition of productivity.
Make Collaboration Explicit Rather Than Hoping It Happens
GitLab’s remote-work guide emphasizes written knowledge, asynchronous communication, and results over visible activity. Asynchronous means people can contribute without being present at the same time; it does not mean every conversation should become a document.
For an engineering team, turn those principles into concrete agreements:
- Reviews: Define ownership, escalation paths, and response expectations in your Git workflow.
- Decisions: Record the problem, alternatives, decision, and owner where absent teammates can find them.
- Mentoring: Schedule pairing and office hours. Give new hires a named person to ask rather than an instruction to “reach out.”
- Time zones: Agree on overlap hours and a handoff format. Do not quietly turn geographic flexibility into permanent evening availability.
- Quality: Pair review expectations with a deliberate testing strategy; revisit the benefits of unit testing when deciding what reviewers should verify.
For hybrid teams, choose office days around shared work such as onboarding or design discussions. Keep decisions accessible to people who were not in the room. For remote teams, retain live conversations for ambiguity, difficult feedback, and problems that are not progressing in writing.
Are People Happier with Remote Jobs?
Some are, but personal preference is not an organizational performance metric. The Trip.com experiment found higher satisfaction under its hybrid arrangement; it did not establish that everyone would be happier working remotely full-time.
Consider whether you would miss spontaneous office interactions. That is a real trade-off, not evidence that office attendance is necessary—or that people who prefer an office only want to socialize.
Evaluate your actual circumstances: the commute, workspace, accessibility needs, social contact, and boundaries between work and home. Ask how you would get mentoring or focused collaboration in each arrangement. Avoid assuming that either home or the office is automatically the better environment.
There is no need to assume engineers generally accept lower salaries for flexibility. In the Stack Overflow 2026 survey, remote US developers earned about 11% more than in-person developers with similar experience, as our software engineer salary analysis shows. Compare your own offers: compensation, commuting and travel costs, equipment, working hours, and the value you place on location flexibility. Make that trade-off explicitly rather than borrowing somebody else’s preference.
Why Is Remote Work Dying?
“Dying” confuses fewer advertised opportunities with the disappearance of an arrangement.
LinkedIn’s March 21, 2025 remote-work report found that the remote share of US jobs receiving applications fell from 27% in early 2022 to 16% in late 2024. In late 2024, remote roles represented 9% of newly listed US jobs. Those are LinkedIn platform measures across occupations—not software-engineering vacancy rates or an October 2026 market snapshot.
That distinction matters: evidence that existing developers work remotely does not tell you how many suitable openings are available to you. Likewise, an employer’s stated reasons for returning to the office do not, by themselves, demonstrate improved delivery, retention, or innovation.
The defensible conclusion is narrower than the original article’s optimism: remote opportunities persist, but neither abundance nor bargaining power is guaranteed. Plan your search around your role, experience, eligible locations, and financial runway—not an unsupported claim that demand for engineers always exceeds supply.
What to Check Before Accepting a Remote Offer
Include these questions in your software engineering interview preparation, then confirm the answers in the offer and relevant policies.
- Location: Where may you live and work? What happens if you move?
- Attendance: Is office attendance recurring, occasional, or discretionary? Which office?
- Policy changes: Who can change the arrangement, what notice is promised, and what happens if you cannot comply?
- Hours: What overlap, on-call coverage, and response times are expected?
- Travel: How often are offsites or customer visits required? Who pays, and what accommodations are available?
- Equipment and access: Who supplies the laptop and workspace equipment? What connectivity, device, and security requirements apply?
- Career development: How do mentoring, promotion, and access to important projects work for remote employees?
Remote work does not need to become universal to be here to stay. It needs to remain a workable option for a meaningful set of teams and engineers. The evidence supports that expectation, provided you distinguish durable practices from promises about your next job.
FAQ
Are fully remote software engineering jobs still available?
Yes. GitLab’s Intermediate Backend Engineer, AMER listing was advertised as remote in Canada and the United States when reviewed for this update. Verify each opening’s location and attendance requirements; one employer’s listings do not establish market-wide availability.
What is the difference between a remote and a hybrid job?
A fully remote job has no routine office attendance, while a hybrid job combines recurring office and remote work. Neither label establishes unrestricted geography, flexible hours, or freedom from business travel.
Can an employer change a remote role to hybrid?
Employers do change attendance policies; Amazon’s return-to-office announcement is one example. Ask how your arrangement is documented, who can change it, and what notice is promised; get jurisdiction-specific advice for a disputed change.
Does remote work make software engineers more or less productive?
There is no universal answer across teams and arrangements. Evaluate delivery, quality, collaboration, and learning together rather than assuming that personal satisfaction or office attendance proves productivity.
What should engineers check before accepting a remote job?
Confirm approved locations, office attendance, overlap hours, travel, equipment, security requirements, and policy-change procedures in writing. Also ask how onboarding, mentoring, and promotion work for people outside the office.
Further Reading
- Stack Overflow’s 2026 work-setting results — developer-reported remote, hybrid, and in-person arrangements.
- Amazon’s return-to-office announcement — attendance expectations, exceptions, and effective date.
- Hybrid working from home improves retention without damaging performance — the randomized Trip.com study.
- The Power of Proximity to Coworkers — evidence on engineering feedback, learning, and output.
- The Remote Work Gap — dated evidence on remote job availability and applicant demand.
- GitLab’s Guide to All-Remote — practical guidance on documentation and distributed collaboration.
