Saturday, July 15, 2017

Network Engineer Evolution

About two years ago I made a learning roadmap for network engineers who want to transform their skills towards Software Defined Networking. I presented it at various events including Cisco Live. It was good, but it looks like I didn't provide the full story. So let's discuss it again, and we will start from the very beginning.


Any network engineer who just starts his or her career today will begin in Phase 1: as the User of networking products where the engineer only knows how to configure the product, hopefully by reading the documentation from the vendor's website first. This type of engineer is what I call "Config Monkey" (sorry, monkey!). If you think you are still in this phase, please don't get offended: I started my career here too. There is no innovation at all, only follow the manual to make the products run.

Then we will move to Phase 2: as Advanced User of networking products. This is the phase where the engineer understands how networking protocols work in detail. He is a domain expert now and can start fine tuning the protocols to optimize the infrastructure. IGP timers, fast re-route, BGP attributes etc. and the engineer should go back and forth between the protocols standard and how they get implemented in vendor's products. So all the fine tunes are based on the 'knobs' provided by the vendor. And by nature, phase 2 network engineer possesses the skill to do troubleshooting as well.

Phase 3 is when the engineer starting to become System Integrator. Even it's similar like Advanced User, but now the engineer must deal with different network functions from wireless access and top of rack switches to security devices, firewalls, domain names, caching, network-based storage, content delivery, application load balancer and so on to provide end-to-end services to end users. He is aware about design trade-offs of various choices. There is still no innovation yet, however by now the engineer has possessed the skill to design, integrate and fine tune complex system all the way to application layer.

SDN and network virtualization comes to the picture in Phase 4: Advanced System Integrator. The system now consists both physical and virtual components. Overlay network runs above the underlying physical infrastructure. Virtual infrastructure has multiple controllers and managers that need to be integrated between each other. Network services have life cycle from initiation until depletion so it must be monitored. Phase 4 engineers talk about APIs when integrating different components. Both physical and virtual networks must run in harmony to provide end-to-end connectivity for the users to access the applications and services.


Once the engineer passes Phase 4, this is the point where he can decide to take either one of different technical paths: first, is to move towards the business and start becoming Solutions Architect. Architect must translate business requirements into technical specifications, and provide integrated solutions to answer the requirements. We can live happily ever after here. I know it because I used to be in this phase for many years when I work for Cisco.

The second path is like what Morpheus described as the red pill: stay in Wonderland and learn how deep the rabbit hole goes. We can choose to stay as engineer to go even deeper in the next two phases.

Phase 5: Contributor. Phase 4 engineer assumes all components will just work when they are integrated, just like playing Lego. Yes, she still needs to understand how one component consumes the API of the other component. But in reality the integration is not, or never, that straight forward. Engineer moves to phase 5 once she starts developing few components to make the system works smoothly. It could be as simple as making automation script using SDK provided by the product's vendor. Or create new driver for an open source platform to connect to specific network device. Or customize the current module of one software to make the system runs. Engineer writes code, understands software development workflow, and fills up the missing ingredient to build one solid system.

Phase 6 is the phase served for Creator. This is the God-mode in Network Engineering. Engineer can look at the current network protocol and decide to invent the new and (hopefully) the better one. When building a complex system with multiple products from different vendors, engineer can assess if it is required to build new software component to have a successful integration. Phase 6 engineer thinks about scalability all the time, centralized vs. distributed model, and about the workflow from beginning of user's request until the service is provided. She generates ideas require to solve complex and open-ended problems. She thinks agile and runs iteration to optimize the system. Engineer in this phase is the one who translates business intent into automated workflow execution to deliver the service.

So let's look at my T-shape SDN Skill Transformation path and try to relate it to the 6-phase of Network Engineer Evolution above.


Obviously you need to be at least a Phase 3 engineer before looking at this path. To start the journey in Phase 4, you need to learn virtualized infrastructure for network, compute and storage as well as the managers and controllers to manage them. Learn abstraction and modeling. Then learn software architecture and engineering. Get involved in software development. Start writing code or optimize existing code to move to become Contributor in Phase 5 and beyond. Or if you decide to take Solution Architect path instead, switch the mindset and learn business skills.

I won't mention any vendor's product, or any vendor's certification, anymore in the evolution. Understand the expectation of what engineer in each phase has to deliver, skills that must be possessed, then make your own judgement to decide which vendor or which certification program (if needed) you want to use in your learning process.

And please don't be mistaken to think I self-proclaimed myself as a Phase 6 engineer. I made decision a while ago to become Product Manager instead, that provides me opportunities to work with many creators to build the next cool things in networking.

Final thought: it's okay to start as monkey once. But knowing where we are, and where we want to be, can surely help to plan how to get evolved.

5 comments:

Prasanth said...

Great post, and nice breakdown. Can you point me out, where can I start with the network virtualization. I'm presently at phase 3, and also leveraging the APIs provided by the vendors.

Moazzam said...

Thank you for your post, this is very interesting. I would also love to hear about you Product management experience. In networks it was always R&D kind of process. But I am sure the PM role is becoming more and more relevant especially considering deeper inception of Automation and even NetworkML.

Main Aman said...

I want to express my thanks to you for bailing me out of this particular setting.
agen sbobet As a result of surfing around through the the web and finding suggestions that were not powerful
agen sbobet, I assumed my life was well over. Existing without the presence of strategies to the difficulties you have resolved by means of your site is a crucial case, and the ones that might have badly affected my career if I hadn’t noticed your blog post. That natural talent and kindness in playing with all the pieces was useful. I don’t know what I would’ve done if I hadn’t come across such a solution like this. agen sbobet I’m able to now relish my future. Thank you very much for your skilled and result oriented guide. agen sbobet I won’t be reluctant to propose the sites to any person who should receive recommendations on this situation.

Andy said...

Needed to compose you this very small jasa seo note to thank you very much tepercaya
jasa seo again for the beautiful tips you have discussed in terbaik this case.
jasa seo This is certainly unbelievably harga open-handed with people like you to give publicly exactly what some people could have advertised as an e-book in making some dough for themselves, certainly seeing that you might well have done it in case you jasa seo decided. The pointers also acted as the great way to realize that other individuals have a similar keenness similar to mine to understand a great deal more around this matter. I think there are millions
jasa seo of more pleasurable moments up bergaransi front for individuals seo service that scan through your site.

Anonymous said...

I simply had to thank you so much once more. I do not know what jasa seo jasa seo I would have worked on in the absence of these creative concepts shown by you directly on that jasa seo theme. Completely was a real fearsome case in my view, however , finding out a new specialised technique you jasa seo solved it made me to weep for delight. I’m just happier for the information jasa seo and in addition sincerely hope you really know what a great job you happen to be getting into teaching people jasa seo today by way of your blog. I know that you have never got to know all of us.