Responsibility & architecture
Technical Lead across the platform. The scope below describes the application architecture and workflows, rather than attributing every feature to one engineer.
Constraints
Employee support and management reporting need distinct experiences. Organization-specific data access is a central boundary in the backend.
Separate workflow modules
Dedicated Express routes organize mood check-ins, appointments, learning and company administration behind a React and TypeScript frontend.
Engineering tradeoff: Separate modules make responsibilities easier to follow, while shared identity and authorization rules need consistent enforcement across them.
Company-scoped data access
A Firestore access layer scopes organizational records by company.
Engineering tradeoff: Scoping is an implementation boundary that must be tested for every access path; it is not, by itself, a privacy or security certification.
Architecture overview based on implementation scope. The tradeoffs describe engineering considerations, not measured outcomes.
Delivery context
The public product presents employee check-ins, resources, consultations and manager analytics. This case study describes technical scope; it does not claim measured wellbeing outcomes.
The challenge
Employees need accessible wellbeing support, while managers need a clearer view of team trends. WejdenSpire brings these two experiences into one platform.
Technical scope
I lead the technical work on WejdenSpire. The application uses React, TypeScript and Vite with a Node.js/Express API and Firebase. Its backend separates mood checks, appointments, learning paths and company administration into dedicated routes, with company-scoped Firestore access for organizational data.
Platform scope
The platform brings together mood and energy check-ins, educational content, expert consultations and manager analytics. These workflows support both employees seeking help and teams organizing workplace wellbeing initiatives.