My path to becoming an architect
I started my career as a system administrator and spent four years becoming the lead. To grow into DevOps, I began to learn by reading professional books about Linux, networks, automation, and more. I started implementing some practical DevOps configuration automation and monitoring tools in my work infrastructure. I went the extra mile and became proactive with those tools to build automation.
Once I felt ready, I interviewed for a DevOps systems engineer and was hired after the first interview. Working with DevOps, I accomplished continuous integration and continuous development (CI/CD) and infrastructure automation projects.
My next move was to become a cloud solutions architect. I call this role “DevOps++.” I did many consulting engagements focusing on deploying cloud-native platforms and delivering Kubernetes training. I also earned certifications such as Google Professional Cloud Architect, Kubernetes Administrator, and Azure Solutions Architect Expert.
After two years, my experience and certifications helped me get an offer to become a solutions architect for a large organization. I learned new skills related to systems design, documentation, presenting, and overall IT solutions life cycles. It was a significant shift from the daily hands-on work on the command line to a role with client meetings, presentations, and design decisions.