Bringing a customer onto the SaaS platform meant creating their virtual machines by hand, one at a time. Terraform and PowerShell replaced the procedure: 3 to 5 hours saved for every new customer, depending on its size.
- Azure
- Terraform
- PowerShell
Available·18 May to 24 September 2027
Cloud & DevOps engineering student
Now in an engineering degree programme at Polytech, I am looking for an internship in infrastructure, cloud or DevOps.
$ whoami --scope=production
role: Cloud & DevOps engineering student
experience: 18 months · SaaS company · team of 2
scope: 4 sites · 2 countries · 12,000 end users
migration: 10 applications → Kubernetes (AKS)
recovery: Velero · documented DR plan · tested restores
2025 – 2028
Engineering degree, Computer Science, Data and Usage, Polytech Annecy-Chambéry
Distributed systems, data and machine learning, governance.
Jun 2024 – Aug 2025
Infrastructure and Cloud Administrator (permanent contract), SYDEV
Kubernetes, CI/CD and GitOps, Terraform, observability, disaster recovery.
Feb – Jun 2024
Final-year internship, converted to a permanent contract, SYDEV
Terraform modules, account lifecycle automation with Ansible.
Jun – Aug 2023
Internship, systems and network support, WIDIP
Level 1 support for a multi-client managed services provider, documentation.
2021 – 2024
Bachelor of Technology (BUT) in Networks and Telecommunications, DevCloud track, IUT1, Grenoble
Skills followed by an arrow link to the case study that puts them into practice.
Infrastructure described in a repository and delivered by a pipeline, rather than assembled by hand. This is where DevOps practice actually happens.
The platform operated day to day: applications spread across several clusters, in two regions.
Knowing before the user does, and being able to roll back.
Four sites, two countries, and access that has to stay bounded.
The databases the infrastructure carries (150 in production), and what they can be made to tell.
What replaces a manual procedure, and the small tools that make it usable by the team.
Infrastructure serves people: helping them when something breaks, and leaving behind enough for someone else to take over without me.
Bringing a customer onto the SaaS platform meant creating their virtual machines by hand, one at a time. Terraform and PowerShell replaced the procedure: 3 to 5 hours saved for every new customer, depending on its size.
The hosting model no longer kept up with growth. Around ten applications were moved to AKS, spread across multi-region clusters by customer segment, and delivered through an Azure DevOps CI/CD pipeline and GitOps deployment with ArgoCD. The data stayed in the same managed pool: one database per customer, 150 in total.
Cluster backups, a documented disaster recovery plan, restores that were actually tested. A backup that has never been restored is not a backup.
Personal project
A complete platform on the Infomaniak Public Cloud: private network, nodes across three zones, a k3s cluster, HTTPS ingress and GitOps, provisioned with OpenTofu and delivered by Argo CD. Every decision is recorded in an ADR, every failure in the repository. What comes next: attributing to each workload its power draw and carbon footprint.
7 min read
A command meant to delete a DNS record destroyed a SaaS company’s production infrastructure on a Friday afternoon. What follows is not an account of an operator error, but an analysis of what allowed an operator error to reach that far.
Read the article→
Available from 18 May to 24 September 2027
Assistant engineer internship: infrastructure, cloud, DevOps. Geneva (Switzerland), Annecy, Lyon, Grenoble, or remote.