Hackathon
HAK-uh-thon
A time-limited event where developers build projects using a product, competing for prizes and learning through hands-on experience.
A hackathon is an event where developers build projects within a time constraint, usually 24-48 hours. For developer tool companies, hackathons serve multiple purposes: developers learn the product by building with it, the company sees creative use cases, and the best projects become case studies.
Hackathons can be in-person (at a conference or office), virtual (developers participate from anywhere), or hybrid. Virtual hackathons have become the norm because they reach more developers. A virtual hackathon can attract 500+ participants from around the world.
The key to a good hackathon is the constraint. Developers build faster under time pressure and with a specific theme. The theme should be broad enough for creativity but narrow enough to be relevant to your product. Prizes motivate participation but the best developers participate for the learning and community.
Examples
A company runs a virtual hackathon.
Theme: 'Build an AI-powered developer tool in 48 hours.' 300 developers register. 150 submit projects. 10 finalists present to judges. The winning project becomes a featured integration in the product's marketplace. The company gains 300 new users who deeply understand the product.
A hackathon at a conference.
At the annual developer conference, the company hosts a 24-hour hackathon. 80 attendees participate. The company provides mentors, API credits, and swag. Projects are demoed on the main stage the next day. The energy from the hackathon carries into the rest of the conference.
Hackathon projects reveal unexpected use cases.
A hackathon team uses the API in a way the product team never imagined: monitoring coffee machine IoT sensors. The project wins a prize. The product team takes note: IoT monitoring is a use case worth supporting.
In practice
Read more on the blog
Frequently asked questions
How do you run a successful virtual hackathon?
Clear theme and rules, generous timeline (48-72 hours), a Discord or Slack channel for support, mentors available to help, simple submission process, and prizes that developers actually want (hardware, conference tickets, product credits). Promote 4-6 weeks in advance.
What makes a good hackathon theme?
Specific enough to guide creativity, broad enough for diverse projects. 'Build anything with our API' is too broad. 'Build a healthcare app' is too narrow. 'Build a tool that helps developers work faster' strikes the right balance for a developer tools company.
Related terms
A group of developers who use a product and connect with each other to share knowledge, solve problems, and provide feedback.
A formal program that recognizes and empowers the most active and influential developers in a product's community.
A hands-on educational session where developers build something guided by an instructor, learning by doing.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.