About Me

Namaste 🙏, I am Ajey

I'm a software engineer who believes technology should serve people, not the other way around.

Born in India, I've had the privilege of living across continents—from Bangalore to London, Chicago to Jakarta, and now Singapore. My journey began in commerce and arts before finding my calling in software engineering. Along the way, I've worn many hats: graphics designer, computer salesman, printing press operator, and even helped run my brother's mobile phone business.

What I've learned is this: every detour taught me something valuable about people, business, and building things that matter. I've spent the last two decades writing software, building teams, and helping organizations grow—but at heart, I'm still that curious person who loves understanding how things work and why people do what they do.

This page is my attempt to give you a user manual for working with me. Think of it as documentation—because everyone deserves to know what they're getting into. 😊

What I Do

I'm a software engineer at heart, but my work extends far beyond code. I build teams, mentor leaders, and help organizations navigate the complexities of scaling technology and culture together.

Currently, I work as an Operating Partner - Technology at Sequoia Capital, where I collaborate with CTOs and CPOs across our portfolio companies. My role is part strategic advisor, part engineering consultant, and part storyteller—sharing lessons learned from two decades of building, breaking, and rebuilding systems and teams.

Before Sequoia, I served as Group CTO at Gojek, where I helped scale a startup from a few engineers to over 2,000 people across multiple countries. It was simultaneously the most challenging and rewarding experience of my career—watching something grow from serving thousands to serving millions of people daily.

My approach is pragmatic: I prefer being the Swiss Army knife in tactical situations and an empowerment advocate in strategic ones. I've learned that the best solutions often come from the people closest to the problems, not from the corner offices.

My Philosophy

"I carry a small collection of successes and a large library of failures. The failures teach me more, and I'm happy to share them so others can avoid the same mistakes."

I believe in intellectual honesty above all else. My perspectives are shaped by my experiences, which means they're inherently biased and potentially incomplete. I welcome being corrected—it's how I learn and grow.

Three principles guide my work:

• People First: Technology serves people, not shareholders' quarterly reports. The best engineering decisions consider human impact.
• Embrace "I Don't Know": These three words have opened more doors for learning than any certification or degree ever could.
• Simple Wins: Complexity is often just poorly understood simplicity. The most elegant solutions are usually the most straightforward ones.

I'm fundamentally optimistic about people and technology's potential to make life better. But I'm also realistic about the hard work required to get there.

How to Work with Me

I'm a converted extrovert, which means I process information through conversation but also need time to think. I prefer direct communication—tell me what you think, disagree when you disagree, and don't worry about being diplomatic. I can separate professional discussions from personal relationships.

What works best with me:

• Come with problems and proposed solutions (I love options to choose from)
• Share your opinion before asking for mine
• Be patient with my learning process—I ask a lot of questions
• Don't take my strong opinions personally—they're held lightly and change with new evidence

I communicate however you're comfortable—many words or few, formal or casual, in person or digital. I'll adapt to what works for you.

What Drives Me

I'm energized by complex problems that sit at the intersection of technology, people, and business. Whether it's scaling engineering teams, designing systems architecture, or helping organizations evolve with their products—I love challenges that don't have obvious solutions.

My core beliefs about building things:

• Transparency over diplomacy: Clear communication prevents more problems than it creates
• KISS principle: Simple solutions scale better and break less often—complexity is often just poorly understood simplicity
• Solutions over features: I prefer working with people who solve problems rather than just ship code
• Action over analysis: Doers who volunteer for unfamiliar challenges make the best leaders

I believe organizations should evolve with their products. The team structure that works for a startup won't work for a scale-up, and what works at scale might kill innovation. The art is knowing when and how to change.

At the end of the day, I'm just someone who enjoys learning, building things that matter, and working with people who care about their craft. The technology industry has given me incredible opportunities—I try to pay it forward however I can.