Opportunity board with match scores
Roles with match scores, filters, and Save or Apply in one place.
Product concept and interactive demo
Orzu Platform
A public pitch and role-switching product demo that makes a student-network platform inspectable from student, employer, and administrator perspectives.
Screens
-
Student, employer, admin Each workspace opens without credentials, so the product can be judged from all three sides.The claim, up front A verified student network rather than a job board, stated before you choose a role. -
One sidebar, six areas Network, career, groups, events and startups stay in view instead of splitting into separate products.Where it starts you The home card turns the idea into a next action: complete the profile, or find nearby groups. -
-
-
Role portal
The light-mode role portal starts with an explicit role choice, making the platform's three perspectives immediately inspectable.
Student workspace
The student perspective combines community, opportunities, events, startups, and profile momentum.
Employer workspace
The employer perspective centers opportunity publishing, talent discovery, applications, and application movement.
Administrator workspace
The administrator perspective coordinates users, groups, opportunities, content, partnerships, events, and platform health.
Public pitch site
The pitch layer explains the ambition and operating context before routing partners into the interactive demo.
System
Features
Kanban employer application review
Six fixed stages, with an applicant drawer on every card.
Multi-step opportunity posting wizard
A guided form with live preview. Publishing seeds the review pipeline.
Floating cross-role messenger
An inbox that opens on any page, without leaving it.
Live-filtering student network
Cards filter live by country, university and field.
Decisions and tradeoffs
Problems we hit
Stakeholder access gate without application auth
Problem
The deployed demo needed stakeholder-only access without building real application authentication.
Our solution
Fail-closed edge middleware
A Vercel edge middleware enforcing HTTP Basic Auth. Missing environment variables return 503 rather than falling through to an open page, and invalid credentials return 401.
Cross-role message leakage in shared mock data
Problem
The messenger demo uses one shared mock data graph, so each role had to see only the threads permitted to it.
Our solution
Point-of-view message histories
Direct-message histories are POV-specific: the same thread does not expose the full transcript to a role that is not a participant.
Profile personalization without backend persistence
Problem
A key stakeholder was to see the demo personalized with their own name and photo, but the demo has no backend.
Our solution
Preview locally, reset on reload
The profile edit sheet previews changes locally and shows save feedback, but resets on reload so the demo does not imply data was stored.
CDK dependency exceeding the bundle budget
Problem
Adding the Angular CDK for the employer Kanban board pushed the production build past the active 500 kB initial-bundle warning threshold.
Our solution
Widen the budget, keep the warning
The error budget was explicitly widened to keep the demo deployable on Vercel, while retaining the warning so the overage stays visible.
Decisions we made
Connected role journeys, not mock screens
Decision
The main product decision was to demonstrate breadth through connected role journeys rather than a collection of unrelated mock screens.
Why we made it
An employer opportunity should make sense beside the student's career pipeline and the administrator's governance surface. The system map makes those relationships explicit.
The demo does not hide behind credentials
Decision
The second decision was to keep the prototype easy to enter.
Why we made it
Authentication buttons and role selection communicate the intended identity model, but the demo itself does not hide behind credentials. That lowers friction for a pitch audience and lets a technical reviewer inspect the product structure directly.
Illustrative numbers, clearly labeled
Decision
Because this is a concept and demo rather than a production launch, its numbers and activity states are illustrative.
Why we made it
The portfolio labels it accordingly and does not imply live adoption.
Next
Contact
Let's talk.
For professional opportunities, collaborations, or selected freelance work.
Open to conversations Frankfurt, Germany Europe/Berlin
GitHub penguindevteam@gmail.com