At Zivver, we're building the future of secure communications. Our platform helps hundreds of thousands of users securely communicate sensitive information, and we're rapidly scaling up.
Our platform is a SaaS application written in Scala that serves our Angular Typescript web applications and a C# Microsoft Office plugin. We manage our infrastructure as code: if it's not under version control in git, it does not exist. And the other way around.
As an infrastructure engineer you have 3 mandates: support, enable and educate. We support the whole company’s infrastructure needs, making sure things run as they should. We enable the development teams to be able to do the best work of their lives. Therefore developer experience in this role is important to us. Lastly, we educate developers about the DevOps mindset.
We don’t just go around and do stuff, we’re an organized bunch and take your opinion seriously. You don’t back off from raising your voice and share your best practises. You know it takes a strong team to be able to #raisethebar.
Developing infrastructure is just like developing a product. There’s users who have needs that have to be met.
You refer to container technology as 'cgroups' rather than 'Docker'.
DevOps is a mindset, not a function or a role.
You’re always looking to add automation where it’s needed.
You noticed this last bullet point is the only one that's not sorted
Times have changed with this pandemic, so we had to adapt to a new way of working remotely. This has led us to a remote first company (yes you’re allowed to work from sunny Spain) but we’re also keeping our HQ open in case you want to see your colleagues in real life every now and then.
It’s a regular Tuesday and you have decided to go to the office today. You're entering the office around 9.30h. Usually, you're earlier, but because of the rainy weather you decided to grab your first coffee at home while checking the output of the daily backup tasks. The backup of GitLab failed because the server ran out of temp disk space.
Once you arrive at the office a colleague has already removed some old log files and restarted the backup task. This allows you to focus on the database locking issue you discovered yesterday. After querying the application logs in Kibana you come to the conclusion that one code path in the backend can easily be consolidated to do only one write operation instead of two. You write a fix and a test and you ask a backend engineer from the End User team to review your code. It's time to have lunch because in the afternoon you have a meeting on how to set up and improve the auto scaling of the backend service.
Later in the afternoon you discuss the performance and platform related bug reports during the daily stand up. Your review of this morning was accepted, but your peer 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 go home.
Maybe tomorrow you go for a morning workout and get in a bit later. You know it’s okay as long as you attend any required meetings and keep your team up-to-date on what you're doing.
Develop, maintain and support Zivver’s infrastructure.
Enable dev teams to operate the software they write.
Educate teams to adopt a DevOps mindset.
Keep up with the pace of our fast growing company.
Choose your own hardware
Flexible working hours and location (we fully support working-from-home or remotely)
An exciting, fast-growing, energetic environment
Great office and awesome people with different nationalities
At least €1.000,- per year on personal development budget
Skills / degrees
Attitude / Personality
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.