Skip to main content

The Future of the SRE: Remote Work

The majority of site reliability engineers (SREs) will be working remotely post COVID-19, according to the 2020 SRE Survey Report from Catchpoint and the DevOps Institute.

Google says SREs should be doing 50% ops work and 50% dev work, yet having a 50/50 workload split seems to be a pipe dream, according to the survey. The majority of respondents are currently spending 75% of their time on operations resulting in far less of their time being devoted to development.

Additionally, 53% of respondents said they were being involved too late in the application lifecycle.

When SREs are invited early into the development process, organizations can mature to more advanced observability resulting in improved service reliability, incident management effectiveness and customer satisfaction.

"Solving complex problems and ensuring reliability in today's highly distributed world can be very difficult and requires greater monitoring and true observability. Prior to the pandemic, most companies had a handle on end-user/customer experience monitoring for distributed systems," said Mehdi Daoudi, CEO of Catchpoint. "But now with a greater distribution of users comes new challenges and added reliability needs. True observability is the key to ensure reliability and customer experiences for all things distributed."

Jayne Groll, CEO, DevOps Institute, added: "SRE is one of the most innovative approaches to managing services since the early days of ITIL and is most closely aligned with the principles and practices of Agile and DevOps. The data in this report supports the rising criticality of both SRE as a practice and Site Reliability Engineer as a role for any organization trying to adapt to the digital age."

Highlights of survey results include:

Observability Components Exist - Observability Does Not

When asked what tool categories SREs are using today, the majority (93 percent) chose monitoring as compared with 53 percent choosing observability.

Additionally, when asked about their key responsibilities, the majority ignored those aligned with the observability pillars (events, metrics and tracing) highlighting the lack of true observability.

True observability requires monitoring of external outputs to determine how reliable internal systems function.

Heavy Ops Work Load Comes at a Cost

DevOps appears to be in a tug of war, and Ops is winning in the SRE community with the pre-COVID survey showing that 75% said they are spending the majority of their time on Ops, resulting in increased costs of owning and maintaining systems.

Perhaps widening the gap, the survey showed that two and a half months into working from home, the survey results showed a net 10% increase in Ops related responsibilities.


Challenges of the Shift to Remote Work

The post-pandemic environment has resulted in a major shift on where SREs will be located, with nearly 50% of SREs believing they will be working remotely post COVID-19, as compared to only 19% prior to the pandemic.

Additionally, 9% of respondents felt incident management has improved.

However, there are cautionary findings for organizations considering the structure of SRE teams post-COVID, as many respondents noted they are dealing with the following challenges:

■ 41% state that half or more of their work is a toil with mostly manual, repetitive, and tactical jobs that could be automated.

■ 52% said they spent too much time debugging

■ More than half of respondents felt that personal challenges included staying focused and having a good work/life balance while working from home

Recommendations for the SRE

Below are a few recommendations for SREs based on the survey's findings:

■ Be sure to include consideration for not only your code, but also the networks, third party services, and delivery chain components, to evaluate how well the three observability pillars are applied through this new digital experience observability lens.

■ Work to be included earlier in the development process should shift reliability further left to reduce cost, increase team alignment, and identify constraints that can be removed.

■ Turn newly surfaced, or previously-ignored challenges into strategic differentiators. Focusing on challenges like morale, employee experience, work/life balance, and employee engagement and sentiment may showcase a company's employee-first mentality to attract or retain top talent.

Hot Topics

The Latest

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

The Future of the SRE: Remote Work

The majority of site reliability engineers (SREs) will be working remotely post COVID-19, according to the 2020 SRE Survey Report from Catchpoint and the DevOps Institute.

Google says SREs should be doing 50% ops work and 50% dev work, yet having a 50/50 workload split seems to be a pipe dream, according to the survey. The majority of respondents are currently spending 75% of their time on operations resulting in far less of their time being devoted to development.

Additionally, 53% of respondents said they were being involved too late in the application lifecycle.

When SREs are invited early into the development process, organizations can mature to more advanced observability resulting in improved service reliability, incident management effectiveness and customer satisfaction.

"Solving complex problems and ensuring reliability in today's highly distributed world can be very difficult and requires greater monitoring and true observability. Prior to the pandemic, most companies had a handle on end-user/customer experience monitoring for distributed systems," said Mehdi Daoudi, CEO of Catchpoint. "But now with a greater distribution of users comes new challenges and added reliability needs. True observability is the key to ensure reliability and customer experiences for all things distributed."

Jayne Groll, CEO, DevOps Institute, added: "SRE is one of the most innovative approaches to managing services since the early days of ITIL and is most closely aligned with the principles and practices of Agile and DevOps. The data in this report supports the rising criticality of both SRE as a practice and Site Reliability Engineer as a role for any organization trying to adapt to the digital age."

Highlights of survey results include:

Observability Components Exist - Observability Does Not

When asked what tool categories SREs are using today, the majority (93 percent) chose monitoring as compared with 53 percent choosing observability.

Additionally, when asked about their key responsibilities, the majority ignored those aligned with the observability pillars (events, metrics and tracing) highlighting the lack of true observability.

True observability requires monitoring of external outputs to determine how reliable internal systems function.

Heavy Ops Work Load Comes at a Cost

DevOps appears to be in a tug of war, and Ops is winning in the SRE community with the pre-COVID survey showing that 75% said they are spending the majority of their time on Ops, resulting in increased costs of owning and maintaining systems.

Perhaps widening the gap, the survey showed that two and a half months into working from home, the survey results showed a net 10% increase in Ops related responsibilities.


Challenges of the Shift to Remote Work

The post-pandemic environment has resulted in a major shift on where SREs will be located, with nearly 50% of SREs believing they will be working remotely post COVID-19, as compared to only 19% prior to the pandemic.

Additionally, 9% of respondents felt incident management has improved.

However, there are cautionary findings for organizations considering the structure of SRE teams post-COVID, as many respondents noted they are dealing with the following challenges:

■ 41% state that half or more of their work is a toil with mostly manual, repetitive, and tactical jobs that could be automated.

■ 52% said they spent too much time debugging

■ More than half of respondents felt that personal challenges included staying focused and having a good work/life balance while working from home

Recommendations for the SRE

Below are a few recommendations for SREs based on the survey's findings:

■ Be sure to include consideration for not only your code, but also the networks, third party services, and delivery chain components, to evaluate how well the three observability pillars are applied through this new digital experience observability lens.

■ Work to be included earlier in the development process should shift reliability further left to reduce cost, increase team alignment, and identify constraints that can be removed.

■ Turn newly surfaced, or previously-ignored challenges into strategic differentiators. Focusing on challenges like morale, employee experience, work/life balance, and employee engagement and sentiment may showcase a company's employee-first mentality to attract or retain top talent.

Hot Topics

The Latest

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...