Background

From the STI2D baccalauréat to the engineering degree

A continuous path: at every step, I tried to bring what I learn closer to what I build.

  1. 2019 – 2022

    STI2D baccalauréat, SIN option

    Lycée Christophe Colomb, Sucy-en-Brie

    The STI2D baccalauréat (sciences and technologies of industry and sustainable development) with the Information and Digital Systems option: analysing and building technical solutions that handle information flows — voice, data, images — in systems both local and remote.

    That's where it all started: programming, networks, communicating systems and project management, learning by doing on real systems rather than abstract exercises.

    • Programming
    • Networks
    • Communicating systems
    • Project
  2. 2022 – 2023

    BUT in Computer Science, year 1 (full-time)

    IUT of Créteil-Vitry, UPEC

    The BUT in Computer Science is built around six skills: building an application, optimising, administering communicating systems, managing data, leading a project and working in a team. With 600 hours of supervised projects over the three years.

    First year: solid foundations in algorithmics, object-oriented programming, databases, web, systems and project management.

    • Algorithmics
    • OOP
    • SQL
    • Web
    • Systems
  3. 2023 – 2025

    Full-stack developer on a work-study contract

    Val-de-Marne prefecture, SINUM department · BUT in Computer Science (application development track)

    Two years of work-study alongside the BUT, entirely on my own: nobody in my department had a technical profile. So I took charge of everything, from design to putting the whole chain into production. A complete rebuild of the intranet's meeting-room and vehicle booking site (PHP, JavaScript), used by ~800 active workstations.

    Android app to manage room inspection reports (Kotlin, Room), agile with Jira and GitHub Projects. Alongside at the IUT: Vigipol (React, D3, Chart.js), a RATP metro route calculator (Python, Flask, Dijkstra and Bellman-Ford), and the PMR app in Flutter.

    • PHP
    • JavaScript
    • Kotlin
    • React
    • Flutter
    • Python
  4. Since Sept. 2025

    Engineering degree, LSI major, work-study

    Efrei Paris · degree awarded together with Université Paris-Panthéon-Assas

    Three years of work-study in the Software and Information Systems major, for a state-recognised engineering degree. I moved from the BUT to the engineering cycle with a clear goal: to specialise in software development and information systems.

    On the school side: software engineering, object-oriented programming, databases, algorithmics, graph theory, advanced web development, C, Java and project management. What interests me is seeing them applied the very next day on a real product.

    • Software engineering
    • OOP
    • Graphs
    • Advanced web
    • C
    • Java
  5. Since Sept. 2025

    IT development officer, S-Print v4 rebuild

    Société des Grands Projets (SGP) — IT department (DSI), Solutions unit, Development team, S-Print team

    SGP is the public body building the Grand Paris Express: 200 km of automatic metro and 68 stations. My scope is not the construction site but S-Print, the platform where contractual partners declare their economic and social footprint and their safety indicators.

    I contribute to the rebuild from version 3 (Java and Vue.js) to version 4 (Symfony + API Platform, TypeScript + React): pages and components, search filters, data browsing, API calls, tests, code reviews. I work in two-week sprints (Scrum and Kanban) with Jira, Confluence, GitLab, Docker and Postman, and I've run several agile ceremonies as a rotating scrum master.

    • Symfony
    • API Platform
    • React
    • TypeScript
    • Docker
    • GitLab
    • Jira
    • Scrum

Two ways of working

Alone and in a team: I can do both

My background has put me in both situations, and each taught me something the other wouldn't have.

Alone · Prefecture · 2 years

Carrying everything, from A to Z

At the Val-de-Marne prefecture, nobody in my department had a technical profile. I was alone to design, develop and above all put the whole chain of my room and vehicle booking application into production, used by about 800 workstations. I also developed a mobile room inspection app.

  • End-to-end responsibility: technical choices, deployment, support
  • Learning alone, searching, solving without a safety net
  • Direct contact with users who aren't technical
In a team · BUT, Efrei, SGP

Moving forward together

At the BUT, almost all my projects were done in teams. Today I'm in a team at school, and in a team at work at SGP, which matches the reality of the market: I no longer depend on myself alone, and I'm not self-taught, since my colleagues help me, review my work and make me grow.

  • Code reviews, daily stand-ups, sprints and tickets every day
  • Colleagues to unblock me, review and challenge my choices
  • Rotating scrum master: leading, listening, coordinating

The result: autonomous when needed, effective as a group when possible.

Review of my first year at SGP

What the work-study taught me

Rebuilding without breaking

Read S-Print 3, understand the need, rewrite it cleanly in S-Print 4, then compare field by field. Slower, much safer.

Code that reads by itself

DRY, KISS, YAGNI, SOLID, explicit naming, early returns, few comments: I learned to name better rather than comment more.

The environment matters as much as the code

A memory crash of the tests under WSL reported with the right context saves the whole team time, even without the final fix.

Documenting is investing

Understanding and documenting a complex data model spared me mistakes on every following ticket.

Leading and communicating

Rotating scrum master, a ten o'clock daily, asking for help at the right time: skills that school teaches little.

Data has consequences

Behind every form field is a real commitment to local jobs and small businesses. Data accuracy is a priority.