Chandra Sekhar MulluDeveloper · Systems & Quant

DISTRIBUTED SYSTEMS · OPEN SOURCE · QUANT

Hi, I’m Chandra.
I like building things
that change things.

I’m a developer working with Python, distributed systems, and data. These days, I’m exploring AI and crypto, and building open-source tools. I’m interested in work closer to the trading desk, especially research tools, market data, and the systems that support trading.

Previously Millennium · 2022–2026
Before that, Marsview.ai, acquired by Eltropy.

01 / SIDE PROJECTS

A few things
I’m building.

These are the projects I’d start with
if you want to see how I work.

PYTHON / QUANTITATIVE RESEARCH

Portfolio Pulse01

A Python app for exploring portfolios and testing ideas.

In Portfolio Pulse, I work on portfolio analytics and backtesting: returns, drawdowns, risk, allocations, and trading costs. I keep the calculations separate from the Streamlit interface so they can be tested on their own.

PythonNumPy / pandasSciPyStreamlit

HOW A BACKTEST WORKS

  1. ObserveSignal at close t
  2. ExecuteNext common close
  3. AccountCosts, cash & holdings
  4. InspectLedger + validation

This is a research app. It uses daily adjusted prices and simulated trades, so the results depend on the data and assumptions you choose.

A few decisions behind the code

The maths lives outside the UI. I can check the portfolio and backtest calculations with small, repeatable inputs, without starting Streamlit or fetching market data.

A signal isn’t a trade. The backtest executes a decision at the next common close. It tracks drifting holdings, pays costs from the portfolio, and leaves unused capital in cash.

Fitting and testing are different steps. Walk-forward allocation uses earlier prices to estimate weights, then evaluates them on later observations. The choice of assets and data still affects what you can conclude.

Read the accounting and timing regression tests ↗
AI TOOLS / DATA INFRASTRUCTURE

Igloo02

An experiment in building software with AI.

I used AI coding tools for all of Igloo’s implementation. It’s written in Rust, which I don’t currently know. It uses DataFusion and Arrow to query PostgreSQL and Parquet together, accept queries from PostgreSQL clients, and cache results in memory.

RustDataFusionArrowPostgreSQL

FOLLOW THE QUERY

PostgreSQLParquet
IglooPlan · push down · execute
Arrow record batchesIn-memory LRU + TTL cache

Igloo currently runs in one process. Distributed execution and Apache Iceberg integration are still on the roadmap.

A few decisions behind the code

A faster query still has to give the same answer. DataFusion rechecks pushed filters locally. String ordering stays local because PostgreSQL collation can disagree with Arrow ordering.

The cache keeps Arrow batches. It shares the result representation used by the engine, with an entry limit, TTL, and LRU eviction.

It’s still an experiment. JSON change-event files invalidate the cache today. A separate draft preview includes agent interfaces, broader ADBC support, and native CDC foundations.

Read the differential query tests ↗

02 / EXPERIENCE

Where I’ve worked.

JUL 2022 — FEB 2026

Millennium

Quantitative Developer

Enterprise Risk Technology

I joined the team early and took systems from design through implementation and production. My work covered risk calculations, shared data tools, and compute infrastructure.

  • A distributed stress-calculation framework covering 2M+ positions and 4,000 scenarios.
  • A risk calculation library using Apache Arrow, with Python and Java bindings.
  • On-demand Ray/Dask clusters, including resource quotas and cost-aware autoscaling.
  • A shared data-orchestration library used by 100+ developers, along with event-driven pipelines for risk reporting.
  • Plotly Dash interfaces for risk users and the deployment pipeline behind them.

AUG 2021 — JUN 2022

Marsview.ai

AI Backend EngineerAcquired by Eltropy

Real-time AI services

I built and deployed NLP services for real-time text, audio, and video analytics. I also worked on API integrations with Eltropy One for financial-institution messaging.

One performance project involved caching token embeddings in Redis to reduce repeated work in the asynchronous processing stack.

2M+positions in a distributed
stress-calculation framework
4,000scenarios supported by
the stress framework
100+developers using a shared
data-orchestration library

Some of the work I did at Millennium.
The projects below are my public work.

03 / TOOLS & BACKGROUND

What I work with.

B.Tech, Computer Science
IIIT Nuzvid · 2018–2022 · 8.73 CGPA

Quant & research

Python · SQL · NumPy · pandas · Polars · SciPy
Portfolio analytics · Risk metrics · Plotly Dash · Streamlit

Compute & data

Ray · Dask · Event-driven ETL · Apache Arrow
PostgreSQL · Redis

Production delivery

AWS · Linux · Docker · Kubernetes
pytest · GitHub Actions · CI/CD

SAY HELLO

Have something
in mind?

If you’re building trading tools, research platforms, or market data systems, I’d like to hear about it. I’m interested in roles closer to the trading desk, and I’m always happy to talk open source.