Case study · Internship
OKRa — Internal Work Tracking Platform
- Client
- Mashup Technology Ventures Inc.
- Role
- Software Engineering Intern / Full-Stack Developer (OJT)
- Timeline
- May 2026 – Jul 2026
A department-first collaborative work-tracking platform built during a software engineering internship, connecting shared workspaces, workflow columns, tickets, permissions, attachments, realtime updates, and administrative oversight.
- 32
- Current route handlers across frontend and API workflows
- 21
- Database migrations supporting the platform data model
- 83
- Automated test files across API, database, auth, UI, accessibility, and E2E workflows
Stack
- Next.js App Router
- React
- TypeScript
- PostgreSQL
- Drizzle ORM
- Zod
- Auth.js/NextAuth
- S3-compatible storage
- Server-Sent Events
The brief
OKRa is a department-first collaborative work-tracking platform for organizing workspaces, workflow columns, tickets, cross-department sharing, comments, labels, activity history, invitations, attachments, and administrative oversight.
Full-stack delivery
The work connected reusable React workflows, Next.js route handlers, shared TypeScript/Zod contracts, and a PostgreSQL/Drizzle data model.
- 32 current route handlers across frontend and API workflows.
- 21 database migrations supporting the platform data model.
- Shared validation contracts kept frontend and backend behavior aligned.
Authentication and authorization
The platform required security-sensitive access control across users, workspaces, and administrative workflows.
- Auth.js credential sessions with session versioning and route protection.
- Role- and workspace-scoped permissions for protected workflows.
- Password and invite flows, database-backed rate limiting, and administrative safeguards.
Storage and realtime behavior
File handling and collaboration workflows were designed around failure-aware server behavior and timely board updates.
- S3-compatible attachment and avatar storage with upload validation and per-kind size controls.
- Staged persistence, protected preview/download behavior, missing-object handling, and recovery states.
- Realtime board updates through Server-Sent Events and PostgreSQL LISTEN/NOTIFY.
Quality and maintainability
The project established a broad automated test surface covering both application behavior and user-facing quality concerns.
- 83 automated test files across API routes, database behavior, shared schemas, authentication, responsive UI, accessibility, keyboard interaction, and end-to-end workflows.
- Clear monorepo boundaries separating the Next.js application, PostgreSQL/Drizzle database package, and shared TypeScript/Zod contracts.
Outcome
The result is a production-oriented work platform demonstrating end-to-end engineering across product workflows, data modeling, security, file handling, realtime behavior, testing, and maintainable project boundaries.