Several years ago, network engineers and architects were worried about their prospects being outsourced to other countries. However, with cloud technology and automation now breaking in, it has really revitalized the network engineering and architect role as a whole. Networks used to be pretty simple - running network cables to equipment and making sure everything was connected. It evolved over time with the need to make complex networking configurations and rules. Now, networks can be defined mostly in software instead of hardware and with automation, you can write programs and scripts to build out entire network solutions at the push of a button. So the occupation as a whole has a really strong outlook because of these new technologies and because it is being adopted so quickly, there are many companies out there looking for people who know these technologies.
Ken recommends the following next steps:
with an exponential increase in data consumption (videos, messages, chats, internet browsing etc) and more n more devices getting connected ( self driving cars, drones etc) , there is a need to build scalable, resilient network architecture that can withstand the bandwidth requirements.
Now, with the advent of public and private clouds, automation, software defined networking, virtualization and MANY other technologies, the Network Engineer/Network Architect has to wear many different hats. Scalable, reliable connectivity is still the primary goal, but speed to market, speed to delivery, and flexible deployments all come into play as well. The Network Engineer/Architects that are succeeding in this environment have taken on programming roles, and are learning in the fields of Agile Development, DevOps, and other areas that weren't even thought of 5, 10 or 15 yeas ago.
To sum up - the outlook is very good right now. We are becoming more and more connected in everything we do. And the Nework Engineer/Architect is at the heard of that connectivity.