DevOps Engineer

Job description

Our platform is a SaaS application written in Scala that serves our Angular Typescript web application and C# Microsoft Office plugin (yes we like strong static typing). We manage our (AWS at the moment) infrastructure as code: if it's not under version control in git, it does not exist. And the other way around.

We expect you to have an opinion on tech. We expect you to pick your own hardware and operating system, because that's how you get productive. Having the best tools at your disposal, you're prepared to question everything you see and do not understand. If it can be improved, you’ll re-prioritise and start improving ZIVVER from within.

The A Team

Hot take

  • Ubuntu doesn't count as a real distro. (https://xkcd.com/424/)
  • You are still considering to give Gentoo another chance but you never do.
  • You refer to container technology as 'cgroups' rather than 'Docker'.
  • You sort you config files alphabetically. Always.
  • You noticed this last bullet point is the only one that's not sorted.

 

A day at HQ

You're entering the office around 9:30. Usually, you're earlier, but because of the rainy weather you decided to grab you 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 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 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 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.

Responsibilities

  • Overall management of our infrastructure running on AWS.
  • Product (dev)operations required to meet SLAs.
  • Design of a scalable platform.
  • Keep up with the pace of our fast growing company.

Benefits

In return for your dedication and attention to detail, you’ll get an independent position in an exciting work environment filled with some of the nicest people in the industry, and more...

  • A beautiful bar in our penthouse office
  • Next-gen pension fund
  • Great food
  • Lots of team events and outings
  • Top-tier coffee.
  • Flexible working hours
  • Flex holidays
  • €1.000 personal development budget

 

Requirements

Skills / Degrees

  • Knowledge of Linux: you can, but don't want to compile your own kernel.
  • You know what all the acronyms of AWS' services and have experience with at least 5 of them.
  • Experience with Ansible & Terraform
  • Experience with JVM-related technology, preferably Scala.
  • Masters degree in computer science or something even more complicated.

 

Attitude / Personality

  • Security and privacy is your first and main concern.
  • You're an engineer that can code like a coder, but not a coder.
  • Proud of successes, peeved by mistakes, resilient to recover and learn.
  • Straight forward, direct, but respectful with a big smile.

The 3-step interview process

  • 1Drive
  • 2Work
  • 3Culture
Who
 Alwin and Vincent
What
 Motivation and Drive interview
Where
 Video Call
Tips
  • There's no right or wrong answer
  • Read into what ZIVVER does, and know as much about the role
  • Ask us questions

 

Who
 Vincent, Alwin and Remi
What
 Tech Interview
Where
 In Person @ ZIVVER HQ
Tips
  • Technical interview, where we will discuss your tech assignment which you've previously submitted.
  • We like to find out why you gave the answers you did in the assignment.
  • Please ensure you have ask the team all of your technical questions.

 

Who
 Wisse or Wouter
What
 Culture interview
Where
 In Person @ ZIVVER HQ (usually done straight after the 2nd Interview) 
Tips
  • A chat to make sure it's a good fit on both sites
  • To check to see if you would be a good team balance.
  • Check out the offices, get to know us better

 

Apply now

Tell us something about yourself

Questions

Answer these questions

CV / Resume

Upload your CV or resume file

We accept PDF, DOC, DOCX, JPG and PNG files