I started in support (2016), then moved to systems and network administration, cybersecurity and finally DevOps. That path makes me look at a platform as a whole: the server, the network, the pipeline, and what happens when something breaks.
At Hoortrade (2022 - 2025) I was the only DevOps engineer of an eight-developer product team: architecture of the SaaS platform on OVH Cloud, Kubernetes clusters from test to production, GitLab CI/CD pipelines, Terraform and Ansible, observability with Prometheus, Grafana and Zabbix, incident management and root cause analyses.
I cannot show my employers' code or infrastructure. The projects on this site are therefore personal, built on infrastructure I run.
How I work
How I work, applied to my projects, with what you need to check it.
01
Nothing ships without review and a green pipeline
Every change goes through a branch and a merge request. A merge is blocked until the pipeline has passed, on every project.
CI may only change the image of a Deployment. Pods run without root, read-only, with no Kubernetes token when they do not need one. The service that receives visitors' messages has no access to the cluster.
DevOps engineer with more than 7 years of experience in infrastructure, containers and CI/CD automation. Former DevOps technical lead at Hoortrade: SaaS architecture on Kubernetes, Infrastructure as Code (Terraform, Ansible) and observability (Prometheus, Grafana). Brings generative AI into DevOps workflows to speed up automation.