Does starting with a clean slate sound good to you? If so, we have the role for you. Zivver is on the verge of a new version of our platform. This is a great opportunity for infrastructure engineers who want to work at one of Amsterdam's favorite tech scale ups. We offer high-end secure communication solutions for ministries, lawyers, and hospitals and are on the look-out for new colleagues who wants to get their hands dirty working on a challenging technical product, with the best tools at their disposal.
Our platform is a SaaS application written in Scala that serves our Angular Typescript web application and C# MicrosofOffice plugin (yes, we like strong static typing). We manage our infrastructure (running on AWS) as code: if it's not under version control in git, it does not exist. Would you fit the team?
“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 grow into senior projects or someone who worked in IT for some time and is retraining as a cloud engineer.
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.
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:30 and start off with checking the output of the daily backup tasks. The backup of GitLab failed because the server ran out of temp disk space.
You notice your colleague Rohit 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 Pablo from the back-end guild 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 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 hit that shut down button.
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
Skills / Experience
Knowledge of Linux: you can, but don't want to compile your own kernel
You know all the acronyms of AWS' services and have experience with at least 5 of them
Experience with Shell, Python and Golang
Experience with Ansible and Terraform
Experience with containers and orchestrators
Experience automating and testing infrastructure (terratest, cloud-custodian, terraform-compliance, InSpec, Atlantis…)
Attitude / Personality
Security and privacy is your first and main concern
You are product-minded. You want to solve problems for people.
You are curious and value learning above everything else
Proud of successes, peeved by mistakes, resilient to recover and learn.
Straight forward, direct, but respectful with a big smile.
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.