Aurionpro Solutions · Software Engineer Intern
I worked on SmartLender, lending software that commercial banks run their loans on. I made database releases work the same way across all three test environments, and shipped features in the product.
01The problem
Database changes moved between the development, testing and user-acceptance environments mostly by hand. That meant copy-paste mistakes, environments drifting apart, and long release days nobody could fully explain afterwards.
02What I built
Release scripts that take settings for each environment, so every release runs the same way everywhere: same script, different settings, same result. On the product side I shipped features for SmartLender Commercial, including hover previews that show a record's details without leaving the page.
03A decision that mattered
I built reusable scripts instead of one-off ones, so a correct release didn't depend on someone remembering every manual step.
04What I explored
I prototyped splitting parts of the large Oracle and Java codebase into smaller services that could be released on their own. It showed me the real trade-offs of changing a system banks rely on every day.
05How it links to my other work
It was my first taste of how careful releases are in enterprise software, where environments, approvals and change control are part of the job. That carried straight into NUS IT, where the audit trail had to satisfy real auditors.