VEC Website Backend
Production backend engineering and team leadership.
Context
The VEC website combined production engineering with a student technical-leadership role. It needed backend services for institutional content and application workflows, and a codebase that could pass to the next cohort.
As Vice Chairman and Lead Backend Developer in WebOps, I helped lead a 17-member team. That describes the collaborative setting; it does not imply that I personally implemented every part of the website.
My contribution
My responsibilities included backend architecture, database schemas, authentication, and REST API development using Node.js, Express.js, MongoDB, and Mongoose. The backend work covered more than 50 RESTful endpoints and integration with the MERN application.
The work also involved access controls, AWS deployment, CI/CD, and monitoring, connecting feature development with maintaining a usable production service.
Engineering and continuity
Team coordination, code review, and documentation were part of the engineering process. Consistent interfaces and understandable backend modules helped integrate frontend and backend work.
Mentoring and handover were important responsibilities. The website needed continuity beyond the original contributors, so explaining the architecture and development practices was part of my contribution.
Scope and evidence
This describes production website and backend work, not independently measured uptime, security certification, or a quantified speed improvement. The historical project page preserves additional context.