Blog · Nov 11, 2026
How to Choose a Hackathon: A Seven-Point Checklist
There are far more hackathons than anyone has time for. Picking well matters more than building well, because a great project in the wrong event earns nothing. Here is the checklist I would run before registering. It takes about ten minutes per event, and it will cut your shortlist fast.
1. Odds: how crowded is the prize?
Divide the cash prizes by the number of people signed up. That gives you prize money per entrant, a rough measure of how crowded the pool is. Say an event offers $6,000 and 120 people have registered: that is $50 each. Compare it with other events you are considering, not with an imaginary target.
Two cautions. Sign-up counts include people who never submit, and they keep rising until the deadline. So use the ratio to rank events against each other, and don't read it as your personal chance of winning. Our best odds list does the division for you, and the methodology page explains the limits.
2. Deadline: can you finish in time?
Look at two dates: when registration closes, and when the submission is due. They are often different. Many events let you register late but expect a finished project by a hard cutoff. Count backwards from the submission date and ask how many real hours you have, after work, family and sleep.
If you only have a free weekend, an event that runs for four weeks is not a problem, but a 24-hour sprint that starts on Friday evening might be. The closing soon page shows what can still be entered this week.
3. Eligibility: are you actually allowed to win?
Read the official rules, not the landing page. Check age, student status, country, and sponsor-employee exclusions. An event that is "open to all" on the front page can still bar your country from receiving prizes. If you are not a student, filter those events out early; our guide to hackathons for adults goes through the wording in detail.
4. Cash or credits?
List what the prizes are made of. Cash can be spent on anything. Cloud credits, API credits, hardware and swag are worth something only if you would have bought them anyway. A pool that is half credits is, for your purposes, a smaller pool.
Also check how prizes are paid: lump sum, in installments, in a token, or by gift card? Are taxes and fees your problem? A prize paid in a volatile token that is locked for a year is not the same as a bank transfer next month. If the rules don't say, ask.
5. Judging criteria
Good events publish what judges score: for example, originality, technical difficulty, design, impact, and use of the sponsor's product. Then you can tailor your project to the scorecard (more on that in how to win a hackathon).
Look for:
- Named criteria, ideally with weights.
- Named judges or a description of who judges.
- A date when winners will be announced.
- Past winners you can look at.
If the judging is "decided by the organizers at their discretion" with nothing else, you are betting on someone's mood. That is a risk, and our post on whether a hackathon is legit explains why.
6. IP rules: who owns what you build?
This is the point people skip, and the one that can cost the most. Look for words like "license," "ownership," "assigns," or "rights to use." Typical arrangements:
- You keep ownership and grant the organizer a limited license to display and promote your entry. This is the comfortable version.
- The sponsor gets a broader license to use your project commercially. Think twice if the project could be your business.
- The sponsor takes ownership of what you submit. Avoid, unless the prize is large and the project is throwaway.
Also see what the rules say about pre-existing code. Many events require that you start the project during the hackathon. Entering something you already built can get you disqualified. And if your employer has a claim over side projects, check your contract before you start.
7. Team rules
Check the allowed team size, whether solo entries are welcome, and whether every member needs to be eligible. Look at how prize money is divided: split equally among members, paid to a team lead, or paid to each person? A prize of $3,000 for a team of five is $600 each, before anything else. If you are looking for people to build with, our guide on finding teammates covers adult and remote setups.
A quick scoring sheet
Give each event a pass, maybe or fail on the seven points. Any fail on eligibility, IP or payment terms is a stop. Otherwise, prefer the event with the best combination of odds and a deadline that fits your calendar. Everything else is a tiebreaker.
| Check | What a pass looks like |
|---|---|
| Odds | Prize per entrant beats similar events you are considering |
| Deadline | Enough real hours before submission is due |
| Eligibility | You qualify on age, status, country and employer |
| Prize type | Mostly cash, with clear payment terms |
| Judging | Published criteria and a named process |
| IP | You keep ownership of your work |
| Team | Size and prize split suit how you want to work |
Do the cheap checks first
Order matters. Eligibility and IP take two minutes to read and rule out the most events, so do those before you analyze odds. Then use the search page to filter by online, city, prize and deadline, and save the survivors to your shortlist. If the same two or three events keep surviving, you have your answer.