To mitigate this risk, the experts from BackBox argued that automation must be inextricably linked with backup and rollback strategies. For an agentic system to be trusted, it must operate within a framework that captures the state of the network before and after every action. If an AI agent attempts to optimize a routing protocol and inadvertently causes a segment of the network to go offline, the system must have the capability to instantly recognize the failure and roll back to the last known good configuration.
This "safety net" approach is what allows organizations to embrace higher levels of automation without compromising the stability of their business operations. As NetOps teams look toward 2030, the maturity of an organization will likely be measured not by how much automation they use, but by how effectively they can recover from an automated error. The integration of real-time backups into the automation workflow ensures that the "human in the loop" can step in when necessary, but more importantly, it ensures that the system itself is self-correcting.
The Evolving Role of the Network Engineer
A significant portion of the conversation was dedicated to the human element of this technological shift. There is a common anxiety in the industry that AI and automation will render the network engineer obsolete. However, Shenoy and Khimji offered a more optimistic and nuanced perspective. They suggested that the role is not disappearing but is instead undergoing an essential evolution.
The network engineer of 2030 will likely need a different skillset than the engineer of 2010. While a fundamental understanding of networking protocols (like BGP, OSPF, and TCP/IP) remains foundational, there is an increasing need for proficiency in data science, API integration, and policy management. The engineer becomes a policy-maker, defining the "intent" of the network—such as security parameters, latency requirements, and redundancy levels—and then monitoring the AI agents to ensure that the actual state of the network aligns with that intent.
This evolution also changes the daily "rhythm" of network operations. Currently, many teams operate in a reactive mode, responding to tickets and outages as they occur. In an agentic NetOps future, the workflow becomes more proactive. Engineers will spend their time refining the models, auditing the actions taken by AI agents, and ensuring that the infrastructure is resilient enough to handle future demands. The shift is from "fixing the network" to "improving the network’s ability to fix itself."
Preparing for the 2030 Landscape
As organizations look toward the end of the decade, the path forward involves a gradual building of trust in automated systems. This process starts with automating the most mundane and repetitive tasks—such as OS updates, configuration backups, and compliance checks—and slowly moving toward more complex, "closed-loop" operations.
