More companies now hire engineers wherever the talent is. Others run hybrid teams that come into the office a few days a week. Either way, the developer writing the code and the QA engineer testing it are often in different cities, different time zones, or simply in the office on different days.
That flexibility is good for hiring and good for people. But it puts real strain on how engineers talk to each other. This post looks at what the research says about that strain, and how Guardian Samurai is built to take it out of the testing and security workflow.
The problem: communication breaks down
Most engineering teams are no longer in one room
Gallup's 2025 hybrid work research, based on a May 2025 survey of 17,660 U.S. adults, found that 51% of remote-capable employees work hybrid. In tech, the split is even sharper: 47% are fully remote, 45% are hybrid, and only 9% are fully on-site.
Even people who go into the office every day feel it. The share of fully on-site workers who say their team is spread across different locations more than doubled, from 13% in 2023 to 27% in 2025.
Remote work makes teams more siloed
A study of more than 61,000 Microsoft employees, published in Nature Human Behaviour, measured what happened to collaboration when the company went remote. Time spent working with colleagues in other groups fell by about 25%. People talked more with their inner circle and less with everyone else, and collaboration networks became, in the researchers' words, "less interconnected and more siloed".
For engineering, "other groups" usually means QA on one side and development on the other.
QA and Dev silos were already a known problem
The gap between development and testing existed before remote work made it wider. In a 2021 Applause survey of more than 1,800 QA, product, engineering and DevOps professionals, one of the top two barriers to testing earlier was that development and QA efforts remain siloed. The same survey found 44% of developers struggle with context switching between coding and testing.
Put a silo that already existed together with a team that is now spread out, and the hand-offs between them get slower and easier to miss.
What it looks like day to day
If you work on a split QA and Dev team, these will sound familiar:
- A developer finishes a change, then waits for someone in QA to be online to run the full test suite.
- Test results land in one person's inbox, and everyone else has to ask for them.
- "Can you send me the latest report?" becomes a daily message.
- The test plan lives with QA, so developers don't know what will be checked until it fails.
- A security scan only runs when the one person allowed to run it remembers to.
None of this comes from bad people or bad intent. It comes from tools that split engineers into groups with different access, and teams that can no longer lean over a desk to close the gap.
Guardian Samurai's answer: one role, Engineer
Guardian Samurai understands this, and that is why we have only one role for the people doing the work: Engineer. We do not distinguish between QA and Dev.
Anyone with the Engineer role can:
- Run security scans on the servers your team is building.
- Run full test suites, not just a single test or a single check.
- View test plans, so everyone knows what will be checked before it runs.
- View test results and reports, from any run, by anyone on the team.
A developer in one time zone can run the full suite before handing off a change. A QA engineer working from home on Monday can open the same results the developer saw on Friday. Nobody has to wait for someone else to be online, and nobody has to ask for permission to see what happened.
No more breakdowns, no more silos
When every engineer can run the same checks and read the same reports, the hand-off stops being a hand-off. The results are simply there, for everyone in engineering, no matter where they work or which days they are in the office.
That means:
- No more communication breakdowns over who ran what, and when.
- No more silos between the people who write the code and the people who test it.
- One shared record of every scan and test run, visible to all members of engineering.
Remote and hybrid work aren't going away. The tools your team uses should be built for that, not against it.
See it for yourself
You can run a scan any time at /tools/scan. To see what a scan checks, read our post on whether your MCP server is ready for production.
One reminder: only scan servers you own or have permission to test.
Sources: Gallup, "Hybrid Work in Retreat? Barely." (2025); Yang et al., "The effects of remote work on collaboration among information workers," Nature Human Behaviour (2021), via Berkeley Haas; Applause shift-left survey (2021).
Photo by Chris Montgomery on Unsplash.
