Medior/Senior Cloud Engineer

The ‘formal description’ is that you’re responsible for a stable infrastructure in which we run our customer environments and that you make it possible for the organization to grow continuously. However, we’re not really formal. So how would we explain what we do? Well, the SaaS platform team works with cutting-edge technologies, and that’s pretty cool. We host over 7000 customer environments which are updated twice a week and need 24/7 uptime. That’s why we keep on challenging ourselves to see if we can go faster or make improvements. Integrating operational work with engineering tasks, and being 24/7 stand-by, requires careful coordination. Picture a dynamic workplace where we do our engineering work sprinting through tasks in Scrum fashion, while operational tasks are managed with Kanban’s flexibility. Night shifts ensure around-the-clock support for critical tasks. Clear communication and mutual respect between teams are key to success in this hybrid approach. Tech Stack Do you have relevant technical experience? Then this list will give you an idea of the tools and processes we work with: provisioning (Terraform), configuration (Puppet, Ansible), containerization (Kubernetes, Azure AKS), block- and object storage, Elasticsearch, observability (Influx, VictoriaMetrics, Nagios etc.), Python and more. We use these technologies on Windows and Linux servers, MS SQL databases, firewalls, and VPN servers. But, it’s not about what we currently use. It’s about a curious mind and an abstract way of thinking. Where will you be working? Currently, we have 4 SaaS platform teams; 27 members in total. We are social technicians with a big love for what we do and find it important to be open to each other, which also means that we give feedback. In our team, we can say everything and we always listen to each other. We work according to the agile principles. You’re probably familiar with them. There’s always something to do when it comes to maintenance, improvements, and working smarter. So, we as a team determine what has high priority in our backlog. During our 2-week sprints, we deliver what we’ve committed to. Retrospectives keep us on our toes and show us what improvements can be made. We expect you, and the team, to be playful with technology. Mind you: playful, but responsible. In the interview, we would like to hear what you’ve figured out and implemented tech-wise in your previous or current job.