
The Power Of Curiosity | Drew Conry-Murray
Get every episode summarized
Each time The Art of Network Engineering publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
About this episode
How does an English major with no technical background become one of the most recognizable voices in network engineering?
Drew Conry-Murray didn't start his career configuring routers, chasing certifications, or working in a NOC. He started as a copy editor who barely understood the networking articles crossing his desk.
Then someone threw him into a technical interview with a firewall vendor.
He had to figure it out.
That moment became part of a career spanning Network Computing, Interop, Packet Pushers, Network Break, Heavy Networking, and years of conversations with some of the smartest people in the networking industry.
In this episode of The Art of Network Engineering, Andy sits down with Drew to talk about the career behind the microphone: learning networking without formal technical training, developing the ability to ask better questions, surviving layoffs and career uncertainty, building relationships that create opportunities, and adapting as technology changes.
And, inevitably, they get into AI.
Drew explains why network engineers should become conversant with AI without assuming they need to become AI experts, why understanding software may matter more than writing every line yourself, and why human relationships still create an advantage even as technology becomes more capable.
In this episode:
- How Drew went from English major to networking journalist
- Learning networking by being thrown into the deep end
- Why asking good questions is a technical skill
- The uncomfortable reality that learning in tech never ends
- Drew's path from Network Computing and Interop to Packet Pushers
- What losing a job does to your identity
- Why relationships create career opportunities
- Whether network engineers really need to learn Python
- How AI may reshape technical careers
- Why being good at your job isn't always enough
One of the strongest lessons from Drew's career is simple: you don't need to know everything before you start. You need enough curiosity to keep figuring out the next thing.
For everything AONE: https://artofnetworkengineering.com/
Get every episode summarized
Each time The Art of Network Engineering publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Know when Drew Conry-Murray turns up
Follow Drew Conry-Murray and once a week we email you every new episode they appeared on — including guest spots the show notes never mention, because we read the transcript.
Follow Drew Conry-MurrayFree. Pick your own day and time.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from The Art of Network Engineering

The Network Automation Paradox - You Need Time To Save Time
The Art of Network Engineering

Stop Vibe Coding: Start Spec-Driven Development, with John Capobianco
The Art of Network Engineering

500 Hours of Foosball, 20 Hours on Your Career | Mike Bushong on Staying Valuabl...
The Art of Network Engineering

Cursor for Network Engineers? Meet Transit AI (Sponsored)
The Art of Network Engineering