Hackathon registration form
A hackathon form separates skill role — developer, designer, PM — so solo participants can find teammates and organizers can announce how many designers vs. developers registered. It also captures team affiliation in case people pre-form groups, dietary needs for catering, and shirt size for the courtesy t-shirt. Team name is optional so individuals looking for a team can register solo and appear on a "Find a Team" board you create later.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Skill role as a dropdown helps solo participants find teams
Skill is a dropdown — developer, designer, PM, other — not free text. You can filter registrations by skill and publish a "developers seeking designers" board; one value per person means your matchmaking is based on real roles, not interpretations of "full-stack" or "I code and do design".
Team name optional, so individuals can self-select
Team name is optional. Participants who pre-formed a group fill it in; solo participants leave it blank so organizers can run a "Find a Team" session and match them by skill. Your CSV shows both types.
No card required.
Hackathon Registration Form
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add text and email fields for participant name and email — required so you can send schedule changes and announcements.
- Add a phone field (optional) for organizers who need to reach participants with last-minute venue changes.
- Add a text field for team name (optional) — some participants register solo to find teammates, others pre-form a group.
- Add a dropdown for primary skill or role — developer, designer, project manager, other — so participants can find complementary teammates.
- Add text areas for dietary restrictions and a dropdown for t-shirt size so merch and catering are ready on day one.
Fields in this form
7 fields, using 5 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Your name | Short text | Yes |
| Yes | ||
| Phone (optional) | Phone | Optional |
| Team name (if pre-formed) | Short text | Optional |
| What's your primary role? | Dropdown | Yes |
| Dietary restrictions | Long text | Optional |
| T-shirt size | Dropdown | Optional |
What goes wrong with this form
Specific to a hackathon registration form, not general advice about forms.
Requiring team name before the event starts
Making team name required means solo participants can't register, and last-minute applicants forming groups mid-hackathon skip you. Leave it optional so individuals and pre-formed teams both register; add a "Find a Team" session if matching is important.
Free text for skill instead of a dropdown
Skill as free text produces "full-stack developer", "I code and do UI", "designer or front-end", none of which sort cleanly. A dropdown with developer, designer, PM, other is one value per person and gives you real data to match on.
Not collecting dietary or shirt size at registration
Asking these at the door means you order wrong quantities of both. Collecting them at registration means catering and merch are sized to the crowd before the event starts.
Questions about this form
How do I set up hackathon registration?
Name and email (both required), phone (optional), team name (optional), primary skill (dropdown: developer/designer/PM/other), dietary restrictions (text area), shirt size (dropdown). That covers team coordination, skill-based matching, catering and merch.
Why ask for skill if team name is optional?
Skill lets solo participants find complementary teammates. You can run a "Developers looking for a designer?" session at kickoff and match people by skill from your export. Team name being optional means both organized groups and individual participants register together.
What happens if someone doesn't have a team yet?
Leave team name blank when registering solo. At the hackathon, organizers can run a matching session at the start, or participants can network during kickoff. Your export separates registered teams from solos.