Overview
At Sophos Solutions I built the entire frontend, from scratch, for a bank’s loan-management platform — the internal dashboard analysts used to run the full loan lifecycle. Regulated, mission-critical software, with the process discipline that implies.
Challenge
This wasn’t maintaining an existing UI; it was building a large, correct, consistent frontend from zero, for a domain where mistakes have real consequences. The dashboard had to support the whole lifecycle — creating applications, reviewing client information, checking credit status, searching large volumes of data, validating documentation, and approving or rejecting applications — all wired to existing backend services.
Constraints
A rigorous, banking-grade delivery process: everything went through code review, CI/CD, and QA before production, with strict validation gates and the bank’s defined processes to comply with. The backend services already existed, so the frontend had to work with their contracts — not the other way around.
Architecture
I built the Angular interfaces from the UX/UI designs and made the business flows work end to end. Consistency, data validation, and state management were treated as first-class concerns — in banking software these aren’t polish, they’re the product. Keeping a large frontend consistent came down to reusable components and standards applied throughout.
Implementation
The flows were wired to the existing backend services, end to end. When the frontend needed data the API didn’t expose well, I collaborated on backend/API improvements rather than forcing workarounds into the UI — fixing problems at the layer that owned them.
Lessons
Working to banking-grade standards — review, CI/CD, QA, strict validation gates — permanently raised my bar for what “production-ready” means. And building a large app from scratch under those constraints taught me that disciplined, consistent frontend architecture isn’t overhead in regulated software; it’s the difference between shipping and not.