As someone who has participated in multiple hackathons and won a national-level hackathon, I've...
As someone who has participated in multiple hackathons and won a national-level hackathon, I've noticed that many teams focus heavily on coding but underestimate the importance of project understanding, architecture design, and judge Q&A preparation.
Most hackathon teams spend 90% of their time building and only 10% preparing for judging.
That's backwards.
A great idea can lose because the team cannot explain:
Why the problem matters
How to Win a Hackathon: Notes From the Judging Table - The JetBrains Blog
Building an AI Interview Coach for the BuildSmall Hackathon 2026
PitchFight AI: Practice the Pitch Before the Real Room
ET AI Hackathon 2.0 enters phase 2, challenging builders to turn ideas into AI-powered solutions
At the JetBrains x Codex Hackathon, I spent two days watching teams build and then pitch their projects. The thing that decided…
My hackathon journey didn't start with winning. It started with losing. My first hackathon was...
Over the last few days, I had the opportunity to review a large number of submissions across...
There’s a specific moment that happens at every single hackathon. It’s usually around 2 or 3 a.m.,...
The day after submitting to the hackathon I finally had a moment to look back at the whole system. Turned out something…
After months of planning, countless emails, sponsor outreach, community workshops, and late nights,...
