Your First Hackathon: A Beginner’s Checklist

hackathon for beginners

A hackathon for beginners is a short, team-based building event where no prior experience is required to take part. Start with a small goal, a friendly team and a clear plan for what to bring and ask.

Online hack events grew sharply during the pandemic, and the story of that period is told in the guide to the covid-19 hackathon movement. This checklist focuses on the practical side of a first event.

What a hackathon actually is

A hackathon is a time-boxed event in which people collaborate intensively to make something that works. According to the encyclopedia entry on hackathons, the work happens over a relatively short period, such as 24 or 48 hours in person or several days online. The goal is to produce functioning software or hardware by the end of the event.

The word itself blends “hack” and “marathon”. In this setting “hack” means exploratory programming, not breaking into computer systems. That distinction matters for newcomers, because the event is about building and learning, not about security attacks.

Many events have a theme, a technology or a cause. Others leave the subject open. Reading the theme before anything else tells a beginner whether the event suits their interests, and it often reveals whether the organisers expect code at all. Design, writing, research and presenting all count as real contributions.

Decide whether you are ready

Beginners often assume they must be fluent programmers. In practice, teams need a mix of skills. The same encyclopedia entry notes that people involved include programmers, graphic designers, interface designers, product managers and domain experts. A newcomer who can sketch a screen, interview a user or write a clear explanation has something concrete to offer.

It still helps to pick a lane before the event starts. Ask yourself three simple questions:

  • What can I already do well enough to be useful on a team?
  • What would I like to learn, even if I do it slowly?
  • How many hours can I realistically stay focused without burning out?

Honest answers make it easier to choose a team and a task. They also protect you from the common mistake of agreeing to a role that is far beyond your current skills on the first day.

Choose an event that welcomes newcomers

Not every event is aimed at first-timers. Student-focused events, community meetups and online events run by developer communities tend to be the gentlest starting points. Major League Hacking describes itself on its about page as a developer community that serves people through hackathons, fellowships and other programmes. Its member events are a common route for students trying the format for the first time.

When comparing events, look for the following signals on the event page:

  • A statement that beginners or students are welcome.
  • Workshops, mentors or office hours during the event.
  • A published code of conduct and a way to report problems.
  • Clear rules on teams, eligibility and what you may reuse.
  • A format that suits you: in person, fully online, or mixed.

Online events lower the cost of entry because there is no travel, but they ask for more self-discipline and clear communication. The planning rules that organisers use for remote events apply equally to participants.

hackathon for beginners laptop notebook
A laptop showing code beside a notebook and a pen.

Read the rules and the code of conduct

Every serious event publishes rules. Read them before you register, not on the first night. Look for team size limits, whether work done before the event is allowed, what happens to the intellectual property in your project, and how submissions are judged.

A code of conduct is just as important. The Major League Hacking policy, published on its code of conduct page, opens with a plain summary: be respectful, and harassment and abuse are never tolerated. It also sets out how attendees can report problems at member events. Knowing that a reporting route exists makes a first event feel safer, and it is a good sign when organisers publish one.

If anything in the rules is unclear, ask the organisers in advance. Questions about eligibility, prizes or ownership are routine, and a well-run event answers them quickly.

Prepare before the event starts

Preparation is where beginners gain the biggest advantage. None of it needs to be elaborate.

Set up your tools

Install the editor, language runtime and version control tools you plan to use, and confirm that they work. Create accounts on the platforms the event uses for submissions and team chat. Time lost to installation problems on the first evening is the most avoidable frustration of all.

Learn one small workflow

Practise a tiny end-to-end project beforehand: make a page, save it with version control, share it with a friend. A beginner who has completed this loop once feels far less pressure when the clock is running.

Prepare your practical kit

For in-person events, bring a charger, headphones, water and a notebook. For online events, test your microphone, camera and connection, and choose a quiet corner. Agree in advance how and when you will rest.

Item Why it helps
Working development setup Avoids losing early hours to installation problems
Accounts for the event platform Lets you join teams and submit without last-minute stress
Notebook or whiteboard Makes it easy to sketch ideas and divide tasks
Headphones and a charger Protects focus and keeps devices running

The checklist above is a general preparation list prepared for this guide; your own event’s rules, such as the Major League Hacking policy, come first.

Find a team and agree how to work

Many events help attendees form teams through a chat channel, a networking session or a team-matching board. Introduce yourself briefly and state what you can do and what you hope to learn. Teams that value learning are usually the best fit for a first event.

Once a team forms, spend the first stretch agreeing on a few basics: who owns which part, how decisions are made, and when everyone checks in. A short written plan on a shared board prevents the confusion that appears when several people edit the same files at once. It is worth knowing the roles that tend to appear in a team before you pick yours.

Keep the scope small. A modest project that works and is clearly explained usually beats an ambitious one that is unfinished. Decide early what the smallest useful version looks like, and build that first. Extra features are a bonus, not a requirement.

Plan your time and look after yourself

A hackathon rewards steady progress. A simple rhythm works for most beginners: spend the opening stretch choosing an idea and dividing tasks, the middle building the core feature, and the final stretch testing, polishing and preparing the demonstration.

Protect your energy. Eat properly, drink water and take breaks away from the screen. Sleep is not a luxury; tired people make more mistakes and work slower. If the event runs over several days, plan rest into your schedule rather than hoping adrenaline will carry you.

Ask for help early. Mentors and organisers are there to unblock participants, and a short conversation can save hours. Beginners who wait until they are stuck for a long time often find the answer was simple.

Show your work and keep going afterwards

Most events end with a short demonstration. Practise it aloud, state the problem, show what works, and name what you would do next. Honest, clear demos are valued more than polished slides, and judges tend to appreciate a team that knows its limits.

Whether or not a prize comes your way, the event is only the start. Write down what you learned, save your code in a public or private repository, and thank your teammates. If the idea has promise, there is a path from prototype to lasting project, described in the guide on what to do after the hackathon. Some themes also connect to community work, such as the projects discussed in the guide to the energy hackathon and other cause-focused events.

Frequently asked questions

Do I need to know how to code to join?

Not always. Teams usually need designers, writers, researchers and presenters as well as programmers, so check the event page to see which skills are welcome.

What should a beginner build?

Choose the smallest idea that solves a real problem and can be shown working. A simple tool that functions is more convincing than a large plan that does not.

Is it safe to attend as a newcomer?

Well-run events publish a code of conduct and a reporting route. Read it before registering and contact the organisers if anything is unclear.

Can I take part online?

Yes. Many events run fully online, which removes travel but calls for good communication, a stable connection and a quiet place to work.