The stack decision was deliberate. A MEAN configuration with MeteorJS reduced the surface area between frontend and backend state management, which mattered given the volume of conditional views and role-specific rendering the application required. The frontend was built on Angular using component-based design, ES6 modules, and lifecycle hooks. I established the module architecture in writing before development began, defined the core service layer (AuthService, UserService, RoleService, EmailService, UtilityService), and set the patterns the team used throughout. I led scope prioritization in Jira, which was non-trivial given a backlog that shifted daily as client requirements evolved.

The feature surface included advanced-filtering certification and user lists, a document upload system backed by AWS S3, account and workflow email templates, multi-step approval logic, and an administrative interface for runtime configuration. Form components received particular attention: the approval workflow depended on reliable, stateful form handling, and component inputs and outputs were used to keep state predictable across views. ESLint enforcement and a staging environment were in place before production deployment.