Defining the Augmented Network Engineer

Surviving (and Thriving) in the Age of AI

The Network Engineer’s job hasn’t just evolved - it’s exploded in complexity.

I have been a network engineer for 15+ years, but before I ever touched a router, I spent four years building custom servers and gaming rigs. I have always been a hardware nerd at heart.

My networking career is split between the two worlds of the industry. I spent four years in Managed Services, keeping the lights on for critical networks, and 11+ years in Professional Services, delivering complex infrastructure projects for large enterprise and government clients.

I’ve seen the industry shift from white-box servers to cloud, and from CLI to “Software Defined” everything.

But right now, we are in the middle of the weirdest shift of them all.

---

The Complexity Trap

Whether you work in a NOC, an enterprise team, or Professional Services, the job is getting harder.

We’re expected to be experts in routing, switching, wireless, security, and automation. We need to deliver “gold standard” secure architectures, yet the sheer number of variables in today’s landscape makes it nearly impossible to do it all manually.

I started The Augmented NetEng to explore how I can use AI to manage this complexity.

I want to discover the landscape of what’s possible. I want to build workflows that handle the “grunt work” of configuration and auditing so I can focus on the deep technical work: architecture, design, and hardening the network.

What to Expect: Deep Dives and Discoveries

This isn’t a “thought leadership” blog; it’s a place to work through real network engineering problems with AI.

I plan to use this space to share:

• Technical Deep Dives: How to actually implement AI-driven automation in a production-ready way.

• Security Discoveries: How AI speeds up finding vulnerabilities and security gaps, and how to defend against them.

• The “Stalled Project” Queue: I’m finishing tools that sat idle for years, using AI to write the Python glue I never had time to figure out before.

No Fluff. No “Top 10 Prompts.”

I am not an AI “expert” or a “futurist.” I am an engineer with boots on the ground.

I don’t write like a journalist. I write like an engineer. That means you won’t find “Top 5 ChatGPT Prompts to 10x Your Life” articles here.

Instead, I plan to:

• Fail in public: I’ll show you what doesn’t work so you don’t waste your time.

• Focus on local and private: How to use models like Ollama locally, so your topology and IP schema never leave your laptop.

The Selfish Motivation

I’ll be honest, I’m writing this just as much for me as for you.

The Feynman Technique says you don’t truly understand a topic until you can teach it to someone else, using simple language. Writing this newsletter forces me to deeply understand the Model Context Protocol (MCP), RAG pipelines, and Python automation before I hit publish.

(It also gives me a decent excuse to convince my wife that I need to buy more hardware for the home lab, haha.)

---

The Reality Check

There’s a lot of noise out there right now. Some engineers are panicking that AI is going to replace them.

I’m in the camp that believes you won’t be replaced by AI, you’ll be replaced by an engineer who uses AI.

If you want to be that engineer, welcome aboard.