A hackathon is a time-boxed event where teams build something new, usually in 24 to 48 hours. It started in software but now includes hackathons for healthcare, education, public policy, design, and internal innovation. This guide explains what a hackathon is, how it works, the main types, what happens at one, and how to plan a hackathon that produces more than pizza boxes and demos nobody uses.
Hackathon Definition
A hackathon is an event in which small teams work intensively over a short, fixed period to create a working solution to a problem, such as an app, prototype, service concept, or data project, and then present it to judges or peers. The word combines “hack,” in the sense of creative problem-solving, with “marathon.” Hackathons emphasize speed, collaboration, and learning by building.
How a Hackathon Works
- Challenge. Organizers set a theme or specific problem statements.
- Team formation. Participants come in teams or form them on site, ideally mixing skills such as coding, design, and subject expertise.
- Building. Teams research, ideate, and build, with mentors available for advice.
- Demos. Each team presents its solution in a short pitch, often three to five minutes.
- Judging and awards. Judges evaluate against published criteria such as impact, creativity, technical execution, and feasibility.
Types of Hackathons
- Software and developer hackathons. Teams build apps or tools, often using a sponsor’s technology.
- Internal or corporate hackathons. Employees work on ideas for products, processes, or customers. Often called innovation days or innovation sprints.
- Social impact and civic hackathons. Teams tackle community, nonprofit, or government challenges.
- Student hackathons. Run by universities and student groups to build skills and connect with employers.
- Non-technical hackathons. Design, policy, healthcare, or education challenges where the output is a concept, prototype, or plan rather than code.
- Virtual hackathons. Teams collaborate online, often over a longer period such as a week.
Hackathon vs. Workshop vs. Design Sprint
| Hackathon | Workshop | Design sprint | |
|---|---|---|---|
| Length | 24 hours to a few days | A few hours to a day | Usually five days, or compressed versions |
| Teams | Many competing teams | One group or several small groups | One team on one problem |
| Output | Prototypes and demos | Skills, ideas, or decisions | A tested prototype |
| Structure | Loose, teams self-direct | Facilitated activities | Highly structured daily steps |
| Competition | Usually yes | Rarely | No |
Sample 24-Hour Hackathon Schedule
| Time | Activity |
|---|---|
| Day 1, 9:00 | Kickoff, challenge briefings, rules, judging criteria |
| 9:45 | Team formation and idea pitching |
| 10:30 | Building begins |
| 13:00 | Lunch and mentor office hours |
| 18:00 | Check-in: each team shares progress in one minute |
| Overnight | Optional building, with rest space available |
| Day 2, 8:00 | Breakfast and final building |
| 10:30 | Code or work freeze |
| 11:00 | Demos, three minutes per team plus questions |
| 12:30 | Judging, awards, and next steps |
How to Plan a Successful Hackathon
- Write good problem statements. Specific, real challenges with access to users or data produce better work than vague themes.
- Mix skills on teams. Teams with technical, design, and domain knowledge build more useful solutions.
- Provide mentors. Short check-ins with experts help teams avoid dead ends.
- Publish judging criteria early. Teams build to what is measured.
- Plan for after. Decide in advance how winning ideas will get time, funding, or sponsorship. Without this, internal hackathons lose credibility.
- Care for people. Food, rest areas, and a code of conduct matter. Overnight work should be optional.
Frequently Asked Questions
Do you need to know how to code to join a hackathon?
Not always. Many hackathons welcome designers, researchers, and subject experts, and some focus on concepts rather than code.
How long does a hackathon last?
Most run 24 to 48 hours. Some internal and virtual hackathons span a week with part-time work.
What do you win at a hackathon?
Prizes range from cash and products to funding, incubation support, or the chance to develop the idea at work. Many participants value the learning and connections most.
Is a hackathon the same as a design sprint?
No. A design sprint is a structured process for one team on one problem. A hackathon is a looser, often competitive event with many teams.
Running the creative sessions inside a hackathon? See workshop roles and what is a workshop.
