Hackathon application form
A good hackathon application asks for the idea, one thing the person has built and how they'll take part, then gets out of the way. This template does that in about five minutes, digs into thin answers with one follow-up, and scores every application against the same rubric.
8 questions · about 5 min · edit anything after
Updated · by Ansorjon Juraev, founder
The questions, and why they're asked
In this order: the name first, the substance next, contact details and links last.
- 1
Full name
In the chat: “First, what's your name?”
Asked first and alone, so the chat can greet people properly before anything else.
- 2
What do you want to build?
In the chat: “What would you like to build at the hackathon?”
The idea comes before any form-filling. It's what organizers read first and what applicants care about most.
- 3
Something you've built
In the chat: “What's something you've built that you're proud of? A link helps.”
The best predictor of shipping in 48 hours is having shipped before. Side projects count as much as jobs.
- 4
Are you applying solo or with a team?
In the chat: “Are you coming solo or with a team?”
Helps you plan team matching. A choice, so it's one tap.
Options: Solo, happy to join a team · Solo, I'll work alone · With a team
- 5
What are you strongest at?optional
In the chat: “Which of these are you strongest at?”
Lets you balance teams and spot gaps (there are never enough designers).
Options: Frontend · Backend · ML / AI · Design · Hardware · Product
- 6
GitHub profileoptional
In the chat: “Got a GitHub profile? A username is enough.”
A username is enough: the chat turns it into the full link and checks the profile exists.
- 7
Email address
In the chat: “What's the best email to reach you?”
Asked near the end, once people are invested. The chat confirms it and catches typos like gmial.com.
- 8
I agree to the code of conduct
In the chat: “Last one: do you agree to follow the event's code of conduct?”
Last, as a single tap. Link your code of conduct in the form's description.
Scoring rubric
Each response is scored once on these, with a reason for every score. The weights set the total; you can change them.
| Criterion | What scores well | Weight |
|---|---|---|
| Idea | Specific about the user and the problem; ambitious but doable in the event's time. | 40% |
| Track record | Concrete evidence of things they built, with their own role clear. | 40% |
| Motivation | A personal reason to be there beyond the prizes. | 20% |
Scores are advice for the people deciding. Nobody is accepted or rejected automatically.
Common mistakes
- Asking for a CV and a motivation letter. Builders drop off; you get ChatGPT essays.
- Putting email, phone and links first. People decide whether to finish in the first two questions.
- Scoring on 'passion'. It rewards confident writers, not good builders.
A good answer and a weak one
For “What would you like to build at the hackathon?”
Good
“A tool that turns lecture recordings into flashcards. My cousin is a med student and spends hours making them by hand.”
Weak
“Something with AI that helps people.”
No user, no problem, nothing to judge. The chat follows up once to ask who it's for, so you rarely get answers this thin.