SYSTEM DESIGN / SELECTED WORK

Real workflows.
Clear system maps.

Each case study starts with the problem the system had to solve, then maps the data path, orchestration, retrieval, and runtime that made it useful.

05 SYSTEMSENTERPRISE · PHARMA · RESEARCH
01 / Multi-agent content system

Pharma asset generation engine

A governed generation workflow for pharma marketing teams. It combines agent handoffs, tool orchestration, and hybrid retrieval so generated assets stay grounded in the right brand and product context.

ZS Associates · US pharma$1M revenue influenced · 66% less manual effort
02 / Multimodal retrieval infrastructure

Scientific document knowledge layer

A retrieval layer for scientific files where the answer may live in a table, chart, formula, or a specific section of a long document. The system exposes small, composable retrieval tools for downstream agents.

ZS Associates · enterprise scientific documents10,000+ concurrent users · section retrieval within 5 minutes
03 / Human-guided agent workflow

Autonomous process interviewer

Turns meeting transcripts into a complete process record. The agent extracts what is known, identifies gaps, asks people for missing information, and generates a process report with a swimlane diagram.

Thomson Reuters · enterprise process capture90% reduction in manual reporting effort
04 / Natural language analytics

Brand analytics assistant

Routes a business question to the appropriate analytics space, translates it into a query, and returns a visualization. The aim is to move from a question to a useful view without hand-building each analysis.

ZS Associates · DatabricksBusiness analysis automation up 50%
05 / Scientific machine learning

Microstructure evolution forecasting

An autoencoder and ConvLSTM forecasting model that predicts how binary-alloy microstructure evolves over time, using a sequence of simulation images as input.

SURGE · IIT KanpurSimulation accelerated by 50%

DESIGN NOTE Enterprise diagrams are sanitized high-level views based on my work. They omit client data, private schemas, credentials, and proprietary implementation details.

HAVE A WORKFLOW WORTH FIXING?

Let’s make the
next step concrete.

Talk through the problem