There are moments in a career that don’t feel significant in real time. Later, you realize they marked a shift.
For me, the recent (WA)NUG meetup hosted by the US Networking User Association at Cascadia Pizza Restaurant and Brewery was one of those moments. It wasn’t just another industry event. It was the first time I wasn’t simply in the room but actively contributing to the conversation.
That distinction matters.
Being part of a panel alongside professionals who have spent years shaping discussions around networking, automation, and operations changes how you see your place in the industry. It’s not about validation. It’s about recognition of contribution and stepping into a broader, evolving dialogue that defines where the industry is headed.
The evening was guided by Eric Chou, whose role as emcee set the tone for the discussion. Rather than prompting rehearsed responses, the conversation was shaped through thoughtful questions that required reflection. That tone carried into the keynote by Scott Robohn, who framed the evolution of the Next Generation Network Engineer (NGNE).
The message was clear: automation and AI are no longer optional. They are expected. But more importantly, they raise the bar. They reward engineers who understand systems deeply and expose those who rely only on surface-level interaction.
That perspective naturally extended into the panel discussion, where the focus shifted from technology to careers.
Early in a networking career, the path feels structured: certifications, protocols, troubleshooting. Progress is tangible. Over time, that clarity evolves. The emphasis shifts from execution to judgment, from commands to context, from solving problems to understanding systems. At some point, you stop following playbooks and start writing them.
That shift led to a question that resonated across the room:
How do you stay relevant when everything keeps changing?
There wasn’t a single answer, but there was alignment. Relevance isn’t built by chasing every new tool. It comes from understanding fundamentals and applying them across changing environments.
Technologies evolve. Interfaces change. Platforms shift. But how systems behave and how engineers think through them remains far more consistent. This became even clearer as the discussion moved toward tools and platforms. Traditional networking has transitioned from CLI-driven workflows to cloud-managed, API-driven, and increasingly AI-assisted environments. The shift isn’t just operational, it’s conceptual.
We’re no longer just managing devices. We’re managing systems. And increasingly, we’re managing intent.
There was a moment during the panel when a question around AI and operational trust came up, and I found myself pausing. Not because there wasn’t an answer, but because the answer wasn’t simple. That pause reflected something important: AI is powerful, but it demands clarity in how we use it.
It’s already delivering measurable value in monitoring, troubleshooting, and capacity planning, areas where pattern recognition and scale matter. But it also introduces risk.
AI can obscure decision-making, create over-reliance, and scale mistakes just as efficiently as it scales insights. Without strong fundamentals, engineers risk becoming operators of systems they don’t fully understand. AI doesn’t replace expertise. It exposes whether it exists.
A similar gap between theory and reality emerged when discussing monitoring and source of truth. In principle, every system aims for clean, centralized data. In practice, environments are fragmented and constantly evolving.
The goal isn’t perfection, it’s alignment. And often, the real challenge isn’t collecting data but maintaining trust in it.
What stood out most, though, wasn’t the panel itself, it was the audience. The questions weren’t about tools they were about direction: What should I focus on next? Am I building the right skills? How do I stay ahead?
These aren’t just technical questions, they’re professional ones. And they reflect something universal: everyone in this field is navigating change, just at different stages.
Participating as a panelist in this environment was more than a moment of visibility. It reflected where I stand in the industry today. Not just learning from conversations but contributing to them. As a Solution Architect, that shift matters. It’s no longer just about understanding systems, it’s about helping shape how they are designed, discussed, and evolved. And that responsibility brings clarity.
If there is one consistent signal from conversations like these, it’s that the industry is moving toward a convergence of networking, AI, and automation, whether we’re ready for it or not. The engineers who will lead in this space won’t be the ones who know every tool, but the ones who understand how these domains intersect and translate that into real-world impact.
That requires more than technical depth. It requires participation. Show up to conversations. Engage with communities. Challenge ideas and be willing to have yours challenged.
Because growth in this field doesn’t happen in isolation. It happens in rooms like these where experience meets curiosity, and ideas are refined through dialogue.
If you’re navigating your place in networking today, the direction is clearer than it seems:
Lean into fundamentals. Invest in automation and AI not as trends, but as capabilities. Build connections with people who are thinking about the same problems. That’s where perspective is built. That’s where relevance is sustained. And increasingly, that’s where impact begins. Technology will continue to evolve. But the engineers who contribute, engage, and move the conversation forward are the ones who don’t just adapt to where the industry is going. They help define it.