Suggested team size
Four is the magic number. Three is too small for parallel work, five is too many for a 24-hour sprint. Preset to 4 per team here.
Hand-picking hackathon teams turns into a popularity contest. Randomise it instead โ and use ratings to balance senior engineers across teams.
Tip: set ratings with the โ
pickers below, or paste them inline like Alice, 5 on each line.
The free version does the job. The optional template pack just makes brackets look beautiful for events, classrooms and clubs.
Free forever for basic use ยท No signup required
Internal company hackathons, university hack days, civic-tech weekends. Skill ratings keep one team from hoarding all the senior engineers.
Names or handles.
Quick estimates work fine.
Each team has a mix of seniors and juniors.
Four is the magic number. Three is too small for parallel work, five is too many for a 24-hour sprint. Preset to 4 per team here.
Enter them as one entry: 'Alice + Ben + Cara'.
Mix departments fairly so every breakout group has a mix of design, engineering, sales, and ops โ without picking favourites.
OpenStop one team carrying the whole game. Rate each player 1โ5 and we'll split them into teams whose total skill is as even as possible.
OpenFour-team splits are the sweet spot for tournaments โ enough variety for a real competition, small enough to fit in one afternoon.
OpenMix up who pairs with whom. Drop your engineers' names, generate pairs in seconds, paste into the sprint kickoff.
OpenRandom pairings for the dreaded 'now go talk to someone you don't know' moment. Make it painless.
OpenFree forever for basic use. No signup required. The free version really does do the job.
Want prettier prints? See the optional template pack