Joining Devolution as a DevOps engineer - what can you expect in terms of the tech stack, clients, internal tools & processes, and the people?
by Nikola Obradović
Joining Devolution, a company specializing in DevOps consulting, marked a significant turning point in my career. As I navigated through the dynamic landscape of technology, I quickly realized that this was not just another job, it was an opportunity to immerse myself in a world of endless learning and innovation.
In this article, I'll share my experiences and insights gained from working at Devolution, highlighting the wide array of technologies and methodologies that newcomers can expect to encounter in this thrilling field.
I was surprised by the team’s ability to handle a variety of technical stacks for different clients, from managing Kubernetes clusters on-prem to handling Kubernetes clusters on Cloud (GKE, EKS), as well as managing different CI/CD, monitoring, alerting and security tools and stacks. After spending some time and working together with the team I have found that the key to successfully managing multiple tech stacks across different clients and projects lies in effective communication, teamwork and thorough documentation.
Another thing I found super helpful when transitioning between projects and technologies was Devolution’s Slack channel called #standup-engineering, where DevOps Engineers write in short what they did each day, which allows everyone to keep track of other projects without being directly involved.
Things I’ve done in the short time since I joined the team are:
1. Upgrading Kubernetes clusters on GKE and
2. Upgrading on-prem Kubernetes clusters using kubeadm,
3. Switched CloudSQL instances to use private IP,
4. Helped in upgrading MongoDB,
5. Upgraded ArgoCD
And the most interesting aspect that I’ve had the opportunity to work on so far is building an internal product that presents a set of deliverables related to deploying PaaS (Platform as a Service) based on Kubernetes. It has various features, and in one of our upcoming posts we will write in more detail about it.
Having recently started working with the Devolution team, it has been a short but effective period of learning and growth. I've worked on crucial infrastructure upgrades, played a role in improving security, and been part of cutting-edge projects like the internal PaaS. Each task has contributed to my experience and knowledge, and I'm eager to share more insights about our journey in future articles.