Post Trade Platform
Replacing a low-code SaaS with an in-house build, while strangling the API beside it into services.
Lead Engineer · Platforms & AI
Lead Engineer, 13+ years building platforms in enterprise banking. Java and enterprise systems first, then cloud, then platform engineering, now AI platforms.
Here for something specific?
Move your cursor over this area — the contour lines follow it.
Right now
Replacing a low-code SaaS with an in-house build, while strangling the API beside it into services.
An MCP layer giving AI agents authorised, scoped and audited access to data they must never reach directly.
A governed memory layer so agents remember what your team already decided.
Featured — personal project
Your AI agents should remember what your team decided. Select a stage to see what it means.
How I work
Four principles. Select a card to turn it over.
Selected work
A proof of concept, still defining where the value is. Today, tracing what someone did across separate platforms, systems and channels is a manual job that takes around 30 days. This unifies that trace into one place, so activity carried out with ill intent can be detected and reported in under five minutes. An LLM first looks for an innocent explanation for each event, then reviews the whole series to judge whether it looks like a one-off or a deliberate pattern. A supervisor makes the call.
Replaced a low-code SaaS post-trade platform with an in-house build, while strangling the internal API that grew up beside it into services.
A governed memory layer for AI agents. Stores engineering decisions and business requirements with authorship, rationale, conflict detection, authority weighting and a signed audit chain.
One surface over HR systems, building services, approvals and a SharePoint CMS — with consistency and accessibility enforced at a boundary rather than requested.
Thirteen years