What Is a Hackathon and What Is It For? A Guide for Students and Companies
A hackathon is a short program where teams build a working prototype for a defined challenge. Here is how it works, what you get as a student and what a company gets.

A hackathon is a short, time-boxed program where small teams build a working prototype for a defined challenge, then present it to a jury. The word joins "hack" and "marathon". You leave with something built, a team and people who saw your work.
If you just heard the word at university or at work, this guide explains how one works from the inside, what it is for depending on who you are, and what it looks like in practice, with examples from hackathons we run in Mexico.
Key takeaways
- A hackathon has four parts: a published challenge, teams, mentors and a jury with criteria known in advance.
- It is often free for participants; the companies and organizations that set the challenges pay for it.
- You do not need to be an expert: the best teams mix code, design and knowledge of the problem.
- The value of a hackathon shows after demo day: which teams keep building.
How does a hackathon work?
A hackathon runs in five moments: the call, team formation, building, demo day and follow-up. The order rarely changes; the length does.
- The call. The organizer publishes the challenges, rules, prizes and judging criteria. You register alone or with a team.
- Kickoff and teams. Partner companies present their challenges and tools. If you came without a team, you form one there.
- Building. Teams code, design and test. Mentors walk the tables to unblock problems.
- Demo day. Each team shows its working prototype to the jury in a few minutes.
- Follow-up. Winners are announced, repos are published and, in well-run programs, someone follows up with the teams that want to keep going.
Length varies a lot. Spanish Wikipedia describes gatherings of two days to a week (Wikipedia, "Hackathon", read 17 Nov 2026), and Major League Hacking, the student hackathon league, calls them weekend-long "creative sprints" (MLH). There are also online formats that run for weeks.
What is a hackathon for if you are a student?
For a student, a hackathon is a way to build something real in little time, show it to people who hire and leave with a project you can put in your portfolio.
- A project you can show. A public repo with a demo counts for more in an interview than a certificate.
- Access to tools and people. Partner companies often give credits, API access and mentors who work with that product every day.
- A team. Many people meet their future co-founders or project partners at a hackathon.
- Practice under pressure. You learn to cut scope, split work and present in three minutes.
You do not need to be an expert. MLH says its events are for coding veterans and for people just starting (MLH), and the best teams we have seen pair someone who codes with someone who understands the problem.
What is a hackathon for if you are a company?
For a company, a hackathon is a way to see developers use its product on real problems, meet people it could hire and receive prototypes it can review. It is the most direct way to get people using your product.
A concrete example: at Hacktoberfest México 2026, Firecrawl set a challenge and 12 of the 16 teams built with its tool. Abimael Martell, from its technical staff, sat on the jury and mentored on Build Day. The company got real use of its product and a direct conversation with the people who used it.
What is not worth buying is attendance. A full room says little about what happened. In hackathon success metrics we explain what to measure instead: unique participants, projects judged against a published rubric and which teams are still building 30 days later.
What types of hackathon are there?
Hackathons differ by who runs them, where they happen and what gets built. The most common in Mexico are these:
| Type | Who runs it | What you go for |
|---|---|---|
| Student | Universities, clubs and leagues such as MLH | Learning, a portfolio, meeting companies |
| Community | Communities and organizations such as Mobil3 | Building with new tools and with other builders |
| Corporate | A company, for its own team or for outsiders | Prototypes on a company problem |
| Government or social | Public offices, NGOs, institutes | Solutions to a public problem with open data |
| Online | Global platforms | Taking part from any city |
If you are a company considering your own format, the guide to a corporate hackathon in Mexico explains what changes when the challenge is internal.
What does a real hackathon in Mexico look like?
A recent example: Hacktoberfest México 2026 ran for two days, 27 and 28 October in Mexico City, with Major League Hacking and inside the global Hacktoberfest. On day one teams formed and partners presented their challenges; day two was Build Day and Demo Day. There were 7 prize challenges, 5 from partners and 2 from MLH, and at the close 16 teams demoed for the jury.
What came out of it are projects you can review: a platform that measures locally how much energy open language models use and a tool that checks suppliers against Mexico's SAT 69-B list. In what teams built at Hacktoberfest México 2026 we cover each project with its repos.
A larger case is the Mobil3 Hackathon 2025 in Mexico City: 644 check-ins, participants from 12 countries and USD 61,600 in announced prizes.
How do you prepare for your first hackathon?
Prepare before the event, not during it: read the rules, pick one challenge and arrive with your setup ready.
- Read the judging criteria. They tell you what will be rewarded. If they ask for meaningful use of a tool, really use it.
- Pick one challenge, not three. Focusing on one leaves you with something finished.
- Arrive with everything installed. Your editor, your API keys and a project template that already runs.
- Cut scope. A demo that works in three steps beats a big idea that does not start.
- Rehearse the demo. Three minutes go fast. Show the product working, not slides.
- Publish the code. A repo with a clear README is what the jury and recruiters look at afterwards.
If you want to run one instead of joining, the guide on how to run a developer hackathon covers challenges, mentors, judging and follow-up.
What happens after demo day
What happens after demo day separates a good hackathon from a nice photo. Most projects stop when the event ends (the data is in the metrics post linked above); the ones that continue have a clear next step, someone following up and a reason to keep going.
So if you take part, leave with three things: your published repo, the contacts of the mentors and judges you talked to, and a list of what you would do the following week. And if you are a company, ask for a report on what your challenge produced: which teams used your product, who won and which repos were left.
Mobil3 designs and runs hackathons and university programs in Mexico. To hear about the next calls, join our subscription list. If you are a company and want to set a challenge, get in touch.
Sources
Frequently asked questions
- What is a hackathon, in simple terms?
- A time-boxed event where small teams build a working prototype that solves a challenge, then present it to a jury on demo day.
- Do I need to know how to code to join a hackathon?
- Not always. Strong teams mix coding, design, product and knowledge of the problem. Check each event's rules, since some challenges do require code.
- How long does a hackathon last?
- It depends on the format. There are one-day events, weekend events and online formats that run for weeks. Hacktoberfest México 2026 ran for two days in Mexico City.
- Does it cost money to join a hackathon?
- Many student and community hackathons are free for participants. The companies and organizations that set the challenges and prizes cover the costs.
- What does a company get from a hackathon?
- It sees developers use its product on real problems, meets people it could hire and receives prototypes and repos it can review. The useful part is measured after demo day, not by attendance.