Insights from judges at the JetBrains x Codex Hackathon on what separates winning pitches from forgettable ones. Key advice: always lead with the problem before showing the tech, scope down to one feature done well rather than many done poorly, make the demo the centerpiece of the pitch (working within 90 seconds), pre-fill forms and mock slow API calls to avoid stalls, rehearse the presentation out loud and time it, and let genuine enthusiasm show. The consensus from multiple judges is that a simpler project with a clear, confident demo beats a complex project with a confusing one.
Table of contents
Start with the problemDo the homework before you write a line of codeScope down to one thingMake the demo the whole pitchRehearse like you’ve already wonRelax and have fun388 Impressions