Education infrastructure · campus launch · first Piscines · 2020
42 Lisboa — founding setup and the first Piscines in Portugal.
Hired from the 42 Network dev team into the founding crew for 42 Lisboa: porting the network operating stack into a new country, building Rails-based student and candidate onboarding tools, and helping the first Piscines move from application funnel to campus reality.
The shape
2020
Portugal campus launch
7 months
42 Lisboa launch engagement
Rails + RBAC
Campus management tooling
Candidates + students
Onboarding and daily ops
Public proof
The visible model behind the launch.
The official campus is 42 Lisboa. For the broader school model, Piscine, culture, and network context, read my internal 42 School and 42 Network background.
Open access
100% free
42 Lisboa describes its education as free, high-quality, peer-to-peer, and open to everyone 18 and up.
Operating model
Peer-to-peer · project-based · gamified
The public methodology is built around peer learning, hands-on projects, gamified progress, and no academic-background filter.
Campus reality
Open 24/7
A 42 campus is not only a classroom replacement. It is an always-on operating environment for students, staff, infrastructure, events, and support.
Network context
30+ countries
42 Lisboa is the Portuguese campus of the global 42 Network, which the school describes as operating across more than thirty countries.
The problem
Launching a 42 campus is not the same problem as launching a normal school. There are no lecture halls to schedule and no teacher-led curriculum to staff. The core product is the operating system around the students: applications, check-ins, Piscine logistics, campus access, peer review, project progression, role-based staff tooling, communications, and the rituals that make the model legible to people seeing it for the first time.
Lisbon also had to inherit a mature network model without feeling like a copy-paste branch of Paris. The infrastructure needed to speak the same language as the wider 42 Network, but the campus had to work for Portuguese partners, applicants, staff, and students on the ground.
The first Piscines were the real launch test. Marketing interest is abstract. A Piscine turns it into bodies in the building, accounts in the system, peer evaluations, support tickets, exams, operational edge cases, and a countdown that does not care whether the tooling feels ready.
What I did
Six layers behind the first live cohorts.
Port the operating stack into a new country
Brought the 42 Network tooling and campus workflows into the Lisbon context: Rails-based student systems, staff-facing tools, onboarding flows, auth and administrative surfaces, and the everyday product glue needed to run a school that is always open.
Turn applicants into Piscine candidates
Built and supported educational software tools that streamlined student and candidate onboarding. The work sat between product, support, operations, and communication: make the process clear enough that motivated candidates could get to day one without the system becoming the bottleneck.
Harden internal platforms for staff and learners
Maintained internal platforms and integrated role-based access control into the campus management system, so administrators, students, candidates, and support staff could operate with the right permissions and fewer manual workarounds.
Map the human system, not only the software
Used the service-design discipline I had picked up at 42 Paris before the launch: stakeholder mapping, interviews, discovery maps, personas, user journeys, usage scenarios, value propositions, and pitch discipline. For a campus launch, those tools matter because every product decision touches candidates, students, staff, partners, and the wider network.
Keep network consistency without flattening local reality
A 42 campus has to stay compatible with the network, but launch work is local by nature. The useful work was adapting the inherited model to Lisbon while preserving the mechanisms that make peer-to-peer learning, project validation, and the Piscine selection process work.
Run launch operations close to the floor
The role was not only code. I oversaw daily student management, coordinated volunteers, handled technical support for platform operations, and turned repeated campus friction into product fixes while the first cohorts were learning the system.
What transferred
Launch lessons that still shape how I build.
- A launch is an operating system, not an announcement. The public opening is only the visible layer; the real launch is every workflow surviving contact with users.
- Educational products have brutal feedback loops. If onboarding, access, evaluation, or support breaks, the learning model breaks with it.
- The first cohort teaches you where the product is pretending to be clear. Candidates and students surface ambiguity faster than any internal review.
- A proven playbook still needs local translation. Copying the model is not the same as making it work in a new country.
Engagement
- Founding team · 42 Lisboa · 2020-2021
- Ruby on Rails educational tools
- 42 Network tooling and campus operations
- Role-based access control for campus management
- Applicant onboarding and check-in workflows
- Piscine launch support
- Daily student management and volunteer coordination
- Student and staff internal platforms
- Service design and Design Thinking fundamentals
Common questions
What this launch work actually covered.
What was the 42 Lisboa launch?
42 Lisboa was the Portuguese campus launch for the global 42 Network. David was hired from the 42 Network dev team into the founding crew to help set up the technical and operational systems behind the campus and its first Piscines.
What did David do at 42 Lisboa?
He worked as a full-stack developer on Rails-based campus tooling, candidate and student onboarding systems, internal platforms, role-based access control, technical support, and daily launch operations around the first selection cohorts.
What is a Piscine?
The Piscine is the intensive 26-day selection period used by 42. Candidates learn the basics of programming through projects, peer work, and exams before earning a place in the main curriculum.
Why is this a case study?
It is a launch case study: taking a proven but unusual operating model, bringing it into a new country, and making the technical, human, and operational systems work under live cohort pressure.
Keep reading