Pitching · Building
Where I test ideas in front of judges and learn what it takes to turn them into something that works. Two podium finishes and one 24-hour build so far, with more to come.
Idea pitching
Pitching taught me to take an idea, shape it into a structured solution, validate the opportunity and explain it to judges, mentors and industry professionals.
I have always liked solving problems and building products. Competitions are where I find out whether my thinking holds up.
Idea pitching gave me a place to test that thinking, validate ideas and learn to communicate a solution in front of judges and experienced professionals. For me it was never only about winning. It was about learning to think like a founder and a product builder.
HMV College
2nd positionAward and certification
Secured second position and received formal recognition, an award and certification, for the quality of the idea and the delivery of the pitch.
KMV College (Kanya Maha Vidyalaya)
2nd positionAward and certification
Presented the idea to a panel of judges and finished second, earning an award and certification at the event.
Hackathon · 2025
My first hackathon. A team of three turned an idea into a working solution under a hard time limit, at CT Group of Institutions, Shahpur.
ByteVerse 2025 was a student hackathon built around innovation, rapid problem solving and technology-driven solutions. It brought together students from different backgrounds to collaborate, build and present within a limited timeframe.
I presented our team and the logic and design behind the product. The three of us were put together with one goal: execute and deliver.
I went in because I was exploring product management and wanted practical experience beyond courses and theory. A hackathon has no safety net and no extra time, which makes it a fast way to learn how product decisions actually get made.
Product Manager
Developer
Designer / Developer
Understanding the problem space and identifying real user needs before building.
Deciding what goes into the MVP and what stays out. Ruthless scoping under pressure.
Giving the team structure and direction so they could move fast without confusion.
Keeping the developer and designer aligned and unblocked throughout the build.
Communicating the idea, the solution and the product rationale clearly to the judges.
A 24-hour clock forces decisions fast. We had limited time, priorities that shifted mid-build and real technical constraints, so the plan kept changing.
At one point the original scope had to be cut hard. Features that felt essential early on became non-essential as the deadline got closer. It taught us to ship a working core before worrying about anything else.
The hardest part wasn't technical. It was staying sharp, deciding clearly and keeping momentum when things didn't go to plan.
Judges reward a real, painful, underserved problem. Technology is the vehicle and the problem is the destination.
People connect with stories, not slides. A well-told founder story stays with the room after the pitch ends.
Great ideas fail when they are poorly communicated. Clear communication inside the team also speeds up delivery.
Public speaking gets better with practice. Each competition made it easier to express and defend my ideas.
Build only what matters most and scope relentlessly. The best MVP is the one that ships.
Ideas are worth nothing without execution. Plans change, and teams that adapt fast do better than rigid ones.
Collaboration in prep sessions improved both the idea and the delivery, and shared context made the team faster.
Building products is not only about technology. It is about problems, users, assumptions, communication and execution.
Defending an idea in front of a judging panel sharpens your thinking in a way classroom assignments don't. Winning second place twice was validating, but the process of preparing, iterating, presenting and taking feedback mattered more. Every pitch taught me something about how people evaluate ideas and what it takes to earn trust.
ByteVerse showed me how a product idea moves from discussion to execution in a very short time. It wasn't clean or perfectly planned. It was messy, fast and real, and I came out knowing what it feels like to own a product problem rather than just study it.
Together they strengthened my interest in product management, startups and innovation-driven problem solving, and showed me where I like to work: at the intersection of business, technology and problem solving.