What exactly is a hackathon?

A hackathon is a time-boxed event, usually anywhere from a few hours to 36 or 48 hours, where individuals or small teams build a working prototype around a theme or problem statement, then present it to judges. The name comes from 'hack' (fast, creative problem-solving, not the criminal kind) plus 'marathon' (a long push against the clock). Teams get judged on things like how well the idea works, how original it is, and how well it's demoed, not on writing production-ready code.

Do I need to already know how to code to join a hackathon?

No. Most hackathon teams need more than programmers: someone to design the interface, someone to think through the problem and pitch it, sometimes someone who understands the business or user side. If you can't code at all yet, joining as a designer, researcher, or presenter on a team is a completely normal way in, and you'll pick up a surprising amount of technical vocabulary just from being in the room.

How is Smart India Hackathon different from a Devfolio or Unstop hackathon?

SIH is a government-run competition (AICTE and the Ministry of Education's Innovation Cell) with fixed teams of 6 students from the same college, problem statements set by government ministries and departments, and a single 36-hour grand finale in December. Devfolio- and Unstop-hosted hackathons are run by companies, communities, or colleges, usually allow teams of 1 to 4, and the rules (team size, themes, prize structure) vary event to event, so you have to check each one's own page rather than assuming SIH's rules apply.

What do you actually get out of doing a hackathon?

Mainly three things: a project you can point to and explain in an interview, practice working under a hard deadline with people you may have just met, and, at the bigger corporate or government hackathons, a shot at cash prizes or a pre-placement interview with the sponsoring company. The certificate is the least valuable part. The habit of shipping something real in a weekend, and being able to talk through why you built it that way, is what actually carries over.

What Are Hackathons? A Straight Answer for Students in India

If you've seen "hackathon" on a college WhatsApp group or a LinkedIn post and aren't sure whether it's a coding exam, a startup pitch contest, or something else entirely, here's the short version: it's neither, and it's more useful than both once you know what you're walking into.

The actual definition

A hackathon is a time-limited event where people, usually in small teams, build something (an app, a prototype, sometimes just a working proof of concept) around a given theme or problem statement, then demo it in front of judges. "Hackathon" is a mashup of "hack," meaning fast, resourceful problem-solving rather than the criminal sense of the word, and "marathon," meaning a sustained push against a deadline. Most run somewhere between a few hours and 48 hours; the classic length at big student events is 24 or 36 hours straight.

The word has a fairly specific origin. The first recorded use of "hackathon" traces to an OpenBSD developer event in Calgary in June 1999, where a small group of programmers worked through cryptography code together to get around US export restrictions on the software. Days later, Sun Microsystems ran a similarly named event, the "John Gage Challenge," where developers wrote Java code for Palm handhelds. Both events happened independently within the same month, which is part of why the exact "who coined it first" question doesn't have a single clean answer, but the timeframe (mid-1999) is well established across multiple write-ups of hackathon history.

What actually happens, hour by hour

Strip away the branding and a typical hackathon follows the same shape almost everywhere:

Registration and team formation. You sign up solo or with a team (event pages usually cap team size at 2 to 6). Solo registrants often get matched into a team at the venue or via a Discord/WhatsApp group beforehand.
Theme or problem statement reveal. Organizers announce what you're building around, sometimes a broad theme ("fintech," "climate," "accessibility"), sometimes specific problem statements set by a sponsor or government department.
Building. This is the bulk of the clock, anywhere from several hours to two full days. Most experienced teams spend the first hour just agreeing on what they're actually building before anyone opens an editor, since that's the step beginners tend to skip and regret.
Submission and demo. Teams submit their project (usually a GitHub repo plus a short video or live demo) before a hard cutoff, then present to judges, often in a 3 to 5 minute pitch.
Judging and results. Judges score against a rubric, typically covering originality, technical execution, how well the demo actually worked, and real-world usefulness. Winners get announced, sometimes same day, sometimes a few days later once judges deliberate.

You don't need to already be a strong coder to take part. Plenty of teams need someone to handle the UI in Figma, someone to think through the actual problem and write the pitch, or someone who understands the end user well enough to keep the build grounded. Non-coders showing up as designers or presenters is normal, not an exception.

The different flavors of hackathon you'll run into

Not every event called a "hackathon" works the same way. The big distinctions worth knowing:

In-person vs. virtual vs. hybrid. In-person events put everyone in one venue for the full duration; virtual ones run over Discord, Zoom, and shared docs so anyone anywhere can join; hybrid events let you pick either. Virtual hackathons widened who can participate a lot, since travel and venue capacity stop being a filter.
Corporate vs. government vs. community-run. Corporate hackathons (think Flipkart GRiD, Amazon HackOn) are run by a company, usually for recruitment, and come with pre-placement interview tracks. Government hackathons like Smart India Hackathon are run by a ministry or public body around real policy or public-service problem statements. Community or college hackathons are organized by student groups or independent communities and tend to have looser rules and smaller prize pools.
Open theme vs. fixed problem statements. Some hackathons let you build anything within a broad theme; others (SIH is the clearest Indian example) assign you a specific problem statement from a list published by sponsoring departments, and you build a solution to that exact brief.
General-purpose vs. niche. Web3 and blockchain hackathons (ETHIndia on Devfolio is the reference example here) run on a sponsor-bounty model where each protocol funds its own prize track, which is structurally different from a single central prize pool.

How this looks specifically in India

If you're a student in India, three names come up constantly and it's worth knowing what separates them:

Smart India Hackathon (SIH), run by AICTE and the Ministry of Education's Innovation Cell, is the largest national one. Teams are fixed at 6 students from the same institution, problem statements come from government ministries and departments, and it runs through internal college-level rounds before a 36-hour grand finale. Registration, internal rounds, and the finale each year follow a published timeline on sih.gov.in.
Devfolio is where most of the Web3-focused and independently organized technical hackathons in India list and run registration, and it doubles as a portfolio site for your past hackathon projects.
Unstop (and platforms like HackerEarth) host most of the big corporate hackathons, plus a wider mix of case competitions, quizzes, and hiring challenges, which is useful if a straight coding hackathon isn't your only interest.

Each platform and each individual event sets its own team size and rules, so the one habit worth building early is reading the specific event's rulebook rather than assuming what worked at one hackathon applies at the next.

Why it's worth your weekend

The honest pitch isn't the prize money, most teams don't win any. It's that you leave with a project you actually built under real time pressure, which is a far better interview answer than "I followed a tutorial," plus practice at the specific skill of shipping something imperfect but working instead of something perfect but unfinished. At the bigger corporate and government events, there's also a real shot at a pre-placement interview or internship attached to strong performance, which is usually worth more than whatever cash prize is on the table. Go in expecting to learn and to build something you can talk about, and treat any prize or interview slot as the upside on top of that, not the reason you showed up.

FAQ

What exactly is a hackathon?: A hackathon is a time-boxed event, usually anywhere from a few hours to 36 or 48 hours, where individuals or small teams build a working prototype around a theme or problem statement, then present it to judges. The name comes from "hack" (fast, creative problem-solving, not the criminal kind) plus "marathon" (a long push against the clock). Teams get judged on things like how well the idea works, how original it is, and how well it's demoed, not on writing production-ready code.
Do I need to already know how to code to join a hackathon?: No. Most hackathon teams need more than programmers: someone to design the interface, someone to think through the problem and pitch it, sometimes someone who understands the business or user side. If you can't code at all yet, joining as a designer, researcher, or presenter on a team is a completely normal way in, and you'll pick up a surprising amount of technical vocabulary just from being in the room.
How is Smart India Hackathon different from a Devfolio or Unstop hackathon?: SIH is a government-run competition (AICTE and the Ministry of Education's Innovation Cell) with fixed teams of 6 students from the same college, problem statements set by government ministries and departments, and a single 36-hour grand finale in December. Devfolio- and Unstop-hosted hackathons are run by companies, communities, or colleges, usually allow teams of 1 to 4, and the rules (team size, themes, prize structure) vary event to event, so you have to check each one's own page rather than assuming SIH's rules apply.
What do you actually get out of doing a hackathon?: Mainly three things: a project you can point to and explain in an interview, practice working under a hard deadline with people you may have just met, and, at the bigger corporate or government hackathons, a shot at cash prizes or a pre-placement interview with the sponsoring company. The certificate is the least valuable part. The habit of shipping something real in a weekend, and being able to talk through why you built it that way, is what actually carries over.