Sandeep Menon

I got into engineering to build things people actually need. At D.Y. Patil I got to do that again and again: a coordination app for a national-level event our college hosted, and an app that gave villagers one place to reach essential services.

At TCS, honestly, I made mistakes, and every one taught me how systems behave at scale: one bad load can quietly break every report downstream. That's where I understood data engineering isn't just a job. It's understanding how the whole system works, because a lot of people depend on it.

I went to USC to go deeper, into distributed systems, machine learning and where they meet. At Visa I owned several pipelines end to end, from ingestion to the features ML models trained on, and learned that the hard part isn't moving data fast, it's being able to rerun it safely. I built them to be idempotent and made sure data quality was never compromised. At Citi, I build Snowflake platforms and an AI agent that investigates data issues on its own.

All of that changed how I think. I don't just ask how to fix a problem today; I ask how the fix holds up a year from now, when the data has doubled and the people relying on it have changed. I use AI every day to move faster, but nothing ships until I've reviewed it, because if people are going to trust the data, I have to trust the code first.