How to win a hackathon: 25 tips and a winning pitch structure

Updated 11 Oct 2026

Winning teams are rarely the ones with the most code. They pick a real problem, finish one convincing flow, and explain it clearly. Here is what to do before, during and after a hackathon, plus a pitch structure judges like.

Before the hackathon

1. Build a balanced team. Aim for a builder for the front end, one for the back end or model, a designer, and someone who owns research and the pitch. Most hackathons allow teams of 2 to 4.
2. Read the rules and judging criteria twice. Note what you must submit, the deadline time zone and what is allowed (pre-built code, AI tools, APIs).
3. Study the problem statements early. Pick two candidates and spend an hour on each: who has the problem, and what data or APIs exist?
4. Talk to one real user. A two-line quote from a user makes your pitch far more convincing.
5. Set up before the clock starts. A shared repository, a deploy target, API keys, and a group chat. Agree on the stack: use what you know.

During the hackathon

1. Write your one-sentence pitch first: “For [user], who [problem], we built [solution] that [result].” Everything you build must serve it.
2. Scope to one flow. List features, then keep only what the demo needs. A finished small product beats an unfinished big one.
3. Split work by layers (UI, API, model, data) so people don’t block each other, and merge often.
4. Deploy in the first quarter of the time. A live link that works is your safety net.
5. Use real data, even a small sample. Fake data makes judges doubt the product.
6. Check in every few hours: what is done, what is blocked, what we cut.
7. Sleep in shifts at 24- to 36-hour events. Tired teams make demo-day mistakes.
8. Freeze features with 20% of the time left. From here on, fix bugs and prepare the pitch.

Winning PPT structure (10 slides)

Keep slides visual, with one idea per slide and no paragraphs. Practise the pitch out loud and finish within the time limit.

Demo video tips

• Keep it to 2 or 3 minutes, unless the rules say otherwise.
• Open with the problem in 15 seconds, then show the product working.
• Record the real product, not slides, and narrate what the user is doing.
• Use a clean browser profile, zoom in on small text, and cut dead time.
• Upload it unlisted on YouTube or Google Drive and check the link in a private window.

After you submit

1. Write a good README: what it does, how to run it, screenshots and the team.
2. Be ready for a live demo: keep a backup video in case the Wi-Fi fails.
3. Answer judges’ questions honestly, including what doesn’t work yet.
4. Share your project on LinkedIn with the team and the hackathon tagged.
5. Win or not, connect with mentors, judges and other teams. That network outlasts the prize.

Mistakes that cost teams the prize

• Building too many features and finishing none of them.
• No live link: “it works on my laptop” is hard for judges to score.
• A deck full of text, or a pitch that runs over time.
• Ignoring the judging criteria or the problem statement.
• Missing the submission deadline by minutes. Submit early, then update.

Tip: New to hackathons? Read what is a hackathon, then pick from beginner-friendly hackathons.

Browse upcoming hackathons