Skip to the content.

HOME | CV PORTFOLIO | 2026-2025 | 2023-2021 | 2020-2013 | 2013-2008 | 2007-2003 | 2003-2000

PORTFOLIO

This section outlines the projects I have been involved in during the period 2025 – 2026.

(CIBC) Swaps Pricing

_ Period _: May ’25 – May ’26

_ Length _: 1 year

_ Team Members _: 2 Quant Devs, 1 Quant Product Lead, 3 Desk Devs, 1 Quant Trader, 1 Desk Dev Lead, 2 Broadway Devs, 2 Platform Devs

_ Technologies _: C#, .NET 9, ASP.NET Core, nUnit, C++ Analytics Interop, Pricing Object Graph, Solace MQ, SolCache, Bloomberg B-PIPE, SQL, MongoDB, Elastic/Kibana, Grafana, KDB+/q (RDB, IDB, HDB), Excel/xlOil, Python, JavaScript/HTML

_ Environments _: Windows, Linux containers

_ Methodology _: Direct Trading Desk interactions, Agile, Micro Services, TDD

_ Consultancy Experience: _ Analyst Developer, Quant Developer, IR Swaps Pricing, Yield Curve Construction, e-Trading RFQ

_ Description _:

Alma is CIBC’s strategic real-time interest rate swaps pricing platform for the electronic fixed income (e-FI) business. AlmaMarks consumes live market data from Bloomberg B-PIPE and trader quotes over Solace, providing a Python-powered Excel interface for traders to manually mark instruments and configure yield curve nodes that feed the core curve build. AlmaPricer continuously builds the yield curve (CAD O/N, multicurve USD setup: O/N, Fed Curve) by supplying live market rates to invoke the Quant C++ analytics library. It streams indicative swap rates across trader-configured sources from 1D to 50Y to Bloomberg, prices client RFQs, publishes key pricing metrics (PV and risk) to Bloomberg and KDB.

Alma went live in late Q3 2025 and replaced the legacy pricer in phases, running in parallel until final cutover in mid-2026. Migrating Alma from a standalone C# prototype into the bank’s shared C# PLATFORM framework unlocked reusable capabilities, including advanced Solace messaging features, standardized bootstrapping and containerisation. This integration inherently boosted service robustness and trader confidence by aligning Alma with bank’s strategic risk platform architecture.

Key engineering challenges included handling high frequency curve recalibration (input rates updating ~10+ times per second against a Bloomberg theoretical cap of several updates per second) while Alma must reprice on every tick yet publish within system limitations. Additionally running dual pricers in production required complete end-to-end visibility across market data feeds, curve builds, and publishing execution prices, driving the construction of an observability estate (Elastic dashboards, KDB dashboards and Grafana).

Progression:

Skills Required:

_ Projects _:

PLATFORM Integration

Delivery Summary:

Delivery Journal:


Streaming Curve Build

Delivery Summary:

Delivery Journal:


Market Data & Connectivity

Delivery Summary:

Delivery Journal:


AlmaMarks Calculators

Delivery Summary:

Delivery Journal:


RFQ Pricing

Delivery Summary:

Delivery Journal:


Curve Configuration

Delivery Summary:

Delivery Journal:


Bond Roll Epic

Delivery Summary: AlmaMarks yield curve configuration is configured by traders such that the long end of the curve is anchored by OTR benchmark government bonds. As benchmarks are replaced and futures contracts approach expiry, the instrument set has to roll with them. Done by hand, that is operational risk and a source of stale marks. This epic automated the rolls in AlmaMarks and the main focus of the pricing accuracy and the final months of the engagement.

Delivery Journal:


Production Monitoring I & Debugging Pricing Graphs

Delivery Summary:

Delivery Journal:


Production Monitoring II – KDB+/Grafana Dashboards

KDB captures every market-data tick and every price Alma publishes. Building Grafana dashboards on it gave the desk and support a view of curve inputs, published prices and RFQ flow across intraday and historical ranges. I learnt KDB+/q from scratch for this story.

Delivery Summary:

Delivery Journal: