Common SIH Mistakes That Get Teams Eliminated (And How to Avoid Them)

Why 90% of SIH Teams Fail

Out of 50,000+ teams that register for SIH, only ~300 make it to the grand finale. Most are eliminated not because of bad coding, but because of avoidable mistakes. Here’s what to NOT do.

Mistake #1: Not Reading the Problem Statement Properly

The #1 killer. Teams read the title, assume they know what’s needed, and build something completely different. Always read the FULL description, expected outcome, and organization background.

Fix: Spend 2 hours just understanding the problem. Rephrase it in your own words. Ask: “If I give this to the organization, will they actually use it?”

Mistake #2: Building Too Much

Teams try to build a complete SaaS product with 20 features. In 36 hours, you can’t. You end up with nothing working properly.

Fix: Build ONE core feature that works perfectly. Then add features if time permits. A working demo of one feature beats a broken demo of ten.

Mistake #3: No Live Demo

“We’ll show you our architecture diagram” or “here’s a video we recorded” – instant red flag for judges. If it’s not live, they assume it doesn’t work.

Fix: Deploy early. Have a live URL by hour 20. Test it 10 times before the presentation. Keep a recorded backup video ONLY for catastrophic failures.

Mistake #4: Wrong Team Composition

6 backend developers. Or 6 friends who’ve never coded together. Or one person doing everything while 5 sit idle.

Fix: Clear roles from day 1. Frontend, backend, AI/ML, design/presenter, domain expert, project manager. Everyone should have clear tasks.

Mistake #5: Ignoring the Presentation

Spending 35 hours coding and 1 hour on the PPT. The presentation is 50% of your score.

Fix: Start your PPT by hour 24. Practice at least 3 times. Time yourself. Get someone outside the team to watch and give feedback.

Mistake #6: Using Technology Nobody Can Explain

“We used a transformer-based attention mechanism with multi-head self-attention” – and nobody on the team can explain what that means when judges ask.

Fix: Only use tech your team understands. If you use AI, everyone should be able to explain at a high level what it does and why.

Mistake #7: Copy-Pasting Last Year’s Winners

Judges have seen every previous SIH project. They recognize copies instantly.

Fix: Be inspired by past winners, but add your own twist. What’s new in 2026 that wasn’t available last year? (Answer: AI agents, better LLMs, new APIs)

Mistake #8: No User Research

Building for farmers without talking to a single farmer. Building for hospitals without understanding hospital workflows.

Fix: Talk to at least 2-3 actual users before building. Even a 10-minute phone call reveals insights that change your entire approach.

Mistake #9: Hardcoded Everything

Demo works only with pre-loaded data. Judge asks “try with this input” and it crashes.

Fix: Make your demo work with ANY reasonable input. Test with edge cases. Have proper error messages instead of crashes.

Mistake #10: Giving Up in the Internal Round

“We didn’t get selected last time so we won’t try again.” Many winning teams failed in their first internal round.

Fix: Get feedback from your SPOC on why you weren’t selected. Fix those specific issues. Try again with a stronger team and better preparation.

Practice at other hackathons before SIH

Scroll to Top