Some people write about themselves. I'd rather let the mathematics do it.
I didn't start with machine learning. I started with a question — why do systems fail when the data gets harder?
That question led me to IIIT Agartala (B.Tech CSE, 2027), then to a research internship at IIIT Allahabad, and eventually to a stage at the Springer MICA 2025 International Conference where I presented my first research paper.
Along the way, I became a Hackathon Finalist at IIT Kharagpur and the University of Hyderabad.
But more than credentials — I became someone who reads loss curves the way others read stories. Every dip is a chapter. Every plateau is a problem worth solving.
At IIIT Allahabad, I worked on a problem that looked simple on paper but wasn't: predicting heart disease from clinical data where the positive class barely existed.
Most models would learn to ignore it entirely. High accuracy. Zero usefulness. That's the quiet deception of imbalanced learning —
I refused to accept that tradeoff.
The result was a paper — "Stacking Inside Voting: A Hybrid Ensemble for Heart Disease Prediction" — published in Springer Proceedings at MICA 2025.
A hybrid architecture that turned a broken
I reason like Bayes — I don't arrive at conclusions, I update toward them. Every new piece of data shifts the posterior:
I believe most models fail not because they can't fit — but because they fit too well. Memorisation dressed as intelligence. Regularisation is the discipline that separates the two:
And I pay attention to what a model doesn't know as much as what it does. Uncertainty isn't a weakness — it's information:
A confident wrong answer is worse than an honest uncertain one.
I work across the full depth of the ML pipeline — from raw tensors to deployed APIs, from research notebooks to production containers.
| Layer | Tools |
|---|---|
| Languages | Python · C · C++ · SQL |
| Deep Learning | PyTorch · TensorFlow · HuggingFace · CNNs · RNNs · Transformers |
| LLM Fine-Tuning | LoRA · QLoRA · PEFT · Unsloth · BitsAndBytes · TRL SFTTrainer |
| Classical ML | Scikit-learn · XGBoost · Ensemble Methods · SMOTE · Feature Engineering |
| MLOps | MLflow · Docker · GitHub Actions · AWS EC2/ECR · DagsHub · CI/CD |
| Serving | FastAPI · Flask · Streamlit · REST APIs |
| Data | NumPy · Pandas · Matplotlib · Seaborn · MongoDB · SQL |
There is one problem in machine learning I keep returning to — the one that sits at the boundary between memory and adaptation.
Catastrophic forgetting.
When a model learns something new, it quietly destroys what it already knew.
Train on
This should go to zero. It rarely does.
I'm working on Dynamic Self-Growing Continual Learning (DSGCL) — a graph-based architecture where the model doesn't replace old knowledge. It grows around it.
New tasks add new nodes. Edge gates
Plasticity and stability. Not a tradeoff. A single objective.
The belief I build everything on:
I'm actively looking for ML Engineer, Data Scientist, and Applied Scientist roles where research depth meets production reality.