Finance × Data × Technology

Turning financial complexity into usable intelligence.

I build software and quantitative systems for financial markets. MS Finance candidate at W. P. Carey, BS Computer Science from the Ira A. Fulton Schools of Engineering at ASU.

Chaitanya Singh
Chaitanya SinghFinance + Computer Science

Arizona

MarketsRiskDataSystemsResearch

The practice

What I work on

Financial reasoning, quantitative methods, and product engineering brought into one working system.

01

Financial analysis

I study how businesses allocate capital, report performance, and create or absorb risk.

  • Corporate finance
  • Valuation
  • Financial statements
  • SEC filings
  • Capital budgeting
  • Risk and return
02

Quantitative systems

I build models and pipelines that turn market behavior into measurable, testable signals.

  • Volatility modeling
  • Monte Carlo simulation
  • Regime detection
  • Risk calculations
  • Market data pipelines
03

Product engineering

I build the infrastructure and interfaces that move analysis from a notebook into useful decisions.

  • Backend architecture
  • APIs
  • Data infrastructure
  • Applied machine learning
  • Clear interfaces

Current focus

Now

September 2026

01

I am deepening my finance and accounting coursework at W. P. Carey.

02

I am building quantitative and machine-learning systems for market analysis.

03

I am making financial analysis understandable to people without a finance background.

Analysis in progress

Research notes

All writing

Jul 22, 2026

Completing Apex Arena: Shipping the Live Data and Replay Stack

Apex Arena is complete: a production Formula racing experience with resilient data handling, replayable race rooms, and a verified delivery path.

Read note

Jul 8, 2026

Fine-Tuning Is a Lifecycle, Not a Training Run

How to operate an adapted model with evaluation gates, versioning, monitoring, and a disciplined rollback path.

Read note

Jun 17, 2026

Choosing Full Fine-Tuning, Adapters, or LoRA

A decision guide for selecting an adaptation strategy based on task shift, cost, inference constraints, and operational needs.

Read note

Operating principles

How I build.

Technology should handle the complexity. The user should receive clarity.

01

Curiosity

Start between disciplines and follow the question wherever the evidence leads.

02

Clarity

Make complexity legible without removing the nuance that matters.

03

Trust

Show sources, limits, assumptions, and uncertainty.

04

Execution

Build beyond the first demo and design for the work of operating it.

The through line

Finance is the domain. Software is the instrument.