Guides · Nov 17, 2026
How Hackathons Are Judged: Criteria, Rounds and What Judges See
Hackathon judging can look like a black box. You submit, you wait, and a list of winners appears. But most of what decides the result is written down before you write a line of code, in the official rules. Read them closely and judging stops being a mystery. It becomes a scorecard you can plan against.
Start with the published criteria
Most hackathons publish judging criteria, usually in the official rules and often on the main event page too. Common ones include:
- Technical execution or implementation: does it work, and is the technical approach sound?
- Design or user experience: is it clear and pleasant to use?
- Impact or usefulness: does it solve a real problem for real people?
- Originality or innovation: is it a fresh idea or a fresh take?
- Use of required tools: does it make real use of the sponsor’s product?
- Presentation: is the video and write-up clear?
The exact list varies. The AI Summit New York’s hackathon page, for example, says its judging covers technology, efficiency, practicality, scalability and impact. Some rules give each criterion a weight. When they do, treat the weights as a budget for your time.
Write the criteria at the top of your project notes before you choose an idea. Then, for each one, write a sentence about how your project will score on it. If you can’t, change the idea or the scope.
The rounds most hackathons use
Large events often judge in stages. The details are in the rules, but a common pattern looks like this:
- Eligibility screening. Did the project meet the basic requirements? Was it built in the allowed window, does it use the required tools, does it fit the theme, and is the submission complete with a video, description and any required links? A project can be excluded here without anyone weighing its merits.
- Scoring round. Judges score eligible projects against the criteria. With many submissions, each judge may see only a share of them.
- Finals. The top projects may get a closer look, a live demo or a pitch, depending on the event.
- Verification. Before prizes are paid, organizers usually confirm winners are eligible and may ask for paperwork.
Stage one is where good projects most often fall out, for avoidable reasons: a missing video, a private repository, a broken demo link or a missing required tool. Our submission-day checklist covers these.
What judges actually see
Picture a judge with a long list of projects and a deadline of their own. They will likely open your submission page, start your video, skim your description and, if they have time and something caught their eye, click your demo link. They might look at your code. They probably won’t install anything.
That means:
- Your video carries the most weight. Show the working product early. Our demo video guide has a script structure you can copy.
- The first lines of your write-up matter most. Lead with the problem, the user and what your project does, in plain words. Save the architecture for further down.
- Your demo must be one click. If judges can try it, give them a live link that works without signing up, or give test credentials right there in the submission.
- Your repo should explain itself. A short README with what it is, how to run it, and which parts were built during the event.
Scoring well on each criterion
Technical execution
A smaller feature set that works every time scores better than a big one that breaks on camera. Show one hard thing done well, and say briefly in the write-up why it was hard.
Design and user experience
Judges notice clear labels, sensible empty states and the absence of confusion. Ask someone unfamiliar with the project to use it while you stay quiet. Fix wherever they hesitate.
Impact
Name a specific user and a specific job. “Small landlords who track repairs on paper” is easier to believe in than “everyone who owns property”. If you have any real evidence of need, such as a conversation with a potential user, mention it honestly.
Originality
If your idea is common, your angle doesn’t have to be. A familiar problem solved for an overlooked group, or with a sponsor tool in an unexpected way, can read as original.
Use of the sponsor’s tools
Make the required product central to the project, not a bolt-on. Show it in the video, and say in one sentence what it does in your build.
Contests judged without a panel
Not every hackathon uses judges. Some use a public vote, some combine a vote with a panel, and some rank entries by measurable results. The Ship or Die $100K Hackathon’s official page says the three businesses with the highest profit after 30 days win, with profit verified through TrustMRR and a manual review. In formats like that, distribution and sales matter as much as the build, so plan your time very differently.
Public-vote prizes reward reach. If one is offered, decide early whether you want to campaign for it, and check the rules on how you are allowed to promote.
Fairness and how to read a result
Judging is done by people, and people disagree. Two good projects can be scored differently by two good judges. If you don’t place, it doesn’t mean the work was weak. Ask whether the event offers feedback, read the winners’ write-ups, and compare them with the published criteria. That comparison is the most useful lesson a hackathon gives you.
If a hackathon publishes no criteria, names no judges and has never announced past winners, take that as a warning. Our legitimacy checklist explains what to look for.
Put it into practice
Pick your next event from the full search or the top 50 by prize money, open its rules, and copy the criteria into your notes before anything else. Then scope the project so you can score on every line. Once it’s live, add it to the entry wall so sponsors and other builders can find it.
FAQ
How are hackathons judged?
Most hackathons publish judging criteria in their official rules, such as technical execution, design, impact, originality and use of the sponsor's tools. Judges review each submission against those criteria, often in a screening round followed by a final round, and the highest-scoring projects win.
What do hackathon judges look for most?
It depends on the event, which is why the published criteria matter. In general, judges respond to a clear problem, a demo that works, a project that fits the theme and required tools, and a submission that is easy to understand quickly.
Do hackathon judges look at the code?
Sometimes. Some events ask for a public repository and may check it to confirm the project was built during the event or uses the required tools. Many judges, though, form their view mainly from the video, the write-up and a short try of the demo.
How long do judges spend on each project?
It varies widely and is rarely published. With many submissions and limited judging time, it is safest to assume a judge may only watch your video and skim your write-up, so put the most important points first.
Can a hackathon be judged on something other than a panel?
Yes. Some contests use public votes, measured results or a mix. For example, a profit-based hackathon may rank entries by verified profit rather than by a judging panel. The official rules always explain the method.