IT Professionals Experiencing Substantial Shift in Responsibilities

The roles and activities performed by IT professionals have evolved dramatically over the past ten years due to the convergence of modern development technologies, cloud platforms, and as-a-service offerings that can significantly improve overall productivity.

Today, many of these professionals find themselves in hybrid roles that combine traditional development activities with activities that formerly were associated with operations professionals who historically had few or no development-oriented responsibilities. A new International Data Corporation (IDC) report provides an extended census and forecast with detail for both traditional IT operations roles and these new hybrid roles.

"The census data shows that a dramatic, once-in-a-generation shift in the composition of the IT workforce is underway. This shift is akin to what took place during the years from 1997 to 2002 when the emergence of the commercial internet and the .com era turned priorities upside down for much of corporate IT and led to the hiring of vast numbers of web developers and networking experts," said Al Gillen, Group VP, Software Development and Open Source, IDC. "The increased adoption of cloud computing is driving similar transitions today in IT teams supporting this modern deployment model."

In developing this data set, IDC used the following definitions to describe the roles broken out in the study:

DataOps uses a combination of technologies and methods with a focus on quality for consistent and continuous delivery of data value, combining integrated and process-oriented perspectives on data with automation and methods analogous to agile software engineering.

DevOps uses collaborative, agile approaches paired with extensive automation development pipelines, testing, infrastructure configuration, provisioning, security controls, and life-cycle continuous integration (CI) for continuous development and continuous delivery (CD).

DevSecOps uses a methodology that asserts that security needs to be prioritized at the beginning of the DevOps delivery pipeline. It enables DevOps teams, collaborating with security, to act as key stakeholders in defining and implementing security policies.

ITOps uses technology and methods to provide routine, scheduled tasks and unscheduled support activities related to IT systems. ITOps professionals may spend as much as 50% of their time engaged with business users in support, the elicitation of requirements, and performing contingent or secondary business tasks.

MLOps uses technology and processes to streamline and automate the entire machine learning (ML) life cycle. The key capabilities include managing and automating ML data and pipelines, ML code, and ML models from data ingestion to model deployment, tracking, and monitoring. MLOps uses similar principles to DevOps practices, applied to machine learning processes.

Platform engineering is a discipline of designing and building toolchains and workflows that enable self-service capabilities focused on managing and optimizing the software delivery process to deploy applications and services to cloud platforms.

Site reliability engineering (SRE) includes software engineers who build scripts to automate IT operations tasks such as maintenance and support. To enable efficiency and reliability, SRE teams fix operational bugs and remove manual work in rote tasks.

Systems administrators configure, maintain, and support computer systems and systems of systems using a variety of tools and methods appropriate to the system or systems of systems in use. They may spend as much as 50% of their time engaged with business users in defining key requirements, business goals, and adaptations needed to maintain fit for use and fit for purpose.

At a macro level, the study shows that a substantial shift in the responsibilities of IT professionals will occur over the next five years. The data indicates that IT professionals in the most purely operational roles are facing a transition to a more technical or focused role that very often may involve some level of software development work. Accordingly, the roles of IT operations and system administrators, respectively, are projected to decline at compound annual growth rates (CAGR) of -8.2% and -7.8% over the 2022–2027 forecast period. By comparison, the recently emerging roles of DataOps and MLOps are projected to have CAGRs of 17.9% and 20.1% respectively, although the growth is starting from comparatively small numbers.

DevOps and DevSecOps roles are also forecast to continue growing with DevSecOps roles showing a double-digit CAGR over the forecast period. DevSecOps roles will benefit from the growing application threat landscape and the dependence that organizations have on their software capabilities to be competitive, combined with the recognition that incorporating security as early as possible in the software development life cycle reduces costs and increases quality. DevOps growth will be muted somewhat by the growth in platform engineering roles, which will absorb some of these same functions.

Related Links

Hot Topics

The Latest

Observability Is Becoming the Grid That Powers AI - and It Isn't Ready

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT Dominates Enterprise Architecture, with Colocation Anchoring Critical Workloads

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

AI is Moving Fast, and Enterprise File Data Is Not Ready

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Move Fast Without the Usual Quality Penalty

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

When the Observability Bill Arrives for Agentic AI

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

AI is Breaking Enterprise Log Management

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

How Edge Intelligence Will Redefine Secure Connectivity

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

Production Inference Shifts Decisively to Private Cloud

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

Why DevOps Teams Build GenAI Tooling While Most Organizations Still Rely on Manual Monitoring

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Why Cloud Reliability Comes Down to People and How to Improve It

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

