College Management Platform
A platform that a UK college runs day to day, built by the team at my internship. I worked on the attendance side and then ran a structured bug hunt across the whole product. The code and the client are confidential, so this is the public-level picture.
What this is
A college management platform: the system a further-education provider uses for staff and students, from attendance and timetables through to records and reporting. One deployment serves one college. It is the main product I work on at TwelveTech Systems, so I can describe what it does and what I did, but not share the code or name the client.
What I did
I joined a codebase that already had real users, which changes how you work. My first stretch was on the attendance side: the self check-in flows that students and staff use every day, and the admin views that let a college see who is in and act on it. That meant working across the React front end and the Node API, with database changes reviewed before they went anywhere near production.
The second stretch was quality. I ran a structured bug hunt across the platform, reproducing each issue, grading it by severity and writing it up so the fixes could be ordered and picked up by the team. Some of those fixes were mine, on their own branches, with tests added so the same bug could not come back quietly.
What I learned
Shipping inside a product that already runs is mostly about not breaking things: small branches, review before merge, and tests that describe the behaviour a college depends on. I also learned that a good bug report is a product in itself. A clear reproduction and a severity that the team agrees with saves more time than the fix.
Stack
React on the front end, Node.js and PostgreSQL behind it, Playwright for end-to-end coverage.