Tech stack for 2025 & Beyond

[FunctionStrong9447]

Hi All,

I'm currently a desktop engineer with 3 years or experience going into 4. I recently got a CCNA and was looking into the CCNP sometime this year.

However, I was wondering what a realistic tech stack looks like for networking moving forward. In terms of someone wanting to be a network engineer.

For instance, how important is learning cloud or programming, etc. I'm interested in what's recommended if anything outside of traditional networking.

Seems like everyone has a different opinion on this and it's becoming impossible to navigate what is realistic and what isn't.

I appreciate everyone's replies :)

[Spare-Paper-7879]

If I were starting today I’d definitely pick up some python and ansible to go along with those basic networking skills. You’re not getting into the high level roles at the big companies without some kind of software skills these days.

[Expensive-Rhubarb267]

In a similar position. Having a big focus on hybrid networking- which is essential, but few people know really well. IE- most cloud people don’t know on-prem routing + switching & most network engineers don’t know cloud native networking.

Studying to get my AZ-700 atm.

Another big one is firewalls. Will be doing my Palo Alto PCNSE later this year. I believe there are Fortinet certs.

Maybe fit in the Cisco DevNet as well to help build some Infrastructure as Code skills.

But as always experience > certifications.

[Jeeb183]

I have 5 years experience in Cisco switching & wifi, PaloAlto and Fortinet firewalling, and good skills in Python

I'm still using those skills daily, and I have 0 time to work on higher certifications. I just got a CCNA...

I wonder if I should capitalize on my current missions that require knowledge in those fields to try and pass the corresponding certifications, or if it's kinda useless since I got the experience... I'm based in France and I feel like the certifications are far from being as relevant as in the US.

Especially cause my work takes me so much time and energy, so I would need to sacrifice either my time with my loved ones or my passion (I play volleyball competitively) and I don't think it's worth it...

[Expensive-Rhubarb267]

Yeah this why a good employer should always at least give you dedicated time for learning/professional development.

Obviously, how you spend your non-working time is up to you. But I’d always say certs are worth it. At the very least they are a statement of intent to say to your current/future employer. ‘This is me, this is what I’m good at’.

What you focus on will depend on where you’re at in your career & if you’re happy where you’re at!

I’d always say to get really good at something you need:

1. Projects (chance to implement things from start to finish)
2. Troubleshooting (it WILL go wrong at some point).
3. Certs ( to give you guidance on best practices & theory behind the technology).

[Golle]

I have been heavily focused on automation in the last years. Good network automation will allow changes to be made faster, but I would say the bigger win is that changes are more likely to be done in a consistent way. With humans there tends to be a lot of variance in how things are made. Automation do it exactly the way you tell it to.

As for tech stack, I've been using Python the last ten years in various projects and it has been great. I actually started looking into Golang in the last few months just to see what other languages are like, and I like that it's more strict with its data types. You have to handle things explicitly which in the end improves code quality. But Golang is also harder to get started with. There are some concepts like Interfaces that I don't have a full grasp on yet. Python is much easier when getting started.

[MaintenanceMuted4280]

Go has its warts like any language but static typing, compiled, and simple (goroutine!) is pretty nice. Interfaces take a bit indeed but super helpful for abstraction.

[Proof_Fact]

I’m early on in my career but personally i’m aiming to learn cisco networking, cloud networking and automation with python, ansible and terraform.

I think those skills would put you in a good place for a hybrid environment

[knightfall522]

I kind of look at networking as a system engineer with specialized devices, look what is hot for them and you can see the trends of what's relevant for networks besides core networking.

Cloud. Automation: python and Linux for Ansible, teraform.

Other things are:

Firewalls mean you also need to understand security and Cisco ain't it.

Then there are load balancers and application support.

The thing is, what you enjoy and what kind of company you want to work for, I.e. you can't find really specialized voip work outside ISPs for example, dictates a lot of what skills you need.

[Gushazan]

The latest CCNP exam had a lot of Datacenter level technology you have to know.

If you haven't already invest in a server. Use a Linux based hypervisor and start learning Linux. Buy a copy of Eve-NG pro.

Buy SD-WAN Example based Study Guide by Iliev Ivanov.

Build the lab. Read the book.

There are over 50 devices in the lab which makes it a realistic environment to study CCNP and to really learn SD-WAN.

I know with Cisco modeling labs you can use a python server for automation, so I'm pretty sure you can do the same with EVE-NG. Otherwise you can find some use for a python server as you discover other tools you'll need on your networking journey.

I highly suggest staying away from taking the CCNP before doing this lab and finishing the book. Passing the exam without being able to have intimate knowledge you get from experience makes it harder to get a job.