A career built at the intersection of business and technology
Not a straight line, but a consistent thread — structuring ambiguous problems, then building the programs and platforms that solve them.
How I got here
I started as a computer engineer, then spent two years at ICICI Bank re-engineering business processes — my first real exposure to the gap between how a process is supposed to work and how it actually works on the ground. That gap has stayed interesting to me ever since.
A master's degree in IT & Management at the University of Texas at Dallas was where the business and technical sides of my thinking started to merge deliberately, rather than by accident. The decade that followed — building BI and data warehousing solutions for a payments company, a state government office, and a Fortune 500 telecom/tech firm — gave me a working fluency in data, systems, and the operational realities of very different industries.
Joining KPMG in 2016 is where those threads came together. As a Manager and later Senior Manager, I moved from building analytics solutions to owning entire transformation programs — accountable for the business case, the delivery, the governance, and the outcome, not just the technical piece. I led programs spanning healthcare data platforms, trade and customs automation, and government subsidy analytics, working directly with executives, government stakeholders, clinicians, and engineering teams to get complex things done.
More recently, AI has become the next version of a problem I already knew how to solve: a powerful capability that only creates value when someone does the unglamorous work of finding the right use case, fixing the data, redesigning the workflow, and earning people's trust to actually use it. I've been building that fluency deliberately — through NVIDIA's Generative AI certification, hands-on work with Databricks and Azure AI, and applying large language models to real problems inside my current role — while staying clear-eyed that my strength is operationalizing AI, not building models.
Today I'm based in the San Francisco Bay Area, looking for the next place to apply that same combination: strategy, data, technology, and the discipline to see it through to execution.
What I'm focused on now
How I work
- Start with the business problem, not the technology.
- Structure ambiguity before proposing a solution.
- Bring users, business leaders, and technical teams together early, not at the end.
- Design for adoption, not just implementation.
- Make ownership and decision rights explicit — most program delays are actually decision-rights problems.
- Measure business outcomes, not just project completion.
- Build reusable capability where possible, instead of solving the same problem once per client.
- Stay close to execution, even at a strategy level — the details are where plans actually succeed or fail.
A global perspective
My career has been built across three countries — starting in India, moving to the United States for graduate school, spending several years leading programs in Canada, and now based back in the U.S. in the Bay Area. Each move meant rebuilding a professional network and a sense of community from scratch, which has made me comfortable operating in unfamiliar environments, working across cultural and organizational norms, and getting to trust quickly with people who don't yet have a reason to extend it.
Outside of work
I'm a fairly curious person by default. I've spent the last couple of years learning tabla and guitar as an adult — which is a good reminder of what it feels like to be a beginner again, something I think helps rather than hurts as a leader. I like to hike and travel when I can; a recent hike up Arenal Volcano in Costa Rica was a good lesson in pacing yourself through discomfort instead of forcing the pace — a habit that's served me well in long programs, too.
I've also been quietly exploring a few product ideas — mostly around trade and tax problems I've seen up close in my consulting work — as a way of testing whether some of what I do inside large organizations could work as standalone products. Nothing formally launched yet, but it's part of how I think about where this career goes next.