Portfolio Risk Management at GIC

Summary

Six months at GIC Pte Ltd as an Associate Software Engineer. Worked on an internal portfolio risk management system that gave fund managers improved risk exposure insights for investment decisions. Implemented data pipelines and analytical tools in Scala and Java, and integrated BarraOne — MSCI's research-driven risk platform — with GIC's internal systems alongside Zenika consultants.

What I learned

Sovereign-wealth-fund engineering culture is its own thing. The tolerance for risk in code roughly matches the tolerance for risk in the portfolio: very low. Code reviews were thorough.

BarraOne integration was my first deep work with a third-party financial risk platform. Lesson: vendor systems carry baked-in opinions about how risk should be measured, and integrating them is partly a translation problem and partly a "do we agree with this opinion?" problem.

Scala and Java side by side was instructive. Scala for the pipelines (concise, expressive), Java for the integration surfaces (predictable, easier for the team). Mixed-language codebases work if the boundaries are clear.

I left after six months — not because GIC was bad (it wasn't) but because I was ready for something more cloud-native and less compliance-heavy. SPH was the next move.