.jpg)
|
July 3, 2026
Career development is an important topic for every employee, and Hypoport Sofia’s culture allows people to develop their skills, take on new challenges, and grow professionally. However, every career path is different and has its own unique challenges. That’s why we spoke with Kliment Chakarovski, who has made his way from System Administrator to DevOps Engineer, to share his experience and insights.
Hi, first of all, thank you for having me. It's a pleasure to share a bit about my journey. I started at Hypoport Sofia around five years ago as a System Administrator. During that time, I had the opportunity to work on a wide range of infrastructure and operational challenges, which gave me a solid technical foundation and helped me understand how different parts of the business work together. Looking back, it's been quite a journey—from maintaining systems to helping improve the way we build and deliver one of our products.
My interest in DevOps started whenever I found myself doing the same task more than once. I would always ask myself, "There has to be a better way to do this." Over time, that curiosity evolved into a passion for automation, process improvement, and preventing recurring issues before they happen. Bit by bit, I started exploring new technologies, CI/CD tools, automations, and ways to make life easier—not only for myself but for everyone involved.
After all, if a computer can do the repetitive work, why shouldn't it?
Besides the technical skills, one of the most important things I needed to develop was my ability to collaborate across different teams. As a DevOps Engineer, you're often working between development, operations, security, and business teams.
Finding common ground, understanding different perspectives, and helping everyone move toward the same goal became just as important as any technical knowledge. Sometimes the biggest challenge isn't the technology- it's translating between people who use different technical "dialects."
The transition itself was actually quite smooth. I already knew which team I would be joining, and I had a good understanding of the challenges and responsibilities waiting for me. Of course, every new role comes with a learning curve, but having that familiarity allowed me to focus on growing into the position rather than starting completely from scratch. It felt less like changing jobs and more like continuing the next chapter of the same story.
Better than ever. The role gives me the opportunity to continuously learn, solve interesting problems, and work with a variety of technologies. Every day brings something different, which keeps things exciting. And fortunately, there are enough challenges left to ensure I won't get bored anytime soon.
Just do it. If you're curious about automation, continuous improvement, and learning new technologies, don't be afraid to take the leap. Start small, experiment, make mistakes, learn from them, and keep moving forward. The best way to understand DevOps is by doing it, not just reading about it.
That's a very good question. The most honest answer would be: I don't know. Technology evolves incredibly fast, and one of the things I enjoy most about this industry is that it constantly creates new opportunities and challenges. But since I shouldn't leave the question unanswered, I'd say that in five years I hope to still be learning, solving interesting problems, and contributing to meaningful projects. As for the exact answer- ask me again in five years, and I'll probably have a much more accurate response.