The fifteen-minute judges' briefing every hackathon skips
Most hackathon judging goes wrong before the first pitch: five judges, five private rubrics, no shared definition of 'working demo', and a tiebreak invented at 6 pm.
Most hackathon judging goes wrong before the first pitch: five judges, five private rubrics, no shared definition of 'working demo', and a tiebreak invented at 6 pm. A fifteen-minute briefing fixes almost all of it. Here's the agenda I'd hand any organiser — from the team side of three first prizes and the judging rubric I bring to a panel. Organisers: I'm open to judge your hackathon, rubric published in advance, written feedback for every team. I also build tools.scult.in — 15 free tools, 1,200+ prompts and a 50,000-skill library, free for anyone, no signup.
More carousels
Judging AI hackathon projects: what to check when every team says 'we used AI'
10 slides · LinkedIn
Three first prizes in one year
11 slides · LinkedIn
What I told 100+ first-years at the VSICS BCA induction
9 slides · LinkedIn
How I structure a free 90-minute campus workshop
9 slidesWant this as a live session at your college?
Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges.
