Full-stack ownership
I worked across the application interface, server-side logic, and persistence layer using Next.js, Node.js, PostgreSQL, and MongoDB.
All workPROJECT NOTES / 2024
FULL STACKInternLoom.
One platform. Different roles. Clear boundaries.
SOFTWARE / SYSTEMS / CONNECTIONSInternLoomCONCEPTUAL PRODUCT MAP
The problem behind
the product.
I built a full-stack internship platform with Next.js and Node.js, backed by PostgreSQL and MongoDB, with JWT and multi-role access control.
The challenge
Support different user roles within an internship platform while keeping permissions and application access explicit.
WHAT I WORKED ON
I combined a Next.js frontend with a Node.js backend and a database stack spanning PostgreSQL and MongoDB. JWT and multi-role access control support the platform’s authentication and authorization needs.
Where the choices
matter.
Permissions as a foundation
Multi-role access control is a core platform capability. It makes user permissions part of the application’s structure.
Authentication
I used JWT as part of the authentication stack, supporting access to the platform’s role-based workflows.
What the evidence
supports.
Multi-role
Access control
JWT
Authentication stack
Scope & limitations
These links open the public React frontend edition. This case study describes the broader full-stack project from my résumé.