Profilbild von Anonymes Profil, Senior (Cloud) Infrastructure Engineer

Letztes Update: 10.02.2024

Senior (Cloud) Infrastructure Engineer

Abschluss: Studied Computer Sciences - No degree
Stunden-/Tagessatz: anzeigen
Sprachkenntnisse: deutsch (Muttersprache) | englisch (verhandlungssicher)


Microsoft Azure Linux Github Grafana Amazon Web Services Systems Engineering Ubuntu Centos Cloud Computing Computerprogrammierung + 22 weitere Schlagwörter anzeigen




- Cloud Infrastructure Engineer
- Systems Engineer
- Devops Architect

I speak German (native) and English (fluent).

Over the course of the last decade I built and worked on systems of nearly every size. From small websites to the world platforms of international companies. Some of them on-premises, some of them in the cloud. Sometimes worked alone but most of them in teams of different sizes. In offices, data centres, on the go and remote. I solved problems and developed solutions for all kinds of departments and companies.

Tools I worked with extensively in recent years:
  • Docker, Kubernetes
  • Terraform, Terragrunt, Packer
  • Ansible, Puppet, Salt
  • Prometheus, Grafana, Alertmanager
  • Grafana Loki, Datadog
  • FreeBSD, Debian/Ubuntu, Arch Linux, Alpine Linux
Since large parts of the IT landscape are changing all the time, this list might already be outdated.

Hyperscalers and managed software products I spent more time with than I’d like to admit:
  • AWS
  • Azure
  • Gitlab and Gitlab CI
  • Github and Github Actions
  • Azure Devops
Programming/Scripting Languages I used for more than just a university project or demo:
  • Python
  • Shell scripts
  • Elixir


08/2020 - 03/2021
Cloud Infrastructure Engineer
(Wirtschaftsprüfung, Steuern und Recht, 250-500 Mitarbeiter)

The customer's product (SaaS application) was already available on AWS (using AWS EKS) but more and more enterprise customers asked for the same product running on Azure because they already had all the paperwork done for using SaaS products running on Azure.

The goal of the project and my responsibilty during the project was to clone the already existing IT platform from AWS to Azure.

It required to learn about the differences of AWS and Azure and the reimplementation of all involved terraform/terragrunt code.

At the end of the project, the SaaS product was running on Azure AKS and the customers SaaS product was deployed to it the same way as the already present AWS EKS solution.

03/2020 - 08/2020
Cloud Infrastructure Engineer
(Wirtschaftsprüfung, Steuern und Recht, 50-250 Mitarbeiter)

The customer's product (SaaS application) was to be made available to enterprise customers as an on-premises solution. For this purpose, a concept as well as a technical solution was required that enables the planning, installation and maintenance of an on-premises application at the customer's site.

The implementation took the form of an installer that sets up a local Kubernetes cluster and provides all required services within this cluster. Updates can be installed online or via USB stick. The product of the company Replicated was used for this.

08/2019 - 02/2020
Cloud Infrastructure Engineer
(Wirtschaftsprüfung, Steuern und Recht, 10-50 Mitarbeiter)

The existing IT landscape and all running services were migrated to Kubernetes (AWS EKS). The migration to the new services took place without any downtime.

My role was to gather requirements for the kubernetes based solution and to implement it.

The cluster and all AWS resources (RDS, IAM, S3, EC2 ...) were created using terraform/terragrunt.
The cluster internals (ingress controller (nginx), cluster autoscaler, certificate manager, logging, metrics ...) were created using kustomize and helm.
The SaaS application created by the customer was also deployed using kustomize.

The services developed by the customers were packaged to small docker containers in close collaboration by me and the development teams. These services were built using on the JVM (Spring Framework) and NodeJS.

This new setup was then replicated to all environments. Starting in a lower environment and eventually moving to the production environment.

08/2018 - 08/2019
Cloud Infrastructure Engineer
(Wirtschaftsprüfung, Steuern und Recht, < 10 Mitarbeiter)

The customer already had a working IT platform hosted on AWS using AWS Beanstalk but wanted to rebuild it to reduce complexity and increase availability.

Over the course of twelve months, this platform was moved to a new AWS account.

The previous concept of Beanstalk was split to AWS standard components (RDS, EC2, ELB) which became a versioned and maintainable "Infrastructure As Code" construct using Hashicorp Packer, Terraform and Ansible. This has increased the visibility of all components and dramatically increased maintainability.

Furthermore, the platform became so modular that the creation of additional tenants or test environments was done very quickly.

At the end of the project, the platform was migrated and multiplied to cover different environments which were deployed to via automated GitLab CI pipelines. Additonally monitoring, logging and metrics were present for all environments.


Weltweit verfügbar
Profilbild von Anonymes Profil, Senior (Cloud) Infrastructure Engineer Senior (Cloud) Infrastructure Engineer