On this page
Many students form a hackathon team the same way: the smartest friends in the hostel sign up together and sort out the rest at the venue. That can leave four people who all write backend code and nobody who can make the screen readable or explain the idea to the judges. Here is how to pick teammates with complementary skills, settle roles early and plan a demo you can finish.
What makes a good hackathon team?
In two studies with 699 people working in groups of two to five, researchers found a general "collective intelligence" factor that explained how well a group did across many tasks (Woolley and colleagues, Science, 2010). That factor was not strongly correlated with the average or maximum intelligence of group members. It was correlated with members' average social sensitivity, with how evenly people took turns in conversation, and with the proportion of women in the group.
A large study of hackathon projects found that continuing a project in the short term was associated with technical preparation, while long-term continuation was linked to skill diversity among team members (Nolte, Chounta and Herbsleb, 2020).
So look for a teammate who brings a skill you lack, listens, and will prepare.
How do you find teammates with complementary skills?
Start from the demo, not from your friend list. Most student hackathon projects need four kinds of work:
Builder: the logic, database or hardware that makes it run.
Interface: the screen or layout a user touches.
Problem owner: talks to real users and checks the facts.
Presenter: writes the pitch and runs the final demo.
One person can cover two roles, but every role needs a name. Event rules set team size, so read them first. A planning kit for hackathon organisers gives, as an example, a decision that teams need to have between 3 and 6 members (Affia-Jomants, Gama, Herbsleb and Nolte, arXiv). National events such as the Smart India Hackathon set their own team rules; see our guide to taking part in Smart India Hackathon from college.
Look in your college's coding, robotics and design clubs, in other branches (an electronics student is often what a team of computer science students lacks), and in the team-formation channel that some events run before the start.
A worked example: the skill map
Four friends plan an SMS alert for when a village water tank runs low. They write each name against the four roles. Three are strong in Python; none has used a sensor, and nobody has spoken to a user. The map shows the gap at once: they swap one coder for a friend from electronics who has built an Arduino circuit, and their best speaker agrees to phone people who manage a water supply before the event.
What roles should you agree before the event?
The Harvard researcher Amy Edmondson defined team psychological safety as "a shared belief held by members of a team that the team is safe for interpersonal risk taking", and in a study of 51 work teams she found it was associated with learning behaviour (Edmondson, 1999). At a hackathon, it means saying "this isn't working" without a fight.
Make that easier by agreeing the basics on a short call a week before. A script you can use:
"Our demo is: one user does one task, and it works live."
"I'll own the builder role; you own the interface; you own users and facts; you own the pitch."
"If two of us disagree for more than ten minutes, the role owner decides."
"Anyone can call a stop and say the plan is failing. We check in every four hours."
"Before the event, each of us sets up our tools and tests one small piece."
How small should your hackathon demo be?
Smaller than you think. Another example decision in the same organisers' kit is that teams need to show a working demo as their final presentation (arXiv). For an overnight event, a plan could be:
First 2 hours: lock the one-sentence demo and split tasks by role.
Until the halfway mark: get one ugly version working end to end.
Next quarter: improve only what the judges will see.
Last quarter: stop building, rehearse the pitch twice and record a backup video.
If a teammate has to learn a new idea quickly, for example how a sensor turns water level into a voltage, the Fermi Concept Library has a lesson for every concept in physics, chemistry, biology, mathematics and computing, so they can learn just the part the demo needs.
What if your team stops working together?
Go back to the role list and ask who owns the stuck piece. Our guide on what to do when group project teammates are not working covers that conversation. Parents wondering whether these events are worth the late nights can read what to know when your teen attends science fests and hackathons.
This week, draw your skill map, find the missing role and send the five-line role script to your team.
