You like cloud systems? Clusters? Containers? Automation? Great! You should read on.

Your job as a member of a small and efficient operations team will be to design, maintain and extend our cloud-based infrastructure and processes, such as (including, but not limited to) …

Do we have all of this? No. Are we done with the rest? No. That’s where you come in - we need help in making all of this happen. We also try to use the latest-and-greatest; currently we use (or plan to use, in brackets):

We offer

Desired Skills and Experience

  • CI / CD processes with different staging environments
  • Docker containers in production
  • AWS and Azure cloud set ups
  • Rancher, k8s or Mesos
  • TÜV & ISO certification preps
  • Monitoring and alerting systems
  • Automatic failure recovery & easy disaster recovery
  • Linux (CoreOS, RancherOS, PaaS)
  • Rancher (k8s, Mesos, Nomad)
  • Docker (rkt)
  • TeamCity (Jenkins with build pipelines, LambdaCD)
  • AWS (Azure, Google Cloud)
  • Prometheus, Grafana, ELK
  • Consul (Vault, etcd)
  • Terraform
  • Puppet (Ansible, Salt)
  • Python for automation scripting
  • an attractive learning curve in a higly motivated team
  • competetive salary
  • an open-ended contract
  • open-minded, friendly working atmosphere, short decision paths through flat hierarchies
  • German course for non-native speakers
  • solid linux knowledge, you like the command line and are used to writing bash scripts.
  • solid experience in one of the technologies mentioned above. You have used this one in a fairly big way in your job before. K8s on Azure would be fantastic, but not neccessary.
  • at least some experience in a couple more of them. Somewhere between expert and “have seen that in a blog post once”.
  • motivated, pro-active and lazy - so automation is an integral part of your working style
  • someone who has suffered lack of documentation so you try to avoid that mistake
  • focused on solving user problems, preferably “The Right Way” (tm)
  • also a developer at heart, because, let’s be honest, it’s “infrastructure AS CODE”, right?