Hackathons reward teams that ship a working, focused demo and explain it well, not teams that write the most code. If you plan the 48 hours deliberately, you can compete with far more experienced teams.
Before the event
- Build a balanced team of three or four: someone strong on the backend or data, someone on the front end, and someone who can design, research users and pitch. One person can hold two roles.
- Read the judging criteria. Most hackathons score some mix of innovation, technical difficulty, impact, design and presentation. Plan to earn points on each.
- Study the tracks and sponsor prizes. Sponsor challenges often have fewer entries than the main prize. Using a sponsor's API well can win you a category.
- Prepare your setup: a starter repository, deployment account, design kit and a shared document for notes.
Hours 0–3: choose a problem, not a technology
Write down three problems you understand personally or can verify quickly with real users. Choose the one where a small demo can show a clear before and after. "Farmers can't check mandi prices offline" is stronger than "we'll use blockchain for agriculture".
Hours 3–6: cut scope ruthlessly
Define the single path a judge will see in your demo: one user, one task, start to finish. List everything else as "later". Sketch the screens on paper before anyone codes.
Hours 6–36: build the demo path
- Get something deployed early, even if it's ugly, so integration problems appear on day one.
- Use real or realistic data. A demo with believable data feels finished.
- Hold quick check-ins every few hours: what's done, what's blocked, what to cut.
- Sleep in shifts. Exhausted teams make mistakes in the final hours.
Hours 36–44: polish and rehearse
Freeze features. Fix the demo path, improve the design of the screens judges will see and record a backup video of the demo in case the Wi-Fi fails.
The pitch
- Problem (30 seconds): who has it, and how you know.
- Demo (90 seconds): show the before and after, live.
- How it works (30 seconds): one diagram, plus what was technically hard.
- What's next (15 seconds): the most important next step and who would use it.
Practise until you finish under time. Judges remember teams that respected the clock.
After the hackathon
Win or lose, publish your project with a clear README, screenshots and the demo video. Add it to your portfolio and connect with the judges and mentors you met. See turning competitions into a portfolio.
Next guide: Tax on prize winnings in India (2026 update)