Guide
First Hackathon Checklist: What to Do Before, During and After
Your first hackathon can feel chaotic: a new team, a deadline, and a room full of people who seem to know exactly what they are doing. This first hackathon checklist breaks it into simple steps so you can focus on building.
Before you pick an event
Start by choosing an event that fits where you are right now. A college hackathon with a friendly crowd is a gentler start than a large sponsor-run competition. Browse the hackathons directory and look at the format, the duration and the team size limit. If travel is a problem, the online hackathons list lets you try the format from home.
If you live in or near the capital region, the Delhi NCR events page is a good place to find something within a metro ride. Students in the south can check Bengaluru. Use the timeline to see what is coming up over the next few weeks so you have time to register and prepare.
- Read the event page fully: theme, tracks, eligibility, rules, and judging criteria.
- Register early. Many events cap the number of participants and close sign-ups before the date.
- Check whether the event is open to all colleges or only to students of the host institute.
- Confirm the schedule, including when you must arrive and whether you can stay overnight.
One to two weeks before
Do not wait for the opening ceremony to sort out your basics. Set up your tools now so the first hour is spent thinking about the problem, not installing software.
- Create or update your GitHub account and make sure you can push a commit from your laptop.
- Pick a stack you already know. A hackathon is a bad place to learn three new frameworks at once.
- Build a tiny starter project that you can reuse: a frontend, a simple backend and a deploy to a free host.
- Sign up for any APIs or tools that sponsors mention, so keys and accounts are ready.
- Read about how to win a hackathon so you know what judges look for.
Sort out your team
Most events allow teams of one to four people. Three or four is common, but two good teammates can beat a larger group that cannot agree on anything. Try to cover a few roles: someone comfortable with the backend, someone who can build the interface, and someone who can handle the demo and the story. If you do not have a team yet, our guide on how to find hackathon teammates explains where to look. Going solo is often allowed too, so check the rules before you panic.
What to bring to an in-person hackathon
Indian college hackathons often run for a full day or through the night, and the venue may not have everything you need. A simple packing list saves a lot of trouble.
- Your college ID card and a government photo ID, since entry is often checked at the gate.
- A printout or screenshot of your registration confirmation.
- Laptop and charger. Keep the charger in your bag, not at your hostel.
- An extension board, because wall sockets are shared and often far from your seat.
- Phone charger or a power bank, and earphones for focus.
- A water bottle, a small snack, and any medicines you need.
- A light jacket, since halls with strong air conditioning get cold at night.
- Basic toiletries and a spare t-shirt if the event runs overnight.
- A notebook and pen for sketching the idea and the demo flow.
During the hackathon
The first hour decides a lot. Spend it agreeing on one clear problem and one clear user. Then cut the idea down until it feels almost too small. A working small project beats a half-built big one every time.
- Write the idea in two sentences. If you cannot, it is not ready.
- Split the work so each person owns a piece and nobody blocks another.
- Get a rough end-to-end version working early, even if it looks ugly.
- Commit often and push to a shared repository so nothing lives only on one laptop.
- Talk to mentors and sponsors. They can unblock you in minutes and often judge too.
- Eat, drink water and take short breaks. Tired teams make silly mistakes late at night.
- Freeze new features a few hours before the deadline and spend that time polishing.
What to submit
Submission is where many first-timers lose points, so treat it as part of the work, not an afterthought.
- A public repository with clean, working code.
- A README that explains what the project does, who it is for, how to run it, and which tools you used.
- A demo video of two to three minutes that shows the product working, not just slides.
- A live link or screenshots if the event asks for them.
- Any form or platform entry the organisers require, submitted before the cut-off time.
Record the video before the final rush. If something breaks during the live demo, you will still have a clean recording to fall back on.
After the hackathon
The event ending is not the end of the work. Within a few days, do the following while the memory is fresh.
- Add the project to your resume and your GitHub profile with a short description.
- Write a short post about what you built and what you learned.
- Message the people you met, mentors included, and thank them.
- Note what went wrong so the next event goes better.
- Pick your next event from the hackathons directory, or subscribe to a few newsletters so new events land in your inbox.
Organising something yourself or know an event we missed? You can submit it and help the next beginner find it.
FAQ
Do I need to know how to code to join my first hackathon?
Not always. Many hackathons welcome designers, writers and people who can pitch or research. Still, a basic ability to build something small helps a lot. If you are new, join a team with at least one person who has shipped a project before and ask for a clear, small task.
What should I carry to an in-person hackathon in India?
Carry your college ID and a government photo ID, your laptop and charger, an extension board, a phone charger or power bank, a water bottle, basic toiletries, a light jacket and any medication you need. Check the event page for extra requirements such as a registration confirmation or printed pass.
How big should my team be?
Most hackathons allow teams of one to four people. Three or four is common, but a team of two can move faster. Check the rules on the event page, since limits differ between events.
What do I have to submit at the end?
Usually a public code repository, a README that explains the project and how to run it, and a short demo video of two to three minutes. Some events also ask for a slide deck or a live link. Read the submission rules early so you are not surprised.
Is a first hackathon worth it if I do not expect to win?
Yes. You will learn how to scope, build and present in a short time, meet people who build things, and end up with a project and a demo you can show. Winning is a bonus, not the point of a first one.