🏆 Hackathon Playbook
From first-timer to winner. Real strategies that actually work at hackathons.
🎯 Prep
👥 Team & Idea
🔨 Building
🎤 Pitching
🚀 After
📋 Before You Register
Pick the right hackathon — College hackathons are low-pressure. Company-sponsored ones have better prizes and networking.
Check the theme — Some are open-ended, some are themed (AI, Web3, Social Impact). Pick one that matches your skills.
Online vs In-person — In-person has better energy and networking. Online is more flexible and comfortable.
Solo or Team — Most hackathons allow 1-4 members. Solo is fine for smaller ones. Teams win bigger ones.
💡First hackathon? Pick a college-level one. Low pressure, friendly judges, and everyone is learning. You'll finish feeling confident for the next one.
🎒 What to Bring (In-Person)
Laptop + charger — Obvious, but people forget chargers
Extension board — Power outlets are always limited
Headphones — For focus time when it gets noisy
Snacks & water — Don't rely on hackathon food alone
Notepad & pen — For sketching ideas and UI wireframes
Change of clothes — If it's overnight, you'll thank yourself
⏰ Timeline — 48-Hour Hackathon
0-2hIdea
2-8hMVP
8-24hBuild
24-36hPolish
36-44hPitch
44-48hBuffer
💡The #1 mistake: Spending 20 hours on code and 2 hours on pitch. Judges see your pitch, not your code. Split time 60% build / 25% pitch / 15% buffer.
👥 Team Formation
Ideal team size: 3 people — one builder, one designer, one presenter
Roles matter: Everyone should know their role before starting. No ambiguity.
Solo strategy: Scope smaller. Build one feature perfectly instead of five poorly. Your pitch is your advantage — you know everything.
💡Finding teammates: Check hackathon Discord/Slack channels. Post: "Looking for [role] for [hackathon]. I do [your skill]." Don't wait until the event starts.
💡 Idea Generation
Problem-first, not tech-first. "What problem can we solve?" beats "What cool tech can we use?"
Check the problem bank — 50+ real-world problems ready to build
Scope ruthlessly. Can you build it in 8 hours? If not, cut features until you can.
Use existing APIs. Don't build what you can borrow — Maps, Auth, Payments, AI. Integration > invention.
⚠️Avoid: Blockchain for the sake of blockchain. AI that doesn't solve a real problem. Ideas that require 10,000 users to work.
🎯 Idea Scoring
| Criteria | Good | Bad |
|---|---|---|
| Impact | Solves real problem for many people | Problem nobody has |
| Feasibility | Buildable in 24-48 hours | Needs months of work |
| Demo-able | Works live, visually impressive | Needs explanation to understand |
| Novelty | Fresh angle or new approach | Clone of existing product |
🔨 Building Strategy
Start with the demo. What will you show on stage? Build that first. Everything else is optional.
Use templates. Don't start from scratch. Use boilerplates, UI libraries, and starter kits.
One feature, done well. A working core feature beats five broken ones. Judges don't check your code quality.
Commit often. Git commit every 30 minutes. If something breaks at hour 20, you can roll back.
⚡Time hack: Set a timer for each feature. If it's not done in 2 hours, move on. Don't perfectionism-kill your project.
🛠️ Tech Stack Shortcuts
| Need | Fast Option | Why |
|---|---|---|
| Frontend | React + Tailwind | Fast to build, looks good |
| Backend | Firebase / Supabase | Auth + DB in minutes |
| AI features | OpenAI API | One API call = magic |
| Maps | Google Maps / Leaflet | Free tier is enough |
| Payments | Stripe / Razorpay | Test mode is instant |
| Hosting | Vercel / Netlify | Deploy in 30 seconds |
🚫 What NOT to Do
Don't learn a new framework during the hackathon. Use what you know.
Don't build auth from scratch. Use Firebase Auth or Clerk. Saves 4+ hours.
Don't skip sleep in 48-hour events. 4 hours of sleep > 4 hours of buggy code.
Don't redesign at hour 30. Ship what you have. Polish what works.
🎤 Pitch Structure (3-5 min)
Hook (15 sec): Start with the problem. "Every year, 50 lakh students waste ₹20K on fake courses."
Solution (30 sec): What you built and how it works. Keep it simple.
Demo (2 min): Show it working. Live demo > slides. Have a recorded backup.
Impact (30 sec): Who benefits? How many people? What changes?
Ask (15 sec): What you need next — feedback, users, mentorship, funding.
💡Golden rule: Judges remember stories, not features. "A farmer lost his entire crop because he couldn't identify a disease" beats "We built an image classifier."
🖥️ Demo Preparation
Test your demo 3 times before presenting. If it fails once, it'll fail on stage.
Have a backup video. Record your demo working. If live fails, play the video.
Zoom in. Make sure judges can see your UI from the back row. Use browser zoom (Ctrl+).
Prepare for questions. Common ones: "How is this different from X?" "What's your business model?" "How does it scale?"
⚠️Never: Apologize for what you didn't build. Focus on what you did build. Confidence wins.
📊 What Judges Look For
| Criteria | Weight | How to Score |
|---|---|---|
| Innovation | 30% | Fresh angle, not a clone |
| Impact | 25% | Real problem, many people |
| Execution | 25% | Working demo, polished UI |
| Presentation | 20% | Clear, confident, engaging |
📝 Post-Hackathon Checklist
Push code to GitHub with a clean README
Add project to your portfolio/resume
Connect with teammates and judges on LinkedIn
Write a short post about what you built and learned
Note what worked and what to improve next time
Find the next hackathon to attend
💼 Portfolio Impact
Hackathon projects are resume gold. They show you can build under pressure, work in teams, and ship fast.
How to present it: "Built [X] at [Hackathon Name] in 48 hours. Won [Y]. Used [tech stack]. Solved [problem] for [users]."
Interview talking point: "Tell me about a challenging project" — hackathon stories are perfect answers.
💡Even if you don't win: The project, the connections, and the experience are worth it. Every hackathon makes you better.
🔍 Where to Find Hackathons
Devpost — Largest hackathon platform, global online + in-person
MLH — Major League Hacking, college-focused
Devfolio — Popular in India, great community
HackerEarth — Company-sponsored, good prizes
College tech clubs — Ask your department or coding club
How to Win Your First Hackathon
Hackathons are intense coding events where you build a project in 24-48 hours. They're the fastest way to learn, build your portfolio, and meet like-minded developers. Whether you're a first-timer or experienced, having a strategy makes the difference between burning out and shipping something great.
The Secret to Winning
Winning hackathons isn't about the best code — it's about the best pitch. Judges see your presentation, not your codebase. A working demo with a clear story beats a complex project with a confusing pitch every time.
Should Beginners Attend?
Absolutely. Hackathons are the best learning environment. You'll learn more in 48 hours of building than in a month of tutorials. Start with college-level hackathons where the pressure is lower and everyone is learning together.