At the time of writing, I am working as a Systems Engineer for Aviatrix for 2 years, where I am heavily focused on public cloud networking. When I first started at Aviatrix, I came from an almost exclusive on-premise networking and network security background. For over 15 years I had been lugging network hardware around, setting up routers, switches, firewalls, SD-WAN and a whole bunch of other IP speaking devices.
Hardly any cloud or automation experience under my belt, it felt like a great challenge to start working for a secure cloud networking company that focuses specifically on public (multi-) cloud. My expectation was that everyone around me would be deploying their cloud network infrastructure using modern deployment methods according to the "cloud operating model".
Afraid that I would be considered to be an "old-school" engineer without an understanding of how things work in cloud, I set out to learn more about IaC, Git and CI/CD pipelines!
I applied this knowledge enabling co-workers, customers and prospects. In addition I leveraged this knowledge to build and provide repeatable building blocks to simplify the deployment of the Aviatrix platform through our Terraform modules.
Now, 2 years later, I have experienced that especially for the network stack, well executed automation is not as commonplace as I expected it to be. This is what led me to move to a different role, where I am able to focus more on gaining and spreading this knowledge to enable the people around me. In my new role as Principal Solutions Architect, I have the ability to develop myself faster and further as a subject matter expert.
As I gain more knowledge, I aim to leverage this platform to share these learnings, especially for people that are going through a similar journey!
Comments