Prototyp3
A website and applicant portal built to support the first developer cohort.
- Category
- Full-stack · Developer community
- Role
- Tech Lead
- Period
- August to December 2025
- Year
- 2025
- Built in
- Three weeks for the website and portal
OutcomeA public website and an application portal for the first developer cohort, built and deployed under my lead.Visit the live site
Overview
Prototyp3 runs project cohorts for students. As Tech Lead, from August to December 2025, I built and deployed the website and the application portal for its first developer cohort in three weeks.
My role and contribution
- Led full-stack delivery across frontend and backend, in React, TypeScript and Supabase.
- Deployed the website and application portal.
- Reviewed code from the developers on the team.
- Mentored beginner developers. Their work is theirs; mine is the lead, the review and the deployment.
How it was built
The public website is a single page. Its main call to action is an interest form for upcoming cohorts, and it also carries the organisation’s story, a "Learning experiences" section with a sample cohort project brief, a link to the community Discord, a partners and sponsors section, and a contact form that asks for a name, an email address and a message. This describes the site as it stood on October 26, 2026. It is served from Vercel, which shows in its response headers.
Behind the public site sits the application portal, which handled onboarding and applicant management. It is not publicly visible, so this page does not describe its screens, its data model or who can see what. Those would come from the code, and no source was available when this page was written.
- Tools
- React, TypeScript, Supabase
Challenges and responses
Shipping on a short clock with beginners on the team
The launch window was three weeks, and beginner developers were on the team. My answer was to take the lead on full-stack delivery and deployment myself, and to spend my review time on the code my teammates wrote, mentoring them as I went. I have no record of a specific technical tradeoff from that period, so I describe the constraint and my response, not an incident.
Limits
No applicant counts, usage figures or test results are claimed. The source code is not public, so the data model, access rules and security measures are not described here.