Code Battle Season 6 · Registrations open until 10 Nov · Grand Finale 21 Nov at Heriot-Watt Dubai Season 6 · Registrations close 10 Nov Register now →
Code Battle logo

How to Win a Hackathon: 12 Lessons from Five Seasons of Code Battle

Cadet division winners at Code Battle

To win a hackathon, build a small idea that fits the theme, get it working early and pitch it clearly. The winning teams we’ve seen at Code Battle rarely have the flashiest code. They have a finished project and a team that can explain every part of it.

We’ve run Code Battle, the UAE’s free inter-school hackathon, since 2021. Across five seasons that’s more than 1,000 students and 500+ projects. These are the 12 lessons we’d pass on to any team, from a Grade 2 Scratch team to a Grade 12 team writing Python.

What are the best tips for winning a hackathon?

1. Read the judging criteria before the theme

Code Battle judges score five things: code, user interface, creativity, teamwork and presentation. In 2022 and 2023, each counted for 20%. Four of those five aren’t about how clever your code is, so plan for all of them. Our guide to hackathon judging criteria breaks each one down.

2. Fit the theme properly

Judges can tell when a team has squeezed a game it already wanted to make into the theme. Spend the first few minutes asking what the theme is really about, then build something that couldn’t belong to any other theme.

3. Shrink the idea, then shrink it again

Teams that try to build three features usually finish none. Pick the one thing your project must do and make that work. You can always add more if there’s time. There rarely is.

4. Get something running in the first 45 minutes

Coding at Code Battle runs from 10:30 to 12:30. If nothing runs by 11:15, you’re in trouble. An ugly version that works gives you something to improve and something to demo.

5. Give everyone a real job

Teamwork is scored, and judges notice when one person built everything while the others watched. A builder, a designer and a presenter is a good split for a team of three. Everyone should still be able to explain the whole project.

6. Make it easy to use

A judge should be able to use your project without you explaining it. Add a start screen, short instructions and buttons that look like buttons. This is what the user interface score is about, and it’s often the quickest marks to pick up.

7. Add one thing people will remember

A sound effect, a surprise ending, a clever use of the theme. One memorable touch does more for your creativity score than five average features. Add it after the core works, not before.

8. Stop building 15 minutes early

Freeze features at 12:15. Fix bugs, save a working copy and rehearse your pitch. The teams that code until 12:29 often present a broken version and a pitch they’ve never said out loud.

9. Use AI where it helps, and be ready to explain it

At Code Battle, AI is allowed, but students must be able to explain how they used it, and recycled code must be disclosed. Use AI for small, specific jobs and read everything it gives you. Our post on using ChatGPT and AI in a hackathon goes into detail.

10. Start the pitch with the problem

You get 2–3 minutes. Open with who the project is for, show it working, then explain how you built it. Our two-minute pitch template gives you timings for each part.

11. Demo the real thing

A live demo is encouraged at Code Battle, and it’s the most convincing part of any pitch. Show the path through your project that you’ve tested. If something breaks, stay calm, explain what should happen and move on.

12. Answer questions honestly

After the pitch, judges ask questions. “We didn’t have time for that, but here’s how we’d do it” is a strong answer. Guessing or bluffing isn’t, and judges who work in the industry spot it quickly.

Is winning a hackathon a big deal?

It’s a great feeling, and at Code Battle the winners take home trophies, medals and sponsor prizes. Every participant also gets a certificate, so nobody leaves empty-handed.

The margins can be tiny. In 2025, the top three Captain teams (Grades 5–8) scored 88, 86 and 85. In the Cadet division (Grades 1–4), first to third was 71, 70 and 69. One or two points separated the places, which is why small things like a clear start screen or a calm answer to a judge’s question matter so much. You can see every team’s score in the Code Battle 2025 rankings.

But winning isn’t the only measure of a good day. If you built something in two hours and pitched it to a panel of industry judges, you’ve done something most students your age haven’t. A teacher who brought students to our 2022 Sharjah chapter put it well:

Code Battle created a positive and energetic learning experience for our students. They were challenged to think, create, and persevere, while still enjoying the process from start to finish.

— Shafeena Basheer, Teacher, Delhi Private School Ajman

What are the most common hackathon mistakes?

Most of these come from the same root: trying to do too much in too little time.

  • Arguing about the idea for 30 minutes. Give yourselves 15, then commit.
  • Building the hardest part last. Do the core feature first, and decorate later.
  • Designing a beautiful start screen for a game that doesn’t work yet.
  • Not saving a working version. One bad change at 12:25 can wipe out an hour’s work.
  • A pitch that’s all talk. Judges want to see the project, not hear about it.
  • Hiding AI use or reused code. Code Battle’s rules ask you to disclose reused code and explain any AI use, and it usually comes out in the questions anyway.
  • One person doing everything. It costs you on teamwork and leaves the rest of the team unable to answer questions.

How can teachers help a team win?

Run at least one practice round with a past theme, a two-hour timer and a two-minute pitch at the end. Themes we’ve used include “The Great Gadget Adventure” for Cadet, “The Interactive Web Museum” for Captain and “AI for Social Good” for Colonel. Then step back. Teams that make their own decisions in practice make better ones on the day.

Watching other teams is useful too. Another teacher who brought a team to Sharjah in 2022 said:

Participating in Code Battle was a memorable experience for our students. It gave them the chance to challenge themselves, learn from others, and experience the excitement of building something through code.

— Ruairi Tubrid, Teacher, Victoria International School of Sharjah

When you’re ready, enter your team through the school registration form. Code Battle is free for schools and students.

Frequently asked questions

How do you win a hackathon?

Pick a small idea that fits the theme, get a working version early and stop building in time to rehearse your pitch. Then show a live demo and answer the judges’ questions honestly.

What do hackathon judges look for?

At Code Battle, judges score code, user interface, creativity, teamwork and presentation. In 2022 and 2023 each was worth 20% of the total.

Do you need to be the best coder to win a hackathon?

No. Code is one of five criteria at Code Battle, so a team with clear design, a strong idea and a good pitch can beat a team with better code.

What do Code Battle winners get?

Winning teams receive trophies, medals and sponsor prizes. Every participant gets a certificate.

How many teams take part in Code Battle?

In 2025, Code Battle had 205 students in 79 teams from 53 schools across four emirates.

About Code Battle

Code Battle is the UAE's free inter-school student hackathon, created and run by iCodejr in Dubai since 2021. More than 1,000 students from over 100 schools have taken part across five seasons. Register your school for the next season.