How Hackathon Judging Works
A hackathon ends with dozens of tired teams and a few hours to pick winners. Without set criteria, judges reward the slickest slide deck or the project closest to their own work. A published rubric tells teams what to build toward and gives judges a common scale.
Most hackathons judge in stages:
- Submission: teams submit a project page, a repository link and a short video or description by a hard deadline
- Eligibility check: organizers confirm the work was built during the event and the team followed the rules
- Expo round: judge pairs visit numbered team tables, science fair style, and score short live demos
- Finals: the top teams demo on stage to a finals panel, often in front of the whole event
- Sponsor prizes: sponsors judge their own challenges, such as best use of their API, separately from the main prizes
Hackathon Judging Criteria and Weights
Six criteria cover what judges can see in a short demo. The weights below make a 100-point rubric for a general hackathon; publish them at kickoff.
| Criterion | What judges look for | Points |
|---|---|---|
| Technical complexity | Hard problems solved, sound engineering, and how much of it actually works in the demo | 25 |
| Impact | A real problem for real users, and how much the project would help them | 20 |
| Creativity | An original idea or a fresh use of a familiar tool | 15 |
| Design and UX | A product someone could pick up and use; clear flow and interface | 15 |
| Presentation | A clear demo in the time allowed, and direct answers to questions | 15 |
| Theme fit | Answers the hackathon theme or the chosen challenge track | 10 |
| Total | All criteria | 100 |
| Band | Points | What it means |
|---|---|---|
| Mockup | 1 to 8 | Slides or screens with little or no working code |
| Partial | 9 to 15 | The core works with hard-coded steps or a narrow happy path |
| Working | 16 to 21 | A working build of the main feature, with real data or integrations |
| Impressive | 22 to 25 | Difficult work done well in the time, and stable in a live demo |
Printable Hackathon Scoring Sheet
Judges fill in one sheet per team during or right after the demo. Use the tally sheet to combine each pair's scores before finals.
Judging Rounds: Expo Tables, Then Finals
The expo round works like a science fair: teams stay at their tables, judges move. It lets you see every team in an hour or two instead of a full afternoon of stage demos.
- 1
Calibrate Judges
Brief judges together before demos start. Walk through the rubric and bands, and score one sample project as a group so everyone agrees what a middle score looks like.
- 2
Assign Tables
Split judges into pairs and give each pair a run of table numbers in walking order. Make sure every team is seen by at least two judges, and avoid sending a judge to a team they know.
- 3
Run the Expo Round
Each team gets the same time, often three to five minutes including questions. A volunteer with a timer moves judges on.
- 4
Tally and Pick Finalists
Average each team's scores. If one judge pair scored much higher or lower than the rest, compare their ranks rather than raw totals, or have a floating judge re-score borderline teams.
- 5
Run the Finals
The top five to ten teams demo on stage to a finals panel of three to five judges, with a few minutes of questions each. The panel deliberates while a sponsor talk or the audience vote fills the break.
For pitch-heavy events where teams also present a business case, the pitch competition judging criteria add market, traction and the ask to the rubric.
Demo Rules, Submissions and Tie-Breaks
Write the rules at kickoff and pin them where teams work. These are the ones judges most often have to rule on:
- Team size, often two to five people, and whether solo entries are allowed
- Fresh code: projects start at kickoff; open-source libraries, APIs and templates are allowed when the team names them
- AI tools: whether AI coding assistants are allowed and whether teams must say how they used them
- Submission: a repository link, a short description and a demo video, by a hard deadline, with no commits counted after it
- Demo: a live demo is preferred; a recorded video counts only if the live demo fails, and judges note which they saw
- Ownership: who owns the code, especially at a corporate hackathon; have the wording reviewed, since it is a legal question
- Conduct: a code of conduct and a named contact for reporting problems
Running a Hackathon at a Tech Conference
Many hackathons run inside a tech conference or a developer event, which gives teams an audience, mentors and sponsors already on site. The room needs more planning than most breakout spaces.
- Number team tables in walking order and print the same number on the table tent, the rubric and the tally sheet
- Plan power for every seat, plus spares; the event power calculator helps size it
- Plan Wi-Fi for every laptop and phone at once, with a wired fallback for demos; see event Wi-Fi planning
- Mark a mentor desk, sponsor tables, food, a quiet room and the demo stage
- Put kickoff, workshops, the submission deadline, demos and awards on the run of show template
- For the wider event, the technology conference software page covers the schedule, app and sponsor booths