About
The person behind
the systems.
I am a Mumbai-born, New York-based senior software engineer. My work sits at the intersection of backend platforms, cloud data systems, and AI infrastructure. The short version: I like building things that keep working when scale, ambiguity, and real users show up.
The journey
Mumbai
IndiaBorn and raised in a city that runs at full capacity and still finds a way forward. It gave me a practical feel for resilience long before I had the vocabulary for systems design.
Pune
IndiaStarted at Barclays on cards and payments infrastructure. Learned quickly that reliability is not abstract when real users, real money, and real support teams depend on your code.
New York
USAMoved for an NYU M.S. in Computer Science, then stayed for the work. New York sharpened the same instinct Mumbai started: build for pace, ambiguity, and systems that cannot pause.
Mumbai
IndiaBorn and raised in a city that runs at full capacity and still finds a way forward. It gave me a practical feel for resilience long before I had the vocabulary for systems design.
Pune
IndiaStarted at Barclays on cards and payments infrastructure. Learned quickly that reliability is not abstract when real users, real money, and real support teams depend on your code.
New York
USAMoved for an NYU M.S. in Computer Science, then stayed for the work. New York sharpened the same instinct Mumbai started: build for pace, ambiguity, and systems that cannot pause.
The throughline
I am drawn to systems that matter after the happy path ends. At Barclays, that meant payments, rewards, settlement flows, Kafka streams, and Kubernetes migrations where reliability was tied to real customer trust.
At Experian, it became cloud data infrastructure at a different scale: 300M+ consumer records, 100TB+ on AWS, Spark and Airflow pipelines, observability, and production AI workflows for operational teams.
The AI work is not a pivot away from systems. It is the next version of the same instinct: retrieval freshness, evaluation, guardrails, latency, cost, and failure recovery are all infrastructure questions. That is the story I want this site to tell.
Operate close to the failure modes
I like work where the messy parts are visible: retries, lag, stale data, noisy alerts, partial failure, and all the things architecture diagrams politely hide.
Make quality measurable
Whether it is RAG faithfulness, pipeline freshness, MTTR, or deployment frequency, I trust systems more when the important behavior is observable and reviewable.
Explain the system clearly
Toastmasters was not a side quest. I learned to communicate technical judgment with structure, context, and enough plain language for people to make decisions.
Build to understand
My best learning still comes from implementing the hard pieces myself: consensus, vector ingestion, eval harnesses, orchestration, and the trade-offs underneath the abstraction.
Outside engineering
The non-work parts still rhyme with the work: attention, curiosity, movement, and a habit of looking closely.
Photography
Nature first: early light, mountain trails, quiet frames, and places where the pace finally drops enough to notice details.
Travel
I like places that reset my assumptions. Moving countries once made unfamiliarity feel less like risk and more like range.
Reading
Systems design, distributed computing, AI infrastructure, and the occasional non-technical book where nobody argues about eventual consistency.
Building
Side projects that start as "let me understand how this actually works" and become small production-shaped systems.
Community & leadership
Engineering is technical, but influence is human. I have tried to get good at both.
Toastmasters International
"The best engineers I know are also the best communicators. I spent three years proving that deliberately."
Served as Chapter President and competed through area and district levels — winning accolades at both. Most engineers treat communication as an afterthought. I treated it as a skill with the same rigour as distributed systems: practice reps, deliberate feedback, measurable improvement.
CKAD NYC '26
Helping engineers get certified in Kubernetes.
Currently volunteering with the CKAD NYC '26 community — supporting engineers preparing for the Certified Kubernetes Application Developer exam through study sessions and mentorship.
TerraNYC STEM Fair
Reminded that curiosity is the real prerequisite.
Served as mentor and judge at the TerraNYC STEM Fair — evaluating student projects and working with the next generation of engineers and scientists.
Hackathons & recognition
Competitive builds under pressure. The constraints are the point.
SBI Hackathon
Predicting loan defaults
Built a machine learning pipeline to predict loan default risk, competing against teams across India.
Azure DevOps Hackathon
Browser extension for CI/CD control
Built a Chrome extension that surfaces Azure CI/CD pipeline controls directly in the browser — trigger builds, check status, and manage deployments without leaving the page.
Bhopal Smart City Hackathon 2.0
Smart city infrastructure
Selected as a finalist in a national-level smart city challenge.
Professionally
6 years building production systems: financial-grade Kafka at Barclays, then cloud data platforms and AI infrastructure at Experian. M.S. Computer Science from NYU. I bring backend and distributed systems discipline to the places where AI products need to be reliable, measurable, and operable.
Full experienceEducation
NYU · M.S. CS
2021 – 2023
Currently
Open to work
New York area · hybrid / remote
Say hello
Good systems start as good conversations.
About backend architecture, AI reliability, cloud migrations, trail recommendations, or new opportunities. Email is best.