diff --git a/report/self-assessment/remi.typ b/report/self-assessment/remi.typ
new file mode 100644
index 0000000..f5cf2f3
--- /dev/null
+++ b/report/self-assessment/remi.typ
@@ -0,0 +1,94 @@
+//
+// Description: Main document to stitch everything together
+//
+#import "/metadata.typ": *
+#import "/tail/bibliography.typ": *
+#import "/tail/glossary.typ": *
+#import "/resources/mse-title-page.typ": *
+#show:make-glossary
+#register-glossary(entry-list)
+#set text(region: "gb")
+
+//-------------------------------------
+// Template config
+//
+#show: thesis.with(
+  option: option + (type: "final"),
+  doc: doc,
+  school: school,
+  date: date,
+  tableof: (toc: false),
+  logos: logos,
+  custom-title-page: mse-title-page(
+    title: [Self-assessment],
+    subtitle: [Team: Pleeeeein deeeee eeeeeeeeeeeeeeeeee],
+    authors: (
+      (name: "Rémi Heredero"),
+    ),
+    date: date,
+  ),
+)
+
+// #show "e": "ee"
+
+//-------------------------------------
+// Content
+//
+
+/*
+Un rapport d'auto-évaluation doit dans le grandes lignes :
+- Reprendre les points qui avaient été annoncé lors de la définition du projet, est-ce que les objectifs et buts de formations fixés en début de projets on été atteints. 
+- Evoquer votre role dans l'équipe, les compétences que vous avez pu mettre à disposition, et celles qui vous ont fait défaut.
+- Lister les gains en compétences que vous ressentez après ce projet.
+*/
+
+#show heading.where(level: 1): (it) => {
+  set text(size: huge)
+  set block(above: 1.2em, below: 1.0em)
+  if it.numbering != none {
+    let num = numbering(it.numbering, ..counter(heading).at(it.location()))
+    let prefix = num + h(0.5em) + text(code-border)[|] + h(0.5em)
+    unshift-prefix(prefix, it.body)
+  } else {
+    it
+  }
+}
+
+#show heading.where(level: 2): (it) => {
+  if it.numbering != none {
+    let num = numbering(it.numbering, ..counter(heading).at(it.location()))
+    unshift-prefix(num + h(0.8em), it.body)
+  } else {
+    it
+  }
+}
+
+= Introduction
+
+This report is a self-assessment provided alongside the team report. It is meant to be a personal reflection on the project, and should be read after the team report.
+
+I want to be upfront, as hinted at in the team report, that this project ran in parallel with a similar hobby project I was doing with some friends. At least, similar regarding my specific tasks. 
+// However, the skills I was developing there directly benefited my work here, and vice versa.
+
+= Role in the Team
+
+My primary role was to set up the server, and develop the APIs for the database and cloud data management.
+
+It also became apparent early on that I'd naturally take on a broader technical role. We decided at the beginning to establish clear Git rules to work efficiently. I was responsible for writing these "Guidelines & Unified Laws for Advanced Gitflow" (GULAG) and making sure everyone respected them. It quickly turned out that I also had to do most of the code reviews. This was quite time-consuming but very formative, especially since we all came into this project with different backgrounds and coding approaches.
+
+Beyond doing most of the reviews, I also ended up helping my teammates with debugging and code design. I became the team's troubleshooter.
+
+I was basically the person picking up all the tasks we forgot to plan for at the beginning. I didn't mind this role at all; I like helping out and sharing my knowledge.
+
+= Objective & skills review
+
+My initial objective was to #quote(strike[Solve Maxwell's equations])
+#par(text(size: 0.8em, emph[
+  A data infrastructure is automated, deployed both in productive and development environment. The database is automatically configured and populated by external MeteoSwiss data. 
+  The student didn't experiment automatic deploy /configuration and multi-environment. 
+]))
+
+This objective was partially completed and shifted during the project. I did successfully deploy a server infrastructure with a database and a broker, including the corresponding APIs to push and retrieve data. However, the MeteoSwiss data integration was abandoned because it fell out of scope after one student left the group.
+The database is indeed automatically configured. I didn't focus on setting up automatic deployment for my part. Another student ended up doing automatic deployment on the project.
+
+I still learned a lot on this project overall. It wasn't really what I expected technically, but I gained much more experience in technical project management and figuring out how to work with people from very different backgrounds and horizons. I became much more versatile during this project, which, I think, is essential for an engineer. We should all be able to do a bit of everything and communicate with anyone.
\ No newline at end of file