What to expect at your first AI hackathon

Expect a short, focused stretch of building with a clear end point. Every event sets its own format, so read the schedule and rules for yours. You do not need to be an expert. A first event is mostly about learning, and it tends to go well when you prepare a little and keep the scope small.

What might the schedule look like?

Formats vary from event to event, so treat the outline below as a sample you can adapt, not a description of any particular event. It assumes a weekend. Use it to plan your own time, then check your event's actual schedule.

When	What might happen	What you can do
Day 1, start	Opening: welcome, rules, themes	Note the deadlines and how projects will be assessed
Day 1, first hours	Teams settle and pick an idea	Agree on one problem
Day 1, evening	Planning and setup	Write a one-paragraph spec, split roles, set up the repo
Day 2, morning	Core build	Get the main feature working end to end
Day 2, afternoon	Any sessions the event offers	Attend the ones that unblock you
Day 2, evening	Check-in	Cut anything that will not be ready
Day 3, morning	Polish and test	Fix bugs, write the README, record a backup demo video
Day 3, before deadline	Submission	Submit early, then check every link works
Day 3, afternoon	Demos	Present, answer questions, watch other teams
Day 3, end	Wrap-up	Thank your team, connect with people you met

How do online and in-person events differ?

Both formats follow a similar arc, but the experience is different.

In person, you share a space with other teams. It is easy to ask the next table a question, and you can talk through problems face to face. The trade-offs are travel, noise, and the temptation to stay up all night.

Online, your team works from different places, possibly in different time zones. You communicate through chat, video calls and a shared repo. That takes more discipline. Set fixed check-in times, write decisions down, and agree on who submits. Read the submission rules early so you know what format your demo should take.

What if you come alone?

Arriving on your own is fine. A few ways to approach it:

• Introduce yourself in the event's chat or community space before it starts. Say what you can do and what you want to build.
• Look for people whose skills complement yours. Design, front end, data and product thinking all help a team.
• Keep the team small. A good rule of thumb is that a few people are easier to coordinate than many.

You can also work solo if the rules allow it. It is harder, but it is a fine way to start.

How do you avoid common first-time mistakes?

A few rules of thumb help:

• Pick one problem. A small project that works beats a big one that does not.
• Get something running early. Aim for a rough end-to-end version by the middle of the event.
• Read how projects will be assessed, if the event says, and build toward it.
• Sleep. Tired teams make slow decisions and break working code.
• Submit early. Treat the deadline as fixed, and leave time for an upload to fail.
• Practice the demo. Show the problem, the working product and what is next, in that order.

What should you pack and set up before you go?

Setup checklist (both formats)

• Accounts created for the tools, APIs and cloud services you plan to use
• API keys stored safely, and never committed to your code
• Code editor, Git and your main language runtime installed and updated
• An account on a code host such as GitHub, and a test repository you can push to
• The event's chat joined, with notifications on for announcements
• Rules and submission requirements read
• A screen recording tool ready for a backup demo video

Packing checklist (in person)

• Laptop and charger
• A power strip or extension lead, labeled with your name
• Phone charger and headphones
• Water bottle and a few snacks
• Layers of clothing, in case the room is cold
• Toiletries, and a travel pillow if the event runs overnight
• Photo ID, in case the venue asks for it

Online extras

• Stable internet and a backup, such as a phone hotspot
• A working microphone and camera
• A quiet space for demo time

If you plan to use an AI coding agent, set it up and test it before the start. Starfield Labs has an MCP connection for agents, so you can bring your agent with you. Test it with real inputs ahead of time so you are not debugging your setup while the clock runs.

What will you take away?

Whatever happens with your project, you will leave with practice in scoping, building and presenting under a deadline, and with people you have built something with. That is a good outcome for a first event. Write down what you would do differently while it is fresh, and bring the list to your next one.

Where to go next

The best preparation is to sign up for a first event. Starfield Labs runs hackathons online and in cities, along with workshops, build days and demo nights. Browse upcoming events at starfieldlabs.ai/events, pick one with a theme you care about, and use the checklist above. To learn a tool or API before the weekend, try the tutorials at starfieldlabs.ai/tutorials.