Education platform · Paris Bocal · 2020
42 Network Student Intranet
Inside the 42 Paris Bocal, I worked with the 42 Network development team on the student intranet used to follow curriculum progress and skills.
The challenge
Work on a student platform that sits inside the learning method, not beside it.
At 42, the intranet is part of how students experience the school. It carries curriculum and project data, progress, skills, profiles, and the state behind everyday student workflows. A change could not be treated as an isolated screen: it had to make sense to students while remaining dependable for the people operating the campus and network.
How it worked
Curriculum state made legible
The student-facing product had to turn project, progress, and skills data into a clear account of where someone stood and what they could do next.
Full-stack delivery
I worked across the web application with the Network development team, following changes through the interface, application behaviour, and the data behind the student experience.
Development inside the Bocal
The team worked inside the operational and pedagogical centre of 42 Paris. Technical problems and curriculum questions were not abstract tickets; they were part of the same building and daily feedback loop.
A shared network product
The intranet and its API connect student, curriculum, project, campus, and identity data. Product decisions therefore had to respect a system larger than one local interface.
My role
-
01
Joined the 42 Network development team inside the 42 Paris Bocal as a full-stack developer.
-
02
Worked on the student intranet rather than a separate marketing or admissions website.
-
03
Contributed within a team positioned close to technical support, curriculum questions, and everyday campus operations.
-
04
Carried that understanding of the Network platform into the founding 42 Lisboa team and its local campus launch.
What changed
Full-stack product work on a student platform embedded in the everyday 42 learning experience.
This was not a public launch with one headline metric. The useful result was production experience inside the software that students and campus teams depended on every day. It showed me how curriculum rules, product behaviour, data, and operational support meet inside a self-directed school—before I had to help make that model work in Lisboa.
- Contributed full-stack work to the 42 Network student intranet with the Paris-based development team.
- Worked where product decisions could be understood against real student and Bocal use, not only a written specification.
- Built the network-level context that later helped me adapt tooling and operate candidate and student workflows at 42 Lisboa.
Tools and technologies
Sources