Ever dreamt of being the decision maker when it comes to infra? Well, buckle up. We’re looking for an expert DevOps Engineer! Someone who understands the challenges within the space and is able to explain our tech and non-tech leadership when and why we need to move in a certain direction. Sounds like a challenge? Well, it is!
Our infra environment runs on AWS, Linux, Terraform, Ansible, Kubernetes, Hashicorp Vault and Gitlab. We are looking to bring a vision to help us migrate from current infrastructure (which is also in AWS) to EKS considering AWS reference architecture with observability stack in place and this is where you come in!
Not only do you understand the technical aspects, you can communicate them clearly. Therefore you know how to communicate clearly and move into the right direction while taking your stakeholders along while keeping them informed.
“Joining us you’ll be part of our versatile, multicultural young engineering team”, says Johan, your soon-to-be-manager. “It makes a great job for an engineer who wants to design and implement complex cloud infrastructure environments as well as leading the team’s growth path towards a stable infrastructure platform".
You will learn everything there is to know about encryption, decryption and email security;
DevOps is a mindset, not a function or a role, and you will be the main spokesperson for this mindset;
The challenges of a scale-up are an excitement to you, no day will be the same;
I like being challenged by handling opinionated stakeholders;
Your vision is so bright, we need to wear sunglasses!
What you will do:
You’ll design and implement complex cloud infrastructure environments;
You’ll promote the best practises for performance and security;
You’ll drive the technical investigation and resolution of a crisis type of incident;
You’ll drive strategic software architecture solutions within their area of ownership;
You’ll provide technical advice and providing input on technical decisions that impact other teams;
You’ll contribute to implementation of metrics, monitoring and alerting;
You’ll collaborate with Product team to define directions and technical requirements;
You’ll be providing feedback that supports the growth and development of their team members;
You’ll be guiding our junior and mid-level engineers;
You’ll play a big role in educating teams to adopting a DevOps mindset;
You’ll be the go-to & spokesperson for the Infrastructure team.
Expertise you’ll bring:
Soft skills you’ll bring:
Security and privacy is your first and main concern;
You are product-minded. You want to solve problems for people;
You are a strong decision maker and you can be pragmatic;
Proud of successes, peeved by mistakes, resilient to recover and learn;
Straight forward, direct, but respectful with a big smile;
You are able to explain the logic behind your technical decisions;
You care for Developer Experience and want to give them the best toolset possible.
If you’re still reading and excited about this role, we welcome your application even if you think you don’t meet all the requirements. We understand that no candidate is perfect, and would love to hear your story. Keen to learn a bit more? Keep reading...
A day at Zivver
Office or home office? It’s your call. You decide to work from home today, as it allows you to go out for a walk and grab a sandwich with a colleague who lives nearby during your lunch break.
Today, you start at 09:30h and start off with checking the alerts and operation channel and see what tickets there are to work on. The backup of GitLab failed because the server ran out of temp disk space. You notice your colleague already removed some old log files and restarted the backup task. This allows you to focus on the database locking issue you discovered yesterday. At 10:30 in the morning you have a daily call with your team during which you can discuss what you are working on and whether anyone needs help with their tasks.
After lunch you have a meeting with the back-end team on how to set up and improve the auto scaling of the backend service and discuss other plans and issues that could have risen as you are the person who communicates the defined plans and directions of the infrastructure team.
Later in the afternoon you are making a presentation on what has been achieved by the infrastructure team during the last weeks followed by a meeting with a CTO discussing the routes of how to achieve the larger results. As the working day comes to an end, you see that your review this morning was accepted, but one of your team members insisted on writing a better scaladoc. After adding a few useful comment lines, you merge your branch. A release to production can wait for tomorrow, so it's time to hit that shut down button.