Rakesh Nair

I’m a technology and engineering leader with 17+ years of experience spanning engineering, architecture, information security, product development and organisational leadership. My career has ranged from building and operating high-scale consumer platforms to leading engineering at startups and growing technology organisations.

I spent more than 12 years at BookMyShow, where I worked across engineering and security as the platform grew substantially in scale. My work included platform modernisation, architecture, performance and reliability, security and PCI DSS, as well as systems operating at tens of thousands of requests per minute with significantly higher peak traffic.

Since then, I’ve held senior technology leadership roles across consumer technology, fintech, music technology and mobility. At SHEROES and Mahila Money, I led multidisciplinary engineering teams, modernised platforms and engineering processes, strengthened security for a regulated financial product, and reduced AWS infrastructure costs by roughly 60% without sacrificing functionality or scale. I also helped deliver a Google WomenWill initiative serving 100,000+ women within approximately six weeks.

As CTO at GSharp, I worked on music-technology products including a licensing marketplace, real-time music customisation and an AI-assisted brand recommendation system. More recently, as Founding CTO at Quicoo, I led the engineering organisation building a rideshare and courier platform from the ground up, covering mobile, backend, web, cloud infrastructure, architecture, security and engineering delivery through production launch.

I’m particularly interested in CTO, Head of Engineering, VP Engineering and senior engineering leadership roles where technology is central to the business. I enjoy problems involving scalable architecture, platform engineering, developer experience, security, reliability and engineering effectiveness. I’m equally comfortable discussing architecture with engineers, product and commercial trade-offs with leadership, and getting close to the technology when that is the fastest way to solve a problem.

My approach to engineering is pragmatic: build for the problems we have and the scale we can reasonably anticipate, rather than for hypothetical complexity. I care about high ownership, clear communication, strong technical judgment and creating teams where engineers understand not just what they are building, but why.