How to Join a Hackathon: Signing Up, Finding a Team and Getting Ready

how to join a hackathon

The short answer on how to join a hackathon: pick an event that fits your level, join it on the platform that hosts it, sort out a team or a plan for finding one, and set up your tools before the start.

This guide is an independent explainer, not a sign-up page. It covers the general process, and readers wanting the pandemic-era background can start with the covid-19 hackathon hub.

Choosing a hackathon that fits you

Hackathons come in many formats, and the first one a person attends tends to matter more than later ones. Major League Hacking (MLH) says the two big variables are format and focus. Format means in person or online. In-person events put a room full of people and mentors nearby, while online events can be joined from anywhere but ask for more self-direction. MLH’s own view is that neither is better; they are simply different experiences.

Focus is the other variable. Some events run a specific theme or a sponsor track built around one platform, and others are wide open. MLH notes that a first event usually goes more smoothly when the theme is broad, because a narrow track adds a constraint before a newcomer has learned how the weekend flows.

Types of event are also worth knowing. MLH’s explainer lists the most common distinctions: in-person, online or hybrid; software or hardware; themed or open; and student or professional. Collegiate events are run by and for students, while corporate events happen inside companies or at industry gatherings. Checking which type an event is tells a newcomer quickly whether they are eligible and what to expect.

Length varies too. MLH describes the classic format as a fixed window, usually 24 to 48 hours, in which teams go from a blank page to a working prototype. Devpost, which hosts many online events, adds that hackathons can run anywhere from a single day to several weeks online. Anyone with a busy schedule can therefore choose a weekend sprint or a longer, slower event.

It also helps to read the event page for the fine print before committing. Age limits, student-only rules, regional restrictions and the rules on using existing code or AI tools all differ between events, and the organiser’s page is the authority on them.

Signing up on the hosting platform

For online and many in-person events, the sign-up happens on a platform such as Devpost. The process is simple, but it has one step that trips people up. Devpost’s help centre states that signing up for a Devpost account does not register you for any hackathons. A person must also open the hackathon’s own page and press the “Join hackathon” button while the submission period is open.

Devpost’s participant FAQ gives the same sequence for a first event: create a free account, find a hackathon at the platform’s hackathons listing, and then go to its page and click “Join Hackathon”. The same FAQ says participating in a hackathon as a participant is free on Devpost, though individual events can set their own rules, so the event page remains the place to confirm costs.

Changing your mind is allowed. Devpost explains that a participant can unregister at any time up until they begin a draft submission, using a link in the sidebar of the hackathon page.

how to join a hackathon laptops together
Two people typing on laptops side by side.

Not every event uses Devpost. Some student-run events collect sign-ups through their own sites or other tools, and MLH’s season calendar lists events run by many different organisers. The steps are usually similar: a profile, a form, and a confirmation. Always keep the confirmation message, and read the code of conduct and eligibility rules the organiser links to.

Do you need a team?

Usually not. Devpost’s FAQ answers the question directly: most hackathons on Devpost don’t require a team, so solo entry is welcome, although a hackathon’s rules may occasionally require a specific team size or set a maximum. MLH takes the same line, saying that going solo is completely legitimate, especially for a first event.

When teams do form, the typical size is small. MLH says participants work solo or form teams, usually up to four people, and that many events run activities to help people find teammates. It also stresses that no global rule sets team size, so the event rules decide.

The teammate-finding tools are built into the platforms. On Devpost, a participant can tick the “looking for teammates” option on the hackathon’s Participants page, add a short introduction, and send a team-up request to someone promising. Devpost for Teams, the company-facing product, has a similar flow in which a participant can filter projects that are open for team building and click the Join project button. MLH adds that most of its hackathons run team-formation sessions, an active Discord and in-person mixers where solo builders find each other.

What makes a good mix? MLH argues that a good team is not built on coding skill alone. Often it combines someone who builds the software, someone who thinks about design and how the project feels to use, and someone who can tell the story at the end. Devpost agrees that all kinds of skills are useful, listing design, project management and video editing alongside development, and that nontechnical builders such as designers and product managers join events too.

Getting ready before the clock starts

Preparation matters less than most newcomers fear, but a little of it goes a long way. MLH calls getting your environment working before arrival possibly the most consequential thing in its guide, because the classic way a beginner loses momentum is spending the first hours installing tools instead of building.

The advice in that guide boils down to three setup steps done at home, on a quiet afternoon:

  • Set up a GitHub account and make sure you can push code to it, treating it as version control first and a community second.
  • Decide where the project will be deployed and create that account ahead of time, so putting it online is not a mystery at the end.
  • Choose any coding assistant you plan to rely on, install it, and try it on a throwaway project.

Ideas deserve the same restraint. MLH warns that arriving with a fully specified product can backfire, because scope creep starts before the event does. Its suggestion is to come with a few loose directions and narrow them in the first hour at the event. When the event has a theme, a short brainstorm beforehand about what problem it could solve and what would be fun to demo is enough.

Logistics are the dull part that people forget. For an in-person event, MLH lists a laptop, a charger, any hardware the project needs, a photo ID and a water bottle. For an online event, it recommends setting up a workspace, turning off notifications and blocking the time on a calendar. Plan sleep and food too: MLH observes that the team pushing through the night on vending-machine snacks is rarely the one demoing something coherent the next morning.

What the weekend looks like

Knowing the shape of the event removes much of the anxiety. MLH describes a consistent pattern: an opening ceremony where organisers cover the schedule, rules, theme and any sponsor challenges; team formation; a long building stretch with mentors, workshops and food; a submission step; judging and demos; and a closing ceremony where winners are announced.

The submission usually goes to a platform. MLH says teams submit their project to a platform like Devpost or Devfolio, usually with a short demo video and a write-up. Judges then score projects on things like creativity, technical execution and how well the idea is realized.

Newcomers often worry that they are behind everyone else. MLH rejects that: it says first-timers are not behind anyone, and that at most events they are the majority. Its preparation guide adds that hackathons are where people get good, not a test passed after already being good.

When the event ends, the work does not have to. Many projects fade after the closing ceremony, and anyone who wants to keep going can read about after the hackathon for ways to turn a prototype into something lasting. Anyone who would rather take part remotely can find platform and time-zone tips in the guide to an online hackathon.

Frequently asked questions

Do I need to know how to code?

No. MLH says anyone can attend and that people with no programming background are welcome, and Devpost says nontechnical builders contribute skills such as design, pitching and product strategy.

Does it cost money to take part?

Devpost states that participating in a hackathon as a participant is free on its platform. Other organisers set their own terms, so the event page is the place to confirm.

Can I join without a team?

Yes. Devpost says most hackathons on its platform do not require a team, and MLH says many events run team-formation sessions for solo attendees. Check the individual event rules for any team-size requirement.

Do I need an idea before the event?

An idea helps but a finished plan does not. MLH recommends arriving with a few loose directions rather than a locked specification, and narrowing them once the event starts.

Can I change my mind after joining?

On Devpost, yes: a participant can unregister until they begin a draft submission. Other platforms and events have their own rules.