About

My journey into technology wasn't planned.

In 2005, I was preparing for an MBA when one of my closest friends suggested that I also apply for the MCA entrance examination. I filled out the application almost casually, never imagining that a single decision would shape the next two decades of my professional life.

What started as an alternative career option soon became a lifelong passion.

During my first internship, I built a simple Leave Management System for internal employees. It wasn't a large project, but seeing people actually use software that I had written gave me a feeling I still remember today. It taught me something that has stayed with me throughout my career: software is meaningful only when it solves real problems for real people.

That curiosity has guided every major career decision I've made ever since.

Over the last 17+ years, I've had the privilege of solving engineering challenges across a diverse range of industries—including commercial printing, digital typography, financial software, hospitality, building automation, IoT, warehouse robotics, and now Enterprise AI. Although the business domains have changed, one thing has remained remarkably consistent: I've always been drawn towards solving complex engineering problems rather than simply building software features.

My career began with low-level C and C++ development, where I developed a strong foundation in systems programming, algorithms, performance optimization, multithreading, memory management, and software design. Those early experiences continue to influence how I approach software architecture today. They taught me that elegant designs, thoughtful abstractions, and simple solutions often outperform unnecessarily complicated systems.

As my career evolved, so did my responsibilities. I gradually moved from writing software to designing systems, leading engineering teams, building products from the ground up, working directly with international customers, and translating business challenges into scalable technology solutions. Along the way, I had the privilege of working onsite with customers in Germany, Sweden, the United States, the United Kingdom, and the Netherlands, collaborating with global engineering teams across multiple domains.

One of the earliest confidence boosters in my career came during my time at Thomson Digital, where I was entrusted with end-to-end ownership of multiple modules—from requirement analysis and solution design to development and delivery—much earlier than I had expected. Those opportunities gave me the confidence to take ownership, work directly with stakeholders, and look beyond individual coding tasks towards delivering complete business solutions.

A significant phase of my professional growth happened at Nagarro, where I had the opportunity to build and technically lead offshore engineering teams for two global product organizations. Working as an extension of the customers' product engineering teams, I was actively involved in engineering planning, execution planning, and long-term roadmap discussions alongside the customers' project leadership teams. Those experiences shaped my approach to technical leadership and taught me how successful products are built through close collaboration between engineering and non-engineering teams.

The next defining chapter of my career began when I joined GreyOrange during the inception of its Assisted Picking product category.

I had the opportunity to be part of the complete journey—from validating product ideas and evaluating robotics platforms to architecting the software, building and leading engineering teams, supporting customer deployments, and scaling the platform into a globally deployed warehouse automation solution.

What started as a focused product gradually evolved into a comprehensive Assisted Picking product category, supporting multiple warehouse workflows and business use cases. That evolution is reflected in its own journey—from Ranger Assist to Pick Assist and ultimately Assisted Picking—as the platform expanded from solving a specific warehouse problem into enabling a broader category of intelligent warehouse automation solutions.

The experience extended far beyond software engineering. It involved product strategy, warehouse operations, robotics integration, customer solutioning, pre-sales engagements, cross-functional collaboration, engineering leadership, and on-site customer go-lives. The platform eventually reduced warehouse fulfilment costs by approximately 30%, supported multiple enterprise deployments, and resulted in a patent on which I am proud to be a co-inventor.

Beyond building software, GreyOrange taught me how to build products, engineering teams, and customer trust simultaneously—an experience that continues to influence how I approach technology leadership today.

Throughout my career, I've rarely viewed engineering through the lens of a single job title. Depending on what the business needed, I've worked as a software engineer, architect, technical lead, engineering manager, product leader, customer-facing solution architect, mentor, interviewer, and occasionally even an implementation engineer working directly at customer sites. I enjoy wearing multiple hats because successful products are built through collaboration across engineering, product, operations, and customers—not through software development alone.

Despite moving into leadership roles, I've consciously remained a hands-on engineer. I continue to enjoy designing distributed systems, building critical components, reviewing architecture, writing code, mentoring engineers, evaluating technologies, and solving production problems. I believe technology leaders make better decisions when they stay close to the engineering challenges their teams face every day.

Today, my primary focus is Enterprise AI.

I'm currently architecting an Enterprise AI Data Platform focused on one of the most fundamental challenges in modern AI: building trusted, governed, and high-quality enterprise data ecosystems that power the next generation of intelligent AI systems. The platform combines modern data engineering, AI, and cloud-native architecture to create production-grade foundations for enterprise AI.

Stay tuned as I share more about the architecture, engineering decisions, and progress of this journey.

Looking back, I realise that every stage of my career naturally prepared me for the next one. Systems programming led to distributed systems. Distributed systems led to IoT. IoT evolved into intelligent robotics and large-scale warehouse automation. Warehouse automation eventually led me towards Enterprise AI, where software, data, and intelligent decision-making come together to solve increasingly complex business problems.

Technology continues to evolve rapidly, but my motivation has remained surprisingly consistent since 2005.

I enjoy understanding difficult problems, simplifying complexity, building products and engineering teams that create measurable business value, mentoring engineers, and continuously challenging myself by learning emerging technologies and exploring new domains.

This website is an extension of that journey.

It brings together the projects I've built, architecture ideas I've explored, engineering lessons I've learned, technical articles I've written, and an AI Knowledge Assistant that can answer questions about my experience, projects, and technical work.

Whether you're an engineering leader, recruiter, founder, architect, customer, or fellow engineer, I hope you find something here that's useful, insightful, or perhaps even inspires your own engineering journey.

Welcome, and thank you for visiting.