Guillaume Weill

Responsible, within a small team, for the smooth operation of several Kubernetes clusters, semi-hosted on OVHCloud, serving as a common foundation for internal applications and CI/CD workflows based on Kubernetes runners.

The platform hosted critical internally developed applications, with strong requirements for availability, security, and observability.

Main Responsibilities:

Key Achievements:

Stack & Tools:

This is an administrative web application that allows citizens to request a certificate of good conduct. This full-stack project, based on modern technologies (VueJs, NodeJs, Kubernetes, ...), primarily provides users with sensitive personal data entry forms through a clear, secure, and accessible interface. The core of the product involves processing the entered information, storing it, and managing its lifecycle, up to its deletion in accordance with GDPR. It also includes managing workflows that simultaneously query multiple external APIs, such as B2 or FIJAIS, to accept or reject the certificate application.

The product has enabled the generation of tens of thousands of certificates and notably identified several individuals unsuitable for positions involving contact with children.

I was involved in this project for several months as a tech lead, technical referent, and senior developer. I implemented the micro-services oriented architecture, integrated into a CI/CD mechanism. In addition to actively participating in development, I provided technical support to the team, offering advice and validating some of the Pull Requests.

As tech lead, I assisted in the development of two web applications for the general public. The applications leveraged the state's design system and integrated with the tools and best practices provided to ensure project longevity (Git, Pull Requests, Kubernetes, Jira documentation).

I was responsible for framing the project and the team, ensuring a sufficient level of quality (standardizing team skill levels, implementing common rules, and adhering to best practices such as appropriate test coverage), and deciding on the technical architecture after analyzing the needs.

Technical Stack:

Challenges Encountered: