I began as a software engineer at Wipro, building automation and data layers for telecom workflows. That gave me a technical foundation, but the more important lesson was how often useful software depends on understanding the process around it.

At EY, I worked on SAP Sales & Distribution transformations for retail and consumer businesses. Five years of requirements, process studies, blueprinting, testing, rollout, and training made operational ownership as important to me as system design.

At MedPiper, a YC-backed healthcare company, product strategy, platform work, operations, compliance, and hands-on building came together. I helped build the platform from the ground up, owned three product lines, worked across a growing cross-functional organisation, and reduced an insurance workflow from roughly four weeks to roughly ten days.

I now stay close to execution through independent products in document intelligence, local-first desktop software, audio workflows, evaluation systems, and spatial simulation. The common thread is not a specific model. It is turning ambiguity into a system people can operate and verify.

I am curious by default, direct about trade-offs, and happiest when I can take a problem from a rough conversation through workflow, interface, implementation, and release. I do not need to own every line of code, but I want decisions to stay close enough to reality that the product can survive contact with users.