Hello, I'm Prasoon

I build practical machine learning systems that survive contact with reality.

Focus
Applied ML, causal inference, A.I. products
Currently
Open to thoughtful ML & data science roles
Based in
Boston, MA | Remote-friendly

About

I work on the parts of machine learning that have to work when the paper ends: turning messy, shifting data and ambiguous goals into well-posed problems, robust pipelines, and models that actually get used.

My experience spans experimentation, causal inference, and production ML systems: defining metrics, designing experiments, building features, and partnering with engineers and stakeholders to ship data products that move the right numbers, not just the easy ones.

I care about clarity: clear problem statements, clear interfaces between models and product, and clear communication with non-technical partners. This site is intentionally minimal – a small set of projects that show how I think, not an exhaustive catalog.

Experience

  1. Senior Machine Learning Scientist Product Company 2022 – Present

    Leading applied ML work for user-facing products: defining problem statements, designing experiments, and taking models from notebook to production in close partnership with engineering.

  2. Data Scientist Analytics & Growth Team 2019 – 2022

    Owning metrics, experimentation, and causal analysis for core product surfaces, helping teams choose sensible metrics and avoid being misled by noisy data.

  3. Research Assistant University Lab 2015 – 2019

    Working on ML and statistics-heavy projects with faculty and peers, focusing on reproducible analysis, careful evaluation, and clear write-ups.

Selected projects

A few applied ML projects from the last few years. Happy to share deeper write-ups, notebooks, or code samples on request.

Signal Ledger

End-to-end demand forecasting replacing spreadsheet heuristics with probabilistic forecasts and uncertainty-aware planning.

Forecasting · Product impact
Role
Machine learning scientist, tech lead
Year
2025
Highlights
Feature engineering, time-series modeling, stakeholder calibration
Request forecasting case study

Experiment Atlas

Unified experimentation framework standardizing metrics, power analysis, and guardrail checks across growth and product teams.

Experimentation · Uplift
Role
Data scientist, experimentation lead
Year
2023
Highlights
A/A tests, CUPED, standardized experiment review process
View experimentation notes

Reader Studio

Content embeddings and lightweight re-ranking powering a reading environment optimized for sustained engagement over raw click-through.

NLP · Personalization
Role
Machine Learning scientist, product partner
Year
2022
Highlights
Embeddings, offline evaluation, human-in-the-loop feedback
Explore NLP concept notes

Notes & writing

Occasional notes on applied machine learning, evaluation, and making models behave in the real world.

When your metric fights your product

A field guide to noticing when an optimization metric is quietly misaligned with the real outcome you care about.

Evaluation · Practice
Published
2025
Length
~7 min read
Topics
Evaluation, product thinking
Read article

Designing experiments you can actually believe

Lessons from running experiments in messy products: guardrails, pre-registration, and why celebrated uplift often misleads.

Experiments · Causality
Published
2024
Length
~10 min read
Topics
Experiment design, causal inference
Read article

The quiet parts of an ML system

Feature stores, data contracts, monitoring, and the unglamorous pieces that decide whether a model survives in production.

Systems · ML in production
Published
2023
Length
~8 min read
Topics
Production ML, reliability
Read article

Two GitHub Accounts, One Laptop: A Clean Isolation Setup

A practical setup for isolating personal and work GitHub contexts so folder path, SSH alias, and CLI wrapper decide account automatically.

GitHub · Workflow
Published
2026
Length
~8 min read
Topics
Git config, SSH, GitHub CLI
Read article

Contact

For roles, collaborations, or interesting ML problems, email is best. A short note about the problem space, your data, and how success is measured is especially helpful.

Elsewhere: feel free to connect via GitHub, arXiv, or LinkedIn if you prefer. I'm always happy to talk about evaluation, experiment design, or making ML systems a little more honest.