You signed up for your first hackathon. Now it's two days away and the panic has set in. Everyone else seems to already have a team, a plan, and probably a working prototype in their head already.
Deep breath. Nobody walks in fully ready, and the people who look calm are usually just better at hiding the same nerves you have. This is everything I wish someone had told me before my first one.
1. A Hackathon Is a Road Trip, Not a Race to a Finish Line
Here's the mental shift that helps most. A hackathon isn't really a race where the fastest typist wins. It's closer to a road trip with a hard deadline: you don't need the fastest car, you need a decent plan, someone to read the map, and the sense to stop for gas before you run empty.
Teams that plan their route for twenty minutes before driving off usually get further than teams that floor the accelerator in a random direction. That planning window is the part beginners skip, and it's the part that matters most.
2. What Actually Happens
Most hackathons follow a similar shape:
- Opening ceremony. Rules, theme, prizes, and schedule.
- Team formation, if you don't already have one.
- Building, usually 24 to 36 hours, sometimes longer.
- Submission. A deadline for your code and, often, a demo video.
- Judging or presentations. A few minutes to show what you built.
- Closing and prizes, even if the prize is just what you learned.
Read the rules early. Some hackathons care about a working demo above all else. Others weigh the idea or presentation heavily. Know which one you're in before you start building.
3. Finding or Forming a Team
If you don't have a team yet, don't panic. Most hackathons have a dedicated channel or session for team formation, and plenty of people show up solo.
Look for teammates who cover different strengths: someone comfortable with the backend, someone who enjoys the interface, someone who can pitch well. You don't need four expert coders. A team of one strong builder, one designer-minded person, and one confident talker can beat four people who all want to write the same kind of code.
A few honest questions to ask before teaming up:
- What do you want to get out of this weekend, a prize or the experience?
- What are you comfortable building?
- Are you okay if we scope down the idea to something we can actually finish?
That last question matters more than any technical skill.
4. Picking an Idea You Can Actually Finish
This is where most first-timers go wrong. You'll have a dozen exciting ideas in the first hour. Resist all but one.
A good hackathon idea is:
- Simple enough to demo in three minutes
- Buildable by your specific team in the time you have, not a hypothetical perfect team
- Focused on one clear feature that works well, rather than five features that half work
- Something you can explain in one sentence
If your idea takes more than one sentence to explain, it's probably too big. Cut it down before you write a single line of code.
5. Scope Down Immediately (Then Scope Down Again)
Whatever you plan to build, assume you'll have less time than you think. Sleep, food, technical hiccups, and a stuck bug all eat into your hours.
Try this exercise as a team: write your idea on one line, then list every feature you're imagining. Circle only the ONE feature that makes the whole thing worth demoing. Build that first, completely. Everything else is a bonus you add only if time remains.
A working, boring version of your idea beats an ambitious, broken one every single time.
6. Divide the Work Early
Once you've locked the scope, split responsibilities clearly:
- Who's building which part
- Who's designing the interface
- Who's preparing the slides and pitch
- Who's keeping an eye on the schedule and deadlines
Set checkpoints. "By hour six, the basic version should run end to end, even if it's ugly" is far more useful than "we'll figure it out as we go."
7. Surviving the Sleepless Stretch
You don't need to stay awake the entire time to do well, and you shouldn't try to.
- Sleep in short blocks if you can. Even ninety minutes helps more than pushing through on pure caffeine.
- Eat real food, not just snacks and energy drinks. Your brain runs on more than sugar.
- Take short walks. Stepping outside for five minutes resets your focus better than staring at the same bug longer.
- Watch your caffeine. A crash mid-presentation is the worst possible timing.
- Know your own limits. If you're not thinking clearly, a short nap will get you further than one more hour of tired debugging.
8. When Things Break (They Will)
Something will go wrong. A library won't install, an API will rate-limit you, a teammate's laptop will crash. This is normal, not a sign you're doing it wrong.
- Have a backup plan for your core feature before you need one
- Commit and push often, so you never lose more than a few minutes of work
- Ask organizers and mentors for help. They're there for exactly this, and using them isn't cheating
- Know when to cut a feature instead of fighting it for two more hours
The teams that finish strong aren't the ones that never hit problems. They're the ones that cut their losses fast and moved on.
9. Preparing Your Demo
With an hour or two left, stop coding new features and prepare to show what you have.
- Write a script, even a rough one: problem, solution, quick demo, what's next
- Practice the pitch out loud at least twice
- Prepare a backup, like a recorded video or screenshots, in case live demos glitch in front of judges
- Keep it to the time limit. Going over usually gets you cut off mid-sentence
- Let the actual product do the talking. A working feature beats a slide full of buzzwords
A good structure: what problem you solved, why it matters, show it working, then one line about what you'd add with more time.
10. Talking to Judges
Judges see a lot of similar projects in a short time. Stand out by being clear and honest.
- Lead with the problem, not the tech stack
- Show, don't just tell. A live click-through beats a description
- Answer questions directly. If you don't know something, say so and explain how you'd find out
- Be proud of what you built, even if it's small. Confidence in an honest, modest demo lands better than nervous apologizing
11. Using AI During a Hackathon
Most hackathons now allow AI tools, and using them well can genuinely help you move faster under time pressure. A few habits keep it from working against you:
- Check the rules. Some events have specific policies on AI use, so read them
- Use it for speed on parts you understand, like boilerplate and repetitive code, so you can spend your time on the harder logic
- Still understand your own code. If a judge asks how something works, you need a real answer
- Don't let it write your pitch for you. Judges can tell when a presentation has no person behind it
12. It's Not About Winning
Most people don't win. That's normal, and it's not the point.
What you actually walk away with:
- A project you can add to your portfolio, with a real story behind it
- New friends and teammates, some of whom become long-term connections
- Practice under real pressure, which is its own kind of experience
- A much clearer sense of what you're actually capable of building in a weekend
Some of my most useful lessons about working with a team under a deadline came from a hackathon I didn't place in at all.
Your Pre-Hackathon Checklist
- [ ] Read the rules, judging criteria, and schedule
- [ ] Find a team, or plan to join one on the day
- [ ] Bring a charger, snacks, and something comfortable to sit or lie down in
- [ ] Set up your development environment beforehand, don't waste hackathon hours on installs
- [ ] Agree as a team on one feature that must work no matter what
- [ ] Plan checkpoints for the build
- [ ] Leave the last hour for the demo, not new code
Go Sign Up
If you've been putting off your first one, stop waiting to feel ready. Nobody feels ready. Bring a small idea, a plan to scope it down twice, and the willingness to sleep less than usual for one weekend.
You'll come out with more than you walked in with, win or not.
Let's Connect
I'm Prayush Adhikari, currently grinding through computer engineering, leading an IT club, and building my own company on the side. I write about Linux, productivity, and the honest side of being a developer.
If you're heading into a hackathon soon, tell me what you're building. I'd love to hear about it.
- LinkedIn: linkedin.com/in/adhikareeprayush
- GitHub: github.com/adhikareeprayush
- Portfolio: prayushadhikari.com.np
What should I write next: how to write a resume that gets past the filters before a human ever sees it, or a month-by-month plan for your last year before graduating?

