Maybank Architecture & R&D
Embedded with the enterprise architecture team as a technology catalyst. Solution patterns, emerging approaches, and the case for change with the teams that had to live with it.
The builder
Most weeks I am the architect, the engineer, and the person explaining why the estimate was wrong. The problem does not split cleanly. Specialisation helps until it creates blind spots: the architect who has never read the production logs, the engineer who does not realise they are negotiating scope.
Across banks, insurance platforms, and startups, wearing several hats is not the problem. Wearing them without knowing you have switched is. The decision that makes sense in architect mode often breaks things in engineer mode. Knowing which context you are in is the discipline.
DivineForge is where that gets written down. Constraints, legacy systems, and timelines that were never realistic.
Embedded with the enterprise architecture team as a technology catalyst. Solution patterns, emerging approaches, and the case for change with the teams that had to live with it.
Architecture and delivery of a mobile-first roadside assistance app in insurance, from early design through production.
AI pipelines and workflow automation. What the technology holds up in practice, and what still needs work.
The lab that documents its own building. Architecture decisions, system builds, and lessons with the constraints left in.
Ki, Invest, Learn, Om. The playground and knowledge nexus. Engineering writing stays here.
Advisory
Written architecture reviews, cloud cost audits, and system teardowns. Async only.