Guides
How to prepare for a hackathon as a beginner: a fluff-free checklist
What to learn in advance, what to bring with you, and how not to get lost at your first hackathon.
A beginner's main fear before a hackathon is: "I'm not good enough, they'll find me out." Spoiler: hackathons aren't filled with ready-made seniors, but ordinary people trying to build something over the weekend. Preparation isn't about becoming a genius in a week, but about not wasting precious hours at the venue on things you could have done at home.
What to learn and configure in advance
Don't try to master a new framework three days before the start. Instead, practice what you already know until it's second nature. The value at a hackathon lies not in the depth of your knowledge, but in the speed with which you turn an idea into a working screen.
- Deploy a project template in advance so you don't have to set up the environment at the start.
- Install and configure the AI tools you code in: Cursor, Claude, Copilot, or their equivalents, and make sure everything works.
- Create accounts and get API keys you plan to use, and check the limits.
- Refresh your memory on what you do most often: API requests, a simple database, deployment, forms.
And one rule of vibecoding to learn before your first hackathon: don't submit code you don't understand yourself. AI speeds things up, but when the jury asks "how does this work?", you'll be the one answering, not the model. We discussed which tools to include in your toolkit in a separate guide.
What to bring with you
The list is boring, but it's exactly because of its absence that people suffer at night.
- Laptop, charger, and extension cord. There are always fewer outlets than people.
- Headphones to block out the noise and focus.
- A spare t-shirt, toothbrush, and deodorant if the hackathon involves staying overnight.
- Snacks and water, even if food is provided. At night, food runs out faster than your energy.
- Power bank and adapters.
The mindset that helps
The goal of your first hackathon is not to win, but to reach the finals with something working. This is already a success that overcomes the fear of a blank slate. Teams that deliver a small but live project almost always beat those who aimed for something grandiose and ran out of time.
Don't be afraid to ask. Mentors at the venue are there for exactly that, and if something is unclear about the rules or deadlines, there is a Q&A board on the event page where organizers answer publicly for everyone. This way, you don't sit around guessing or waiting for a DM reply.
Where to keep all of this handy
To avoid getting lost, it's great when the event lives in one place rather than being scattered across chats. On Stavleak, you fill out your skills profile once, and organizers and your future team immediately see what you can do. The schedule, announcements, and reminders are sent there and to Telegram, and a personal checklist during the hackathon shows what has not yet been submitted so you don't forget anything in the rush. If the organizer has partnered with an AI sponsor, access to paid models is also provided right here in your dashboard.
Where to start your search
If you haven't chosen where to go yet, start with open events for beginners. Browse the hackathon catalog and the list of upcoming events, filter by format and dates, and look for one where beginners are welcome. Your first hackathon should be chosen not by the size of the prizes, but by the atmosphere and entry level.
And one last thing. Show up even if your team isn't assembled and your idea isn't ready. Half of the best projects are born from connections made in the first hour at the venue. How to assemble a team, including in advance via the search board, will be discussed separately.