From first commit
to final pitch
Practical tips and curated links for every stage—first timer, team finder, weekend survivor, and power user.
Getting started
A hackathon is a build sprint with a demo at the end—not a coding exam. Show up curious; leave with a story.
- Pick for fit, not prestige: virtual vs in-person, theme, team size, and whether you can finish the weekend without burning out.
- Before you register, check eligibility, deadline, Discord invite, and whether you can join solo or need a team.
- Done for a first timer means a working demo someone can understand in two minutes—not perfect code.
- Read the rules once. Note prize tracks, hardware limits, and what counts as a submission.
Finding your people
Solo is fine. A balanced team is often better. The goal is people who finish together—not a stacked résumé.
- Open with a 30-second pitch: what you build, what you need, and what energy you bring.
- Hunt teammates in the event Discord, campus clubs, and mixers—not only LinkedIn cold DMs.
- Aim for complementary roles: builder, designer, storyteller, and someone who knows the domain.
- Joining an existing team? Ask what is missing, ship a small contribution early, and own a clear slice.
Your first weekend
Treat the clock as a design constraint. Ideate fast, cut scope early, and protect time for the pitch.
- Prep the night before: accounts, repo, stack, chargers, and a sleep plan you will actually follow.
- Mental model: ideate → MVP → polish → pitch. If polish eats the demo, cut features—not the story.
- Demo structure: problem → solution → live proof → ask. Rehearse once out loud.
- Ask mentors early when stuck. Judges reward impact, originality, execution, and clarity—not all-nighter lore.
Leveling up
After a few events, stop treating every weekend the same. Choose on purpose and reuse what works.
- Pick events for sponsors, stack, prize tracks, and people—not only total prize pool.
- Build a personal kit: boilerplate, design tokens, pitch template, and a README you can fork.
- Chase a sponsor challenge only if it still serves a product you believe in.
- Ship the repo publicly within 48 hours. Follow up with mentors and teammates while the weekend is warm.
Advanced play
The next level is not more caffeine. It is better selection, sharper demos, and giving back.
- Novelty without a user is a trap. Winning patterns usually solve a sharp problem with a crisp demo.
- Plan recovery between events. Skipping a weekend is a skill—burnout kills seasons.
- Mentor, judge, or organize once you know the rhythm. Teaching forces clearer instincts.
- Build in public and recruit for future weekends before the Discord goes quiet.
Tools & templates
Steal these for any weekend—first hackathon or fiftieth.
Two minutes, four beats.
- ·Hook: who hurts and why now
- ·Solution: what you built in one sentence
- ·Proof: live demo or tight recording
- ·Ask: prize track, users, or next step
What judges and teammates open first.
- ·Problem + one-line solution
- ·Demo GIF or screenshots
- ·Stack + how to run locally
- ·What you would ship next
Before you walk on stage.
- ·Cold start works offline or on hotspot
- ·Backup screen recording ready
- ·One person owns the click-path
- ·Timer practiced under the real limit
Ready to pick one?
Browse the globe or flip the deck—then show up with a plan.