SIH 2024: When 4th Place Taught Us More Than Winning Ever Could
Leading a team of six through the Smart India Hackathon internal rounds in our third year. 4th place, no grand finale — but lessons worth more than any trophy.
September 15, 2024
The Dream Team
Smart India Hackathon. The biggest student hackathon in India. When SIH 2024 internals were announced at our college in third year, I knew we had to go for it.
Six people. Different strengths. One goal — make it to the grand finale.
- Omkar – The calm problem-solver who kept us grounded when things broke
- Atharva – My CODEATHON partner. Fastest coder I know when the pressure is on
- Isha – Turned our rough wireframes into a UI that actually looked professional
- Swapnil – Cloud and deployment. If it needed to go live, Swapnil made it happen
- Sourabh – Research backbone. Every claim we made, Sourabh had verified twice
And me? Keeping the chaos organized and making sure we actually shipped something.
Presenting our solution to the judges — when preparation meets reality.
The Grind
The hackathon doesn't start at the venue. It starts weeks before.
We analyzed past SIH problems, finalized our tech stack, ran team sync sessions, and practiced mock presentations. Atharva and I brainstormed approaches on late-night calls. Isha had design prototypes ready before we picked our problem statement. Omkar researched APIs. Swapnil prepped the deployment pipeline. Sourabh built a research doc with datasets and references.
We weren't just showing up — we were coming prepared.
The grind — laptops on the floor, team huddled together, building and debugging.
The Hackathon
College-level SIH internals are brutal. You're up against friends, seniors, last year's winners, and the professors' favorite batch. Everyone is hungry.
We picked a problem statement at the intersection of tech and real-world impact — working prototype, solid architecture, business viability, and a compelling pitch. All of it.
Things didn't go smooth. Our initial API approach hit rate limits. Omkar suggested caching as a workaround — not perfect, but practical. We pivoted fast. Isha delivered a clean frontend. Swapnil wrestled with deployments until it went live on the third attempt. Sourabh refined the presentation in parallel.
When we stood in front of the judges, the demo worked. Every click did what it was supposed to. Judges asked tough questions — we answered some confidently, some honestly admitting what we hadn't figured out.
Authenticity beats pretense. Every time.
The team discussing strategy before the presentation round.
4th Place — And Why We Didn't Make the Grand Finale
4th place. College-wide. Third year.
Close. So close. But not close enough.
And here's the thing most people don't know about SIH: even if we had placed top 3, we likely wouldn't have made the grand finale. The way SIH works — if more than 500 solutions are submitted for a particular problem statement across all colleges, that problem statement gets removed from the grand finale shortlist.
Our problem statement was popular. Too popular. Hundreds of teams across India picked the same one. When the solution count crosses 500, it doesn't matter how good your execution is — the idea itself gets cut.
We built something that worked. We built something we were proud of. But we picked a crowded problem, and the numbers weren't in our favor.
That stung for about ten minutes. Then someone said, "We shipped a working product as a team. That's more than most people do in college." And they were right.
What We Actually Won
No trophy. No grand finale. But here's what 4th place gave us:
Team Management
Leading 6 people under pressure teaches you when to delegate, when to step in, and that leadership is about making the team smarter together — not being the smartest person in the room.
Choosing Smarter, Not Harder
The 500-solution rule taught us the hardest lesson: picking the right problem is half the battle. You can build the best solution in the country, but if 500 other teams picked the same problem, none of it matters at the national level.
Next time: research which problem statements are less saturated. Work smarter.
Execution Under Pressure
Deadlines are unforgiving. You learn to prioritize what MUST work, cut features without guilt, and ship something real instead of something perfect.
Bonds That Last
You don't really know people until you've debugged together under pressure. The six of us — Omkar, Atharva, Isha, Swapnil, Sourabh, and me — went through the trenches together in third year. That bond doesn't break.
Gratitude
To this team:
- Omkar — the steady hand when things got chaotic
- Atharva — always showing up, no matter what
- Isha — making our product look like a real product
- Swapnil — deployment magic
- Sourabh — the research and documentation backbone
The result was 4th place. The experience was 1st place.
We didn't make the finals. But we learned how hackathons really work, what judges actually look for, and how to pick battles that are winnable.
4th place in third year isn't the end — it's the benchmark to beat.
Watch this space.
Here are some other articles you might find interesting.
Code Apex: How a Casual Call Led to a District-Level Coding Victory
From a spontaneous registration to competing against 240 teams at CODEATHON 2024. Here's how Atharva and I secured 2nd Runner-Up at MGM University's district-level competition.
When Preparation Meets Reality: My Zensar Interview Experience
I spent a month preparing for a hackathon, received an email about 'Java/Python and MySQL Assessment', yet still made assumptions. Here's what happened, the valuable lessons from Rajesh Madhai sir, and why fundamentals and personal responsibility matter most.
