--- title: The People Behind DebugInit | DebugInit url: https://www.debuginit.com/company/people source: DebugInit (https://www.debuginit.com) --- The people behind DebugInit # Different minds. Different journeys. One thing we're building together. A story about people, possibilities, and the work behind the ecosystem. DebugInit · Bengaluru, India · a global crew across India, Nepal and Australia 01 · Chapter ## It was never supposed to be just one person. Every company has a story about what it wants to build. But behind every product, every idea, every decision, and every experiment, there are people. People with different backgrounds, different ambitions, different ways of thinking, and different definitions of what success looks like. DebugInit is no exception. When I started DebugInit in 2021, I had an idea of building something bigger than individual software projects. Over time, that ambition grew into an ecosystem of products, technology, research, and intelligent systems. But there is something I have come to understand along the way. A founder can initiate a vision, but cannot build an entire ecosystem alone. It takes people who are willing to explore unfamiliar problems, challenge assumptions, take ownership, learn new things, and contribute in their own ways. That is what makes our team important. We are not a group of people who all think alike. We come from different places, bring different experiences, and approach problems differently. And that diversity of thinking is something I want us to preserve. 02 · Chapter ## A team without borders Our team brings together people working across India, Nepal, and Australia. Some work around product and engineering. Others focus on business strategy, research, operations, project coordination, user experience, and content. We are a distributed crew, but our work connects through a common ambition: building technology that is useful, thoughtful, and capable of evolving. We don't believe every contribution needs to look the same. Some people make products work. Some make them easier to use. Some question whether we are solving the right problem. Some find opportunities we haven't considered. Some help the outside world understand what is happening inside. All of these contributions matter. 03 · Chapter ## Meet the people ### Sanjay Shah Founder & Executive ChairmanBengaluru, India I started DebugInit with the ambition of building technology from the ground up. Today, my responsibilities span the ecosystem's long-term direction, governance, innovation, technical architecture, and product foundations. I remain deeply involved in understanding how our systems work and where they should go next. My responsibility is not simply to keep the vision alive. It is to create the foundations, direction, and environment in which other people can contribute to making it real. ### Avi Aryan Chief Executive OfficerIndia Avi brings a business-oriented perspective to DebugInit. His interests span finance, strategy, entrepreneurship, product development, and execution. His role is to help turn ambitious thinking into practical organizational action, maintain focus, and keep the team moving towards meaningful outcomes. A good idea needs more than technical possibility. It needs business judgment and execution. That is an important part of his contribution. ### Ashwin Menon Chief Strategy OfficerBengaluru, India Ashwin brings an entrepreneurial and strategic perspective to the team. His background includes a BBA in Human Resource Management, an MBA in Innovation, Entrepreneurship and Venture Development, and ongoing doctoral research into growth, marketing, and operational alignment in early-stage digital startups. He also has interests and experience across publishing, digital libraries, and FMCG ventures. At DebugInit, his perspective connects business strategy, market opportunities, organizational development, and the practical challenges of building ventures. ### Kajal Budha Kshetri Project ManagerNepal Kajal helps bridge the gap between ideas, product requirements, design, and development. Her work involves defining system features, mapping user workflows, coordinating with the team, and testing designs to identify usability issues and bugs. She brings structure to the details that can otherwise get lost between planning and implementation. Because a product is not ready simply because the code works. It needs to work for the people using it. ### Neeraj Operations & AI ResearchBengaluru, India Neeraj works across operational coordination and AI research. This combination connects two important aspects of our work: understanding emerging technology and making sure the organization can translate ideas into practical progress. His contribution sits at the intersection of exploration and execution. ### Ravi RV User ExperienceBengaluru, India Ravi works around the user experience dimension of our products. Technology can be powerful and still be difficult to use. The challenge is to make complex systems understandable, interactions intuitive, and product experiences meaningful. That is the perspective UX brings to the ecosystem. ### Ankit Business Research & DevelopmentKathmandu, Nepal Ankit explores business opportunities, market trends, research, and growth possibilities. His work focuses on connecting information with decisions. Research is valuable when it helps us understand what is happening, identify opportunities, challenge assumptions, and make better choices. His curiosity and analytical approach contribute to that process. ### Rahul Kumar Mahato Technical Business AnalystBengaluru, India The space between business requirements and technical implementation is where many product challenges begin. Rahul's role as Technical Business Analyst connects those two perspectives. Understanding what needs to be built, why it matters, and how requirements translate into systems is essential to building products that solve actual problems. ### Roshan Frontend DeveloperBengaluru, India Roshan contributes to the frontend development side of our work. The frontend is where technology meets people. Behind every screen, interaction, and interface is a series of engineering decisions that shape how someone experiences a product. His contribution is part of turning product thinking and design into working experiences. ### Sudhir AI ResearchBengaluru, India Sudhir works in AI research. Artificial intelligence is changing rapidly, and understanding its possibilities requires continuous experimentation and learning. Research helps us look beyond current implementations, understand emerging capabilities, and explore where intelligent systems can create meaningful value. ### Golden Whispers Content CreatorAustralia Every technology company needs people who can communicate what it is building. Golden Whispers brings a creative and content-oriented perspective to the crew. From stories and social content to capturing the personality behind the products, the role is about making technology more approachable and giving the community something to connect with. Working from Australia also adds a different perspective to our distributed creative presence. 04 · Chapter ## Different responsibilities. Shared ownership. We have people working across different functions, but we don't want those functions to become isolated departments that never understand each other. Engineering needs to understand business. Business needs to understand technology. Design needs to understand users. Research needs to inform decisions. Operations needs to make execution possible. Communication needs to represent what we actually build. This is how we want to work. Not everyone needs to be an expert in everything. But everyone should understand enough about the bigger picture to see how their contribution connects to it. That is the kind of organization we want to develop. 05 · Chapter ## The reality of building together Let's be honest. Working in a growing technology venture is not always glamorous. There are difficult discussions, changing requirements, unfinished features, unexpected bugs, missed expectations, new priorities, and moments when the original plan needs to change. Sometimes an idea looks excellent on paper and becomes difficult during implementation. Sometimes we spend hours discussing a small detail because that detail affects the entire experience. Sometimes we need to stop building something new and fix what already exists. And sometimes the most valuable contribution is simply asking a question nobody else has thought to ask. We are learning that collaboration is not about agreeing with everything. It is about being able to disagree constructively, communicate clearly, take responsibility, and keep improving. We don't expect perfection from people. We do expect honesty, curiosity, ownership, and respect. 06 · Chapter ## The Brutal Truth About Being a Team A company can have a great vision and still struggle to execute it. A team can have talented people and still experience coordination problems. A product can have excellent engineering and still fail to find its market. We need to acknowledge these realities. At DebugInit, we are still improving how we plan, communicate, distribute responsibilities, document decisions, and measure progress. We have learned that: - Being busy is not the same as being productive. - Attending meetings is not the same as contributing. - Having ideas is not the same as taking ownership. - Completing tasks is not the same as creating meaningful outcomes. - Working together does not mean everyone must think alike. - Motivation cannot replace clear processes. - A good team is built through trust, consistency, and accountability. As leadership, we also have responsibilities. We must communicate expectations clearly, provide the right direction, listen to feedback, and create an environment where people can grow. We cannot expect people to take ownership without giving them the clarity and space to do so. And we cannot expect a company to improve if we are unwilling to question our own ways of working. This is a learning process for all of us. 07 · Chapter ## More than a job title We don't want people to be defined only by their current designation. A project manager can develop product thinking. A developer can become a researcher. A business strategist can understand technology more deeply. A content creator can influence how a product is positioned. An individual contributor can become a future leader. We want people to explore, learn, and discover their strengths. Not every experiment will work, and not every opportunity will become a formal responsibility. But we believe that curiosity and continuous learning should remain part of the culture. 08 · Chapter ## What we want to build together Our ambition is to create more than a collection of applications. We want to build an ecosystem where products, intelligent systems, shared foundations, and people can work together. That ambition requires different kinds of thinkers and builders. We need engineers who care about foundations. Researchers who question assumptions. Designers who understand people. Strategists who understand markets. Operators who make execution possible. Creators who communicate ideas. And individuals who are willing to contribute beyond the boundaries of their current experience. We want DebugInit to become a place where people don't just participate in building products. They understand the thinking behind them. 09 · Chapter ## To everyone building with us To the people currently contributing to DebugInit: Thank you for bringing your time, energy, perspectives, and ideas into this journey. Not every contribution will immediately become visible. Not every late-night discussion will turn into a feature. Not every experiment will become a product. But the learning, effort, and thinking behind those experiences matter. I want us to keep questioning, keep improving, and keep building with purpose. And I want us to remember that the company is not defined by one person, one product, or one moment. It is shaped by the people who contribute to it and the quality of the work we create together. 10 · Chapter ## The story is still being written We are not presenting ourselves as a finished organization. We are a growing crew, building across disciplines, exploring possibilities, learning from mistakes, and working towards a larger vision. There will be new people, new ideas, new products, new challenges, and new chapters. Some people may take on different roles. Some may move on to new opportunities. Others may grow into responsibilities they never imagined when they started. That is part of building something over time. We want to celebrate the journey, not just the destination. Because behind every product is a group of people who decided to give an idea their time and effort. Different minds. Different journeys. One ecosystem. DebugInit · AI-native IoT ecosystem The people are the foundation. Building intelligent systems for a connected world. Founded by Sanjay Shah in 2021. Bengaluru, India · building globally. We are not just building products. We are learning how to build together. The story continues.