IT Professionals Experiencing Substantial Shift in Responsibilities

The roles and activities performed by IT professionals have evolved dramatically over the past ten years due to the convergence of modern development technologies, cloud platforms, and as-a-service offerings that can significantly improve overall productivity.

Today, many of these professionals find themselves in hybrid roles that combine traditional development activities with activities that formerly were associated with operations professionals who historically had few or no development-oriented responsibilities. A new International Data Corporation (IDC) report provides an extended census and forecast with detail for both traditional IT operations roles and these new hybrid roles.

"The census data shows that a dramatic, once-in-a-generation shift in the composition of the IT workforce is underway. This shift is akin to what took place during the years from 1997 to 2002 when the emergence of the commercial internet and the .com era turned priorities upside down for much of corporate IT and led to the hiring of vast numbers of web developers and networking experts," said Al Gillen, Group VP, Software Development and Open Source, IDC. "The increased adoption of cloud computing is driving similar transitions today in IT teams supporting this modern deployment model."

In developing this data set, IDC used the following definitions to describe the roles broken out in the study:

DataOps uses a combination of technologies and methods with a focus on quality for consistent and continuous delivery of data value, combining integrated and process-oriented perspectives on data with automation and methods analogous to agile software engineering.

DevOps uses collaborative, agile approaches paired with extensive automation development pipelines, testing, infrastructure configuration, provisioning, security controls, and life-cycle continuous integration (CI) for continuous development and continuous delivery (CD).

DevSecOps uses a methodology that asserts that security needs to be prioritized at the beginning of the DevOps delivery pipeline. It enables DevOps teams, collaborating with security, to act as key stakeholders in defining and implementing security policies.

ITOps uses technology and methods to provide routine, scheduled tasks and unscheduled support activities related to IT systems. ITOps professionals may spend as much as 50% of their time engaged with business users in support, the elicitation of requirements, and performing contingent or secondary business tasks.

MLOps uses technology and processes to streamline and automate the entire machine learning (ML) life cycle. The key capabilities include managing and automating ML data and pipelines, ML code, and ML models from data ingestion to model deployment, tracking, and monitoring. MLOps uses similar principles to DevOps practices, applied to machine learning processes.

Platform engineering is a discipline of designing and building toolchains and workflows that enable self-service capabilities focused on managing and optimizing the software delivery process to deploy applications and services to cloud platforms.

Site reliability engineering (SRE) includes software engineers who build scripts to automate IT operations tasks such as maintenance and support. To enable efficiency and reliability, SRE teams fix operational bugs and remove manual work in rote tasks.

Systems administrators configure, maintain, and support computer systems and systems of systems using a variety of tools and methods appropriate to the system or systems of systems in use. They may spend as much as 50% of their time engaged with business users in defining key requirements, business goals, and adaptations needed to maintain fit for use and fit for purpose.

At a macro level, the study shows that a substantial shift in the responsibilities of IT professionals will occur over the next five years. The data indicates that IT professionals in the most purely operational roles are facing a transition to a more technical or focused role that very often may involve some level of software development work. Accordingly, the roles of IT operations and system administrators, respectively, are projected to decline at compound annual growth rates (CAGR) of -8.2% and -7.8% over the 2022–2027 forecast period. By comparison, the recently emerging roles of DataOps and MLOps are projected to have CAGRs of 17.9% and 20.1% respectively, although the growth is starting from comparatively small numbers.

DevOps and DevSecOps roles are also forecast to continue growing with DevSecOps roles showing a double-digit CAGR over the forecast period. DevSecOps roles will benefit from the growing application threat landscape and the dependence that organizations have on their software capabilities to be competitive, combined with the recognition that incorporating security as early as possible in the software development life cycle reduces costs and increases quality. DevOps growth will be muted somewhat by the growth in platform engineering roles, which will absorb some of these same functions.

Related Links

Hot Topics

The Latest

Observability Is Becoming the Grid That Powers AI - and It Isn't Ready

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT Dominates Enterprise Architecture, with Colocation Anchoring Critical Workloads

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

AI is Moving Fast, and Enterprise File Data Is Not Ready

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Move Fast Without the Usual Quality Penalty

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

When the Observability Bill Arrives for Agentic AI

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

AI is Breaking Enterprise Log Management

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

How Edge Intelligence Will Redefine Secure Connectivity

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

Production Inference Shifts Decisively to Private Cloud

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

Why DevOps Teams Build GenAI Tooling While Most Organizations Still Rely on Manual Monitoring

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Why Cloud Reliability Comes Down to People and How to Improve It

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...