Software Systems

In development

CMU Academic Resource and Mentorship Platform

Timothy serves as lead full-stack engineer and service vendor for a Carnegie Mellon University platform combining mentor connections, personalized resources, direct messaging, and AI-assisted resource discovery.

Outcome
Leads an active commissioned development effort for a student-support platform; the product remains in development.
Timothy’s contribution
Timothy leads full-stack delivery across the mentor-connection system, personalized resource portal, direct messaging, AI-assisted discovery, and the platform's Next.js, Tailwind CSS, Supabase, and Gemini API stack.
Role
Service Vendor / Lead Software Engineer
Institution
Carnegie Mellon University
Date
June 2026–Present
Technologies
Next.js, Tailwind CSS, Supabase, Gemini API
Methods
Full-stack application architecture, Mentor-connection workflows, Personalized resource delivery, AI-assisted resource discovery, Commissioned product development
Related experience: Service Vendor / Lead Software Engineer

Problem and constraints

The platform brings several forms of academic support into one coordinated system: finding a mentor, receiving relevant resources, communicating directly, and discovering additional material with AI assistance. That combination creates a systems problem across interface design, data-backed workflows, communication, and an external AI service.

Because the engagement is commissioned and still in development, the public case study maintains a strict boundary around nonpublic material. It does not link a repository, invent interface details, or expose implementation information beyond the approved capabilities and verified stack.

Timothy's role

As service vendor and lead full-stack engineer, Timothy is responsible for directing the application architecture and delivering the connected product workflows. His role combines hands-on engineering with the translation of institutional requirements into a coherent platform.

Technical architecture

The verified architecture divides responsibilities across four public stack elements:

  • Next.js provides the application framework for the connected portal and communication workflows.
  • Tailwind CSS supports the interface layer.
  • Supabase supports the platform's data-backed application needs.
  • The Gemini API supports AI-assisted resource discovery.

The architecture is described at this boundary because the underlying repository is nonpublic. No additional services, data models, or implementation claims are inferred.

Delivery constraints and engineering boundaries

Timothy is developing the system as commissioned professional work rather than as a public prototype. Public documentation therefore names the product goals, his role, and the verified stack while keeping source code and unapproved product surfaces private.

The in-development label also prevents planned capabilities from being mistaken for a completed release. Mentor connection, personalization, messaging, and AI-assisted discovery are the approved system scope; this case study does not attach unverified completion or usage metrics to them.