The Trajectory
I believe in building software with a clear understanding of the problem and the business it serves, and in shaping business strategy with a deep understanding of the technology that enables it. My journey has been about expanding that intersection—from engineering and system design to leadership, business strategy, and now intelligent systems. Each step has strengthened my ability to connect technical depth with business objectives and turn that understanding into products and systems built for what comes next.
The Chapters
01 / Deep Engineering & Execution Systems
Over a decade in engineering gave me a strong foundation in building and operating complex software systems. I engineered enterprise mobile platforms, worked with memory-constrained environments, built APIs and backend systems, and designed systems where real-time data moved between connected devices and cloud services. This experience shaped how I approach engineering today: with a strong emphasis on simplicity, deterministic behaviour, edge cases, system reliability, and ownership of the outcome.
02 / Business Strategy & IIM Bangalore
I wanted to understand the decisions behind the systems I was building—not just how to engineer them. An MBA from IIM Bangalore expanded my perspective from architecture and execution to business strategy, value creation, market dynamics, and commercial decision-making. It strengthened my ability to connect technical choices with the business objectives they are intended to serve.
03 / The Future: Intelligent Systems & AI-Driven Workflows
Today, I am bringing these two perspectives together to build intelligent systems. I built an AI-native CRM end-to-end as a hands-on platform for applying AI to real system problems, evolving from deterministic, tool-based workflows toward RAG, contextual retrieval, AI agents, orchestration, and workflow guardrails. This is the direction I am building toward: engineering intelligent systems that combine strong technical foundations with a clear understanding of the business problem and the value they are expected to create.
