68. Network Engineers are Facing an Identity Crisis

Tech Field Day Podcast

Network engineers are the firefighters and knowledge bases of enterprise IT, however the role of a network engineer is rapidly evolving. With the rise of automation, orchestration, and AI, the familiar image of an engineer hunched over a command-line interface (CLI) is giving way, leading many to question the future of their profession. In this episode, Tom Hollingsworth is joined by Ryan Harris, Chris Grundemann, and Nathan Nielsen as they discuss how the perception of their role has shifted, the continuous need for learning and adaptation, and whether the CLI is truly dead.

The conversation explores the challenges and opportunities presented by these technological advancements, highlighting how network engineers are embracing new tools like chatbots and GUIs for enhanced visualization. While some aspects of the job, like manual CLI work, may be diminishing, the core principles of understanding network functionality remain core to the role of the network engineer. The panel talks about identity crisis in a field where continuous learning is essential, contrasting it with professions like doctors and lawyers who deal with slower-changing fundamentals. They discuss the value of specialization versus being a generalist, the concept of the “pitchfork engineer,” and ultimately, how redefining their identity as lifelong learners can help network engineers thrive in this ever-changing landscape.

Learn more about ⁠Networking Field Day 38 here⁠.

Host: ⁠Tom Hollingsworth⁠, Tech Field Day Event Lead

Panelists:

Ryan Harris, Senior Network Engineer

⁠Chris Grundemann⁠, Network Infrastructure Consultant

Nathan Nielson, Principal Solutions Architect

Follow the Tech Field Day Podcast ⁠⁠⁠⁠⁠⁠⁠on X/Twitter⁠⁠⁠⁠⁠⁠⁠ or ⁠⁠⁠⁠⁠⁠⁠on Bluesky⁠⁠⁠⁠⁠⁠⁠ and use the Hashtag #TFDPodcast to join the discussion. Listen to more episodes ⁠⁠⁠⁠⁠⁠⁠on the podcast page of the website⁠⁠⁠⁠⁠⁠⁠.

Follow ⁠⁠⁠⁠⁠⁠⁠Tech Field Day⁠⁠⁠⁠⁠⁠⁠ for more information on upcoming and current event coverage ⁠⁠⁠⁠⁠⁠⁠on X/Twitter⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠on Bluesky⁠⁠⁠⁠⁠⁠⁠, and ⁠⁠⁠⁠⁠⁠⁠on LinkedIn⁠⁠⁠⁠⁠⁠⁠, or ⁠⁠⁠⁠⁠⁠⁠visit our website⁠⁠⁠⁠⁠⁠⁠.