QuantLink AI · Derivatives

An options desk, built into the stock page.

I built and shipped QuantLink's Options workspace, from a mirrored options chain to an interactive 3D implied-volatility surface, skew and term structure, across the product's data layer, API and web app. Then I profiled the volatility-surface pipeline and cut a cold catalog load from 6.2 s to 1.4 s.

Every options lens, one toolbar.

A single declarative spec drives the whole tab: each view binds one dataset to one presentation, so new analytics ship as configuration rather than new pages.

  • Views across chain, analytics, flow, market context and contract detail, with one-click quotes and Greeks presets.
  • Volatility views: an interactive 3D implied-volatility surface, a volatility topography, multi-expiry skew and ATM term structure, filterable by DTE, moneyness and quote quality.
  • A mirrored chain (calls, pinned strike, puts); clicking any bid or ask opens that contract's price, session VWAP and volume views.

Three codebases, one contract.

  • Data layer: an options data transport that meters vendor egress per HTTP call (a cache hit costs nothing) and caps every leg at the request's remaining deadline.
  • API: routes that fail closed with precise 422 / 502 / 503 answers, streaming rows to the browser as Apache Arrow.
  • Web: moved the options tables onto the product's shared table component, which had 57 consumers and no direct tests. I added a test baseline and default-off props, then proved byte-identical output across 17 real-consumer configurations.

Measured first, then made fast and honest.

Instead of raising timeouts, I profiled the volatility-surface request stage by stage and optimized what the numbers showed.

  • Profiling traced cold-start cost to a pure-Python YAML parse of the field catalog. Switching to the C-accelerated safe loader cut fresh-process hydration from 6.2 s to 1.4 s and setup from 13.3 s to 7.2 s, with output verified byte-identical.
  • Stage-level timing telemetry for each step of a request, privacy-safe by design; the last started stage stays visible even when a worker is killed.
  • Clear refusals: a request that fails before its first Arrow chunk returns a structured error with its run ID.