Send us a text

Consulting Engineers (CEs) at networking vendors blend deep technical expertise with customer-facing skills to bridge the gap between account managers and specialized solution design. They operate as specialists who support Sales Engineers when customer requirements demand deeper technical knowledge.

• CEs often join from traditional network engineering backgrounds or increasingly through vendor graduate programs
• The role provides higher impact by influencing entire industries rather than just one company
• CE positions typically offer better compensation than operational networking roles
• Computer science education rarely covers networking fundamentals, creating an industry knowledge gap
• The autonomy of the CE role allows for continuous learning and specialization while maintaining customer contact
• Working at a vendor provides exposure to bleeding-edge technology and broader industry perspectives
• Soft skills are equally important as technical skills for success in consulting engineering

If you're interested in transitioning to a Consulting Engineer role, develop your soft skills and build relationships in the networking community, as these connections are invaluable. Reach Colin Doyle and Jared Cordova on LinkedIn to learn more about consulting engineering opportunities.

Find everything AONE right here: https://linktr.ee/artofneteng

Send us a text

The divide between network engineers and developers has long been a source of frustration, misunderstanding, and blame in the tech world. When applications fail, the classic refrain "it's the network" often echoes through organizations, leaving network engineers scrambling to prove their innocence while developers remain convinced of their code's perfection.

In this enlightening conversation, former Cisco developer advocate Erika Dietrick joins hosts Andy Lapteff and Jeff Clark to unpack the root causes of this technological rift. Erika offers a rare dual perspective, having worked both as a software engineer and in Cisco's Technical Assistance Center (TAC). She explains how educational paths create fundamentally different mindsets: "Developers learn to code, period. We do not learn how our computer works. We do not learn how the network works."

Andy shares his personal struggles with learning automation, admitting to starting and quitting "every Python class on planet Earth." This prompts Erika's most valuable insight – that learning to "think like a developer" matters more than syntax or commands. The conversation explores how network engineers often find themselves drowning in daily operational tasks while being expected to add coding skills "for no more money," creating resistance to automation despite its potential benefits.

The discussion takes unexpected turns through topics like cultural differences between teams, the challenges of breaking technical silos, and how AI might actually help bridge these gaps without replacing human expertise. Erika outlines her upcoming free course designed specifically for network engineers learning to code with AI – addressing the exact educational gap that has frustrated network professionals for years.

Whether you identify more with Andy's automation struggles or Jeff's enthusiasm for Python scripting, this episode offers practical perspectives on healing the developer-networker divide.

Subscribe to Erika's Youtube channel here: here:https://www.youtube.com/@erika_thedev

Subscribe to our podcast for more conversations that tackle the human side of technology and join our Discord community at linktr.ee/artofneteng.

Find everything AONE right here: https://linktr.ee/artofneteng

Send us a text

Network engineers have traditionally drawn a line between "our tools" and "developer tools," often rejecting powerful solutions that could dramatically improve our workflows. But what if we thought about tools the same way tradespeople do? A plumber wouldn't refuse to use a hammer just because it's "for carpenters" – so why do we resist Git?

In this eye-opening discussion, we explore how Git – the version control system created by Linux founder Linus Torvalds – can transform how network teams manage configurations, collaborate on changes, and maintain system history. Far from being "just for developers," Git provides elegant solutions to problems network engineers face daily.

Think about how many times you've emailed configuration files with names like "config_v2_final_REALLY_FINAL.txt" to your team, trying to track which version is current. As our guest William Collins puts it, "If you're versioning in the file name, you've already lost." Git eliminates this chaos by providing a structured approach to tracking changes that's actually remarkably similar to how routing protocols work – distributed nodes maintaining a consistent state through carefully managed updates.

We break down the differences between Git (the technology) and platforms like GitHub (commercial services built on Git), demonstrate how branching and pull requests can formalize peer review of network changes, and show why you don't need to understand every Git command to start benefiting from it today. Whether you're backing up configurations, collaborating on documentation, or building automation workflows, Git provides the structure and accountability that network operations desperately need.

Ready to stop emailing configurations and embrace a better way? Listen now to discover why Git isn't just for developers – it's for anyone who wants to work smarter.

Find everything AONE right here: https://linktr.ee/artofneteng