somnathmukherjee

Systematic trader and quantitative researcher focused on algorithmic execution in Indian markets. I work on: • Designing and validating rule-based trading systems • Robust backtesting with walk-forward and Monte Carlo analysis • Slippage and execution modeling for NSE instruments • Building production-grade Python execution stacks using broker APIs • Risk-layer engineering (position sizing, capital allocation, drawdown controls, kill switches) My primary interest is in building resilient, risk-managed systems rather than optimizing for headline CAGR. I’m particularly focused on robustness, capital efficiency, and deployment discipline. Currently working on: – Strategy licensing (code-only, no signals) – Algorithmic execution infrastructure for systematic traders – Quant research and validation services Happy to discuss: • Execution architecture • Risk modeling • Backtesting methodology • Infrastructure best practices Not offering tips, discretionary signals, or advisory services.

About

Username
somnathmukherjee
Joined
Visits
48
Last Active
Roles
Member

Activity

  • Systematic trader and quantitative researcher focused on algorithmic execution in Indian markets.

    I work on:

    • Designing and validating rule-based trading systems
    • Robust backtesting with walk-forward and Monte Carlo analysis
    • Slippage and execution modeling for NSE instruments
    • Building production-grade Python execution stacks using broker APIs
    • Risk-layer engineering (position sizing, capital allocation, drawdown controls, kill switches)

    My primary interest is in building resilient, risk-managed systems rather than optimizing for headline CAGR. I’m particularly focused on robustness, capital efficiency, and deployment discipline.

    Currently working on:
    – Strategy licensing (code-only, no signals)
    – Algorithmic execution infrastructure for systematic traders
    – Quant research and validation services

    Happy to discuss:
    • Execution architecture
    • Risk modeling
    • Backtesting methodology
    • Infrastructure best practices

    Not offering tips, discretionary signals, or advisory services.
    February 28