MPA COACHING.
Educational mentorship and placement organization managing connections between candidates, corporate hosts, and career mentors.
What is the product / business?
Educational mentorship and placement organization managing connections between candidates, corporate hosts, and career mentors.
What friction existed?
Manual matching, disconnected email threads, and untracked student progress caused administrative overhead and poor participant retention.
How did people work before?
Admins spent hours manually matching students to industry hosts via spreadsheets, coordinating interview schedules across disparate calendar invites, and tracking training completion manually.
What did I design & build?
Built a multi-portal platform with dedicated role-based views for Students, Hosts, and Admins, centralizing application workflows, milestone tracking, and communication.
What did I personally execute?
Engineered the frontend application using Next.js and React, established role-based access flows, structured reusable portal layouts, and built progress tracking dashboards.
Core stack & architectural decisions
FRONTEND
- React
- Next.js
- TypeScript
- TanStack Query
- Redux
- Mantine UI
Critical choices made during development
Developed dedicated, scoped portal experiences for each stakeholder to prevent interface clutter.
Implemented centralized data queries with cached invalidation so admin actions immediately reflected in student portal dashboards.
Verified Impact
Replaced messy spreadsheet management with an automated portal that gives students, mentors, and administrators clear visibility into coaching cycles.
Takeaway
When designing multi-stakeholder software, segmenting workflows by user context prevents feature sprawl and reduces onboarding confusion.