11 Competitions, 11 Wins: The System Behind the Streak

I've entered 11 competitions — hackathons, business championships, pitch competitions. I've won all 11. That includes Brand Wars at IIT Mandi (a national business analysis + marketing championship), Innovation Deck at LPU (business strategy), and the BHU hackathon.

The streak isn't about being the strongest coder in the room. It's that most teams lose the same three ways, and you can simply... not.

Most teams lose before they start

They pick an idea they love instead of an idea that fits the judging rubric. Read what's actually being scored. A hackathon scoring "impact + feasibility + demo" does not want your technically-fascinating infrastructure project with no demo. Brand Wars scored analysis and marketing — so I competed on analysis and marketing, not on code that nobody asked for.

The rubric is the spec. Engineers who would never ignore a spec ignore rubrics constantly.

The demo is the product

Judges experience your project for three minutes. Whatever isn't in those three minutes doesn't exist.

So build backwards from the demo: script the exact walkthrough first, then build only what the walkthrough needs, then spend the saved time making it bulletproof. A modest idea demonstrated flawlessly beats an ambitious idea that crashes on stage. Every single time.

Win the question round

Presentations are rehearsed; Q&A is where judges actually decide. The trick is boring: list the ten hardest questions you could be asked, and prepare honest answers before you present. Most teams improvise their weakest moment. Make yours the strongest — judges remember the team that had already thought about the flaw they spotted.

Range is a cheat code

The reason the same system wins hackathons and business competitions: the skills are the same three — understand what's being judged, build the narrative, execute the details. Code is just one possible payload. Being able to switch payloads (tech, strategy, marketing) means every competition is winnable with the same engine.

The streak will break someday. The system won't — it's the same one I use to ship: read the spec, build backwards from the demo, prepare for the hard questions.