There are thousands of hackathons happening every year, and they're wildly different from each other. A 48-hour on-site hackathon in Berlin with 500 developers is a completely different experience from a one-day virtual event with 30 people focused on climate solutions. Both are great — but one might be perfect for you and the other might not.

This chapter helps you figure out which events fit your goals, your experience level, and your life.

On-site hackathons happen at a physical venue. You show up, hack alongside other teams, eat together, maybe even sleep there (though you definitely don't have to). The energy is electric — there's something about being in a room full of people building things that's hard to replicate online. Great for networking and for first-timers who want the full experience.

Online hackathons let you participate from anywhere. You'll collaborate with your team over video calls and chat. The schedule is usually more flexible, and you can participate in your pyjamas. Great if you can't travel, want a lower-commitment entry point, or are in a different timezone from the event.

Hybrid hackathons combine both — some people are on-site, some are remote. These can be tricky to run well, but when they work, they offer the best of both worlds.

Open hackathons let you build whatever you want. Maximum creative freedom, but can feel overwhelming if you don't come with an idea.

Themed hackathons focus on a specific area — AI, healthcare, sustainability, fintech, education. If you care about a particular domain, themed events give you structure and connect you with like-minded people.

Corporate hackathons are hosted by companies, often using their APIs or products. They tend to have bigger prizes and more mentorship around specific technologies. Good for learning a company's stack and getting noticed by potential employers.

Community hackathons are run by local groups, universities, or nonprofits. Usually smaller, friendlier, and more beginner-friendly. A fantastic starting point.

One-day hackathons (6–10 hours): Compact, intense, no overnight drama. You'll build something small but complete. Perfect for beginners and people with limited time.

24-hour hackathons: The classic format. Enough time to build something substantial without the marathon of a full weekend. Most people go home to sleep and come back.

48-hour hackathons (full weekend): The full experience. Friday evening to Sunday afternoon. More time to build, iterate, and polish. Can be tiring but rewarding.

Beginner-friendly events explicitly welcome newcomers and usually include workshops, extra mentorship, and simpler challenge tracks. Look for phrases like "no experience required," "first-timers welcome," or "all skill levels."

Advanced/professional events expect participants to have working knowledge of relevant tools. These tend to move faster and assume less hand-holding.

Student hackathons are organised by and for university students. Often free, with lots of energy and socialising. Many accept non-students too — check the rules.

BuilderBase — Browse the discovery page to find upcoming events filtered by theme, format, and location. You can register directly and start connecting with other participants before the event.

Community channels — Local tech meetup groups, Slack communities, Discord servers, and university bulletin boards regularly share hackathon announcements.

Social media — Follow hackathon-related hashtags on LinkedIn and Twitter/X. Many events promote heavily on social platforms.

Word of mouth — Ask friends, colleagues, or classmates. Personal recommendations are often the best way to find well-run events.

Before you register, look for a few signals:

Clear challenge tracks. Good events tell you what problems you'll be solving. Vague events ("innovate the future!") tend to be less well-organised than specific ones ("build tools to improve mental health access for rural communities").

Organiser credibility. Who's behind it? Is it a known community, company, or institution? Check if they've run events before and look for photos or recaps from past editions.

Mentorship and support. Does the event mention mentors, workshops, or tech support? Events that invest in participant support tend to be better experiences, especially for newcomers.

Judging criteria published in advance. If you know how you'll be evaluated, you can prepare better. Events that publish their rubric are usually more thoughtful about the whole experience.

Community before the event. Does the event have a Slack or Discord where participants can connect beforehand? Pre-event community is a strong signal of a well-organised hackathon — and it gives you a head start on team formation.

Prizes that match the effort. Prizes aren't everything, but they signal how seriously the organisers take the event. Look beyond cash — mentorship, incubator access, cloud credits, and meetings with industry leaders can be more valuable than money.

If this is your first event, don't optimise for winning. Optimise for learning and connection. Look for:

You can always level up to bigger, more competitive events later. Your first hackathon should be fun, not stressful.

Key takeaways: