No One Wants To Be A Network Engineer Anymore

59,145
0
Published 2024-03-12
The job market is more competitive than ever but the desire to fill network engineering roles is lower than before. In this episode, Tom Hollingsworth is joined by Ryan Lambert, Dakota Snow, and David Varnum for an examination of why network design and implementation isn’t a hot career path. They look at the rise of cloud as a discipline as well as the reduction of complexity in modern roles with help from software an automation shifts. They also discuss how entry level professionals can adjust their thinking to take advantage of open roles on the market.

Host:
Tom Hollingsworth, Tech Field Day Event Lead: www.linkedin.com/in/networkingnerd/

Panel:
Ryan Lambert: www.linkedin.com/in/ryanl-nw/
Dakota Snow: www.linkedin.com/in/dakota-seufert-snow-8a220764/
David Varnum: www.linkedin.com/in/varnumd/

Follow Gestalt IT
Website: www.GestaltIT.com/
Twitter: www.twitter.com/GestaltIT
LinkedIn: www.linkedin.com/company/Gestalt-IT

#NFD34 #NetworkEngineer #Networking #AI #Automation

All Comments (21)
  • @BradyLooney
    I am studying CCNA as part of my Bachelors in Network Engineering. I see so many people ask about Cybersecurity, Software engineering, Computer Science. I very very rarely see anyone looking to become a network engineer. I am very proud to be studying it and enjoy learning the ins and outs. Thank you guys for this refreshing view.
  • People want jobs. Network engineering is not thought about because no one talks about network engineering. It's that simple.
  • I started out in Networking in the Marine Corps. Got my CCNA and the Old way of Networking that I learned it going away. Now I'm Learning Coding, Automation and Cloud. The Transition has not been Easy. Thanks for the Video!
  • @ChrisRossUK
    Really enjoyed this. As an IT professional (with limited networking knowledge) it's nice to hear what networking professionals think of networking in the modern day.
  • @srw788
    As a networker who later entered cybersecurity, this is spot on. As a networker I often found myself being the "go-to" for anything that touched the network, even in large environments. The Windows/Linux admins expected me to configure link agg on their boxes. I was expected to know Linux to run networking tools, I was expected to address SOHO networking, branch networking, WAN networking, and everything that passed a bit. And yes, when cloud came through I was expected to understand how to do it all in Azure and AWS simultaneously as the company couldn't make up its mind. The biggest skill it taught me was being self-reliant and patience as often other disciplines would throw their hands up when it "wasn't their domain". Now, being in Cybersecurity, even when focused on an EDR solution heads-down, I am still relying on networking to understand beyond surface-level the TTPs of the threat.
  • @elsacarrera2860
    I'm a Cybersecurity bootcamp student with zero prior knowledge and I agree 100%!!! Network fundamentals was the most overwhelming class I took. Emphasis should be on Network Fundamentals - every Cybersecurity class thereafter has reverted back to knowledge learned from network fundamentals. Misconfiguration is one of the reasons vulnerabilities occur.
  • @bbakerxyz
    Great panel, guys. And that's a really high light switch behind Tom.
  • @pataleno
    I was network engineer 25 years ago. I’m accidentally getting dragged back into a Network engineering role with cloud and I’m loving it. 👍
  • I’m working on my CCNA and Python and currently working as a network engineer. We install servers, cables, security cameras, telco, it’s my favorite job. It’s such a rewarding career too! Ultimately I wanna work towards network automation and SDN
  • @naordaniel
    Network engineer that made the move to cloud Architect here, I can totally agree that my knowledge in networking has made my job so much easier. Deep Routing understanding is a must for cloud
  • @neel4fun
    Excellent discussion. Networking is evolving & will always remain relevant.
  • @SkyMonkey42
    I honestly thought this was going to be a video about 3 network engineers explaining why they don’t like networking. Instead, they are referencing more about how it’s changed relating to cyber security and cloud. Great perspective! Good video!
  • Great discussion. I want to be a network engineer because it's the backbone of IT. I have the Net+ and going for CCNA next!
  • @LabEveryday
    I love networking, but between the gatekeeping, the difficulty of getting your first networking job, to the cap on the amount you can make even as a CCIE. It’s not as sexy as it used to be to be. You have to have a real passion for networking in order to be successful and like someone on your panel stated a lot of people don’t have the attention span to sit there and labeveryday. They also struggle to deal with the pressure of the role. Lastly, the lack of representation is a real problem. I’m interested to see the diversity at Cisco Live this year. 🤔 Good topic!
  • This was great I just passed my CCNA and I feel I have a lot more to learn. I want to be a Network Engineer
  • @garymoore3878
    As a retired Network Engineer, very interesting topic. Very good discussion. I really like the concept of network engineering as a hobby. I still have a very small network at home, and try to keep up with current trends.
  • @xxxyyy4668
    I'm 42 and just started studying for my CCNA, I know cloud has the cooler jobs now a days, I dont care, I like networking and Im starting from the ground up.
  • Network engineering is made supper hard to learn and is taught in such a morning way. When I started my IT learning I actually started-with Network engineer and taught my self.
  • @FikkyT13
    I enjoy watching and listening to the guests, and I love the closing remarks from the host. Networking can never be obsolete.
  • @alienmicrobes
    IT operations and vendors have replaced a lot of network engineers. You can rent an engineer for a few days a week. A lot of work shifted to operations due to NMS, automation, and redundancy. A network can be run by IT operators, DevOps, vendor account team, and a senior designer. In-house engineers are needed when there are complex SDN issues, routing with providers, client server events, troubleshooting with vendors. There is no reduction in complexity, it just gets shifted or masked. I would argue complexity has increased, and engineers are more reliant on vendors for support.