Teams finish more often
Opportunity Hack found that hackers who register with a team submit at 39.7 percent. Hackers looking for a team submit at 17.8 percent, and solo hackers submit at 9.8 percent. That is a large gap before anyone writes code.
The same Opportunity Hack report says solo projects ship 46 percent of the time, while teams of 3 or more ship 93 percent+ of the time. Team formation is not just social comfort. It is completion infrastructure.
Keep the team small enough to move
MLH recommends teams of 1 to 4 because it sees hackers have the most success with that maximum size. HackAI 2025 also allowed solo work or teams of up to 4. That makes 1 to 4 the safest default unless the event page says otherwise.
More people can help, but only when the event allows it and the work splits cleanly. A five-person team with unclear ownership can move slower than a three-person team with one demo path and a submission owner.
Cover the minimum roles
Devpost advises virtual teams to diversify roles across front-end, full stack, project management, product management, and design depending on the hackathon. That does not mean you need one person per label. It means you need the work covered.
A practical split is product and pitch, front end, backend or AI, and submission QA. AngelHack says balanced teams with a frontend builder, backend or infra developer, and strong presenter beat all-technical teams. The presenter is not decorative. They convert the build into judge understanding.
Form online without chaos
Devpost says virtual hackathons use the Participants tab plus Slack or Discord-like channels for team formation. Post with specifics: what you can build, what you need, the timezone, and the kind of demo you want to ship.
Avoid vague posts like 'looking for team'. A useful post says 'frontend builder looking for AI/backend teammate, aiming for a 2-minute demo by Sunday morning'. That gives strangers enough information to self-select.
Split work by strength
Devpost advises teams to divide tasks based on each member's strengths. Devpost winner Betsy says her team splits work based on strengths and gets more done that way. This is basic, but beginners still ignore it when everyone wants to touch the exciting feature.
Name owners for repo, demo, submission text, video, and fallback screenshots. If nobody owns the Devpost page, the team discovers missing fields when the deadline is already eating the project.
If you go solo, shrink the idea
Opportunity Hack's solo completion numbers are the warning. Solo can work, but the idea needs one visible output and almost no coordination cost. Choose the path where one person can build, explain, record, and submit without waiting on anyone else.
For solo builders, copy the team process anyway. Make a tiny task board, lock the demo path early, and treat submission QA as a separate role. You are the team, but the work still has different jobs.
< read by a human · updated as things change >
browse hackathons