I Ran My First Hackathon, and So Can You! Here are the lessons I learned from planning, organizing, and executing my first hackathon. The hackathon I ran was the Stupid Shit and Terrible Ideas Hackathon) in Honolulu, Hawaii.

Okay, so first of all, what exactly is a hackathon? I find that when I tell people about hackathons, they assume I am hacking into some mainframe with my hack friends, like some scene out of Hackers.

I define “hackathon” very broadly:

        • Hacking is creative problem-solving. (It does not have to be about technology.)
        • A hackathon is any event of any duration where people come together to solve problems or build something.

The idea for the Stupid Shit Hackathon was born out of the idea that tech — specifically corporate tech — can solve any problem with a weekend of hacking. Climate Change — give me four hackers and 48 hours and I can solve that for you. Homelessness — No problem, we’ll start a hackathon and solve that in a jiffy. The Stupid Hackathon was intended to be a meta-hackathon. Self-aware of corporate tech, male dominated self-seriousness I found at most hackathons. The bottom line is that everyone at the event came in order to build stuff for the sheer joy of creation, not for profit or for glory. Okay, enough by my event, let’s talk about yours!

Over the years as my career as a Software Engineer, I had attended dozens of hackathons, but until now, I had not organized one on my own. I learned a ton through trial and error, research (see resources below), friends (Ray Farias, Jon and Kelli Borgonia, Jason Sewell, Russel Cheng and Victor Lee). I am by no means an expert, but here are the lessons I learned from organizing my first hackathon ever. I hope it helps and encourages other new hackathon organizers to run an amazing event.

In this article, I will cover the following:

  1. How to get prepared for your hackathon
  2. How to market your hackathon
  3. How to get sponsors
  4. How to run the kickoff ceremonies
  5. What to do during the hackathon
  6. How to run the final presentations and award ceremony
  7. What to do after your hackathon

A couple of notes before we dig in:

        • The event I organized had about 60 people in attendance, if you are planning an event with 100 people or more, you are probably on a whole other level and you will need to do a lot more prep work. I would recommend checking out the Hackathon Guide for details on how to run an event with lots of people in attendance.
        • This was a Stupid Shit and Terrible Ideas hackathon, which by its very nature is a very nonstandard hackathon. We wanted to create more of a collaborative and warm vibe so that all of our entrants have fun, but hopefully you can bring the positive and welcoming vibes to your hackathon.
        • This was the first hackathon I ever ran — I definitely still have lots to learn in regards to running a smooth, diverse and inclusive event, but I am trying my hardest.
        • I am a software engineer, not a lawyer. Do not take anything I say here as legal advice.



There’s so much to do before your hackathon. Here are some easy ways to get prepared ahead of time.


Do you want to promote your business? Acquire new talent? Generate new ideas? Solve a problem? Make some stupid shit? Whatever your reason, just know that hackathons are not the be all end all. Hackathons should be used in conjunction with a larger strategy to promote your objectives.

You might not even want to run a hackathon, I would suggest reading, So You Think You Want to Run a Hackathon? Think Again by Laurenellen McCann for thoughts on other (and sometimes better) ways of engaging a community.


Assemble a diverse team just like the Avengers.

If you want to attract a diverse audience, you will want your organizing team to reflect the audience that you hope to attract. For my hackathon, I don’t think that I did a great job at doing of getting together a diverse team, and for my next event, this is something that I really want to focus on improving.


For our hackathon, we created a Slack channel for the organizing team to talk about our tasks. This has worked great for communicating in real time with the team and with the attendees during the hackathon. We were also able to use this Slack account for the team during the hackathon, to organize their own teams and to send out live updates to the teams while they were hacking.


This is the only thing you need to do significantly in advance of the event. The earlier you can reserve space the better. When looking for a space to host your hackathon, be sure to find a venue that can provide:

        • Proper seating
        • One power strip per table
        • Wifi (is it fast and reliable? can it connect all of your participants? does it block any ports?)
        • Projector
        • A microphone, at least in large rooms
        • Accessible entrances and wheelchair-friendly seating space (and if there is a stage, check if it is accessible, if applicable)
        • Gender-neutral, single-occupancy, accessible bathrooms
        • Is food allowed in your venue
        • Is not in the middle of nowhere

Venues are typically very expensive. If you are reserving a professional space like a banquet or conference center, it can run you anywhere from $10 to $40 a head. For our hackathon, we were lucky enough to be sponsored by a local government agency that supports tech growth in Hawaii, HTDC. It might be worthwhile to try and find a place that is willing to sponsor your space, this will especially be easier if your hackathon is for a good cause. If you are running a corporate hackathon, you might be out of luck.


Picking a date for your event is actually really hard. There are many things that you will want to keep in mind. First of all, look at a calendar of other similar events. You do not want to pick a date when all of your developers are at a big local conference if you are trying to attract a large number of developers. You will also want to avoid:

        • Holidays
        • Summer (especially late summer) — This is especially hard for parents
        • Major events in your area (especially other tech events or conferences)

Have it on a weekend — trust us — just do it. Nobody can jam during the week.

Picking a date about 6 months ahead was really helpful for us. We were able to stake a claim on a date before anyone else had a chance to take the great event dates. If you have the ability, be sure to reserve your date as early as you possibly can. We never regretted planning our event so early.


Okay, here are some guidelines for selecting food for your hackathon:

        • The first rule of picking food for a hackathon is “No Pizza”. Pizza is just about the most unhealthy thing you can eat, and tech people eat it at 90% of the events they go to. I have a confession to make, I had pizza at my hackathon. I know, I know, I hate pizza at hackathons, but money was short, and pizza is the cheapest thing you can order for a large group of people.
        • You usually halfway healthy food, right? Order food that you would actually eat if you weren’t at a hackathon.
        • Provide options for people with dietary restrictions. Something I did not do well at my hackathon was providing options for vegetarians, people with allergies, or people with other dietary restrictions. Be sure to have food for everyone.
        • Provide coffee and light pastries and/or fruit for breakfast.
        • Make sure you have lots of water throughout the whole day.
        • Sugar and caffeine are okay. Soda and energy drinks are usually appreciated.
        • Budget about $20 to $40 per head per day for food.
        • When ordering food, be sure to order it at least a couple of days before the event.

Alright, one final thought, for a small event or a non-profit event, food can be optional. Food was the most expensive part aspect of our hackathon, and I would have rather allocated money for swag for everybody, or more inclusive prizes for the winners. For my next hackathon, I would will questions whether we need to provide full meals for the participants or not.



When your participants are signing up for your event is a great time to collect preliminary information about the audience of your hackathon. For our event, we set up an Eventbrite registration form, you can easily collect as much info as you want with it. This worked great for our free event. Hackathon.guide has some great suggestions for types of information that you should be looking to collect on the registration form.

        • Name (and possibly other information as required by venue security)
        • Email address
        • Job title
        • Are they new to hackathons?
        • What kind of hacker are they? Examples: Developer. Designer. Data Scientist. Domain Expert. Government Staff. Communicator. Project Manager. Advocate.
        • What are they interested in hacking on? (free form question)
        • Are they interested in any of the workshops?
        • How they heard about the event
        • Special needs/requests

This information you can collection ahead of time, the better you can plan and prepare.

One final note, according to the Hackathon Guide, “For a free event, about 65% of those who register will actually show up. This number is very consistently seen across events. So cap registration at 150% of your actual maximum capacity.”


Be sure your organization is adequately insured for the event, venue and any other liability (lost or stolen goods at the event, injuries, etc.). While people aren’t likely to be skateboarding or sword-fighting at hackathons, it’s always better to be prepared for the worst.


Okay, so you have been doing all this planning for your big event, but now you actually want people to show up and participate in your event? How the heck do you get people to show up? Well, you gotta get the word out on the street, that’s how! As an engineer, marketing an event is something that I naturally suck at. This was actually a great chance to up my marketing skills.

One note, your marketing plan should be put together in order to fit your objectives for the hackathon. Do you want to reach a particular audience? Do you want to get a massive numbers of submissions? Do you want to attract the top talent in the industry? Do you want to simply promote your brand? Be sure to keep your objectives in mind as you are developing your marketing plan.


You’re running a hackathon, you have got to make a website for your event. This is important for so many reasons. One, make it easy for people to get information about your event. Two, you are going to need it to get sponsors (see below). Your website should cover the following:

        • Make it look professional — this is the site your sponsors will be looking at when deciding if they want to give you money.
        • The who, what, when, where, and why’s of your event (duh).
        • Start and end dates
        • Location
        • Information about parking
        • Reminder about materials needed for the event (laptop, charger, camera, etc)
        • Schedule of events during the day
        • Food that will be provided (if applicable)
        • Times of workshops or training sessions before the event
        • The Code of Conduct
        • Information about the previous years event (if applicable)
        • Information about your sponsors.
        • Contact information for the organizers
        • Link to Eventbrite registration form


Alright, this is a tech event, you basically gotta have an online presence for your hackathon. You should have at least a Twitter account, and a Facebook event page.


        • Create a twitter account for your event
        • Choose a hashtag for your event
        • Encourage people during the event to follow your events Twitter if they want to be updated about future events.

Facebook Group/Event

        • Facebook pages and events are a great way to interact with the community. I have found that people feel more comfortable posting to Facebook event pages then Twitter pages for Hackathons, but that could just be the community I am in.


If you want to attract a lot of people that are new to programming or if you anticipate that many of your participants will be new programmers, than having training workshops leading up to the start date of your event is a great way.

Offer a variety of workshops to the public, with a variety of languages and topics. Marketing them as low pressure workshop will help lower the barrier of entry many people feel when considering joining a hackathon.


I find that prizes can be a great way to market your event, but you need to be careful about the prizes you offer, as they can severely affect the mood of your event. For example, large cash prizes can make the event more competitive, which might turn off lots of inexperienced programmers, future programmers, and future technical leaders. The folks over at Major League Hacking wrote up a much better article than I could ever hope to write about how to select “good” prizes for your event. I encourage you to check out their take on what makes a great or terrible hackathon prizes.


Swag is a great way to do some guerrilla marketing for your event.

Here are some great example of good swag for your event:


        • Making exclusive stickers. Devs love putting stickers on their laptops, water bottles, children, bosses. Basically, we put them everywhere.



This last one is huge, but be sure to get the word out about your hackathon with your mouth. Tell everybody you know, talk about it all the time. Get comfortable with asking your friends and acquaintances to come to your event. Lots of the traffic at my event was due to word of mouth.


Organizing hackathons costs money, there is no way around it. Even if you are running a bare bones hackathon, you are going to need find some money for food, prizes, and space to hack. You basically have two options:

  1. Pay for it out of pocket or
  2. Find corporate sponsors to help you fund your hackathon.

This section is going to cover the later section. I am going to tell give you some tips I picked when you are trying to get people to give you money to help you run your event.


When people are considering whether they want to give you money for your hackathon, the first thing they are going to do is check out your website. Your website will give you credibility, and help sell your event to potential sponsors. Make sure your message is clear and that you represent yourself well. For more tips about what you should have on your website, check out my section about on how to build a great marketing website.


Companies are going to be giving you money, but they will expect something in return. This is your job to sell them on why the people that you are bringing to your hackathon are a good fit for their company. Usually companies sponsor hackathons to get exposure for their products, acquire new talent, to promote their brand. With your team, brainstorm how your are going to sell your event to your sponsors. Be able to explain in simple terms why a company should give you money.


Reach out to big companies that have money allocated to sponsor hackathons, like Microsoft, Google, or GitHub. They are usually easily sold on sponsoring your event since they already have money allocated for events like yours. Plus, once you have these big sponsors, it is usually easier to get smaller companies because you can share how big well-known companies have already sponsored your event. 😉

Okay, so you want to make a cold call to a potential sponsor, what do you even say? Well buddy, I’ve got you covered with this handy-dandy hackathon sponsor email template.

Greetings [Company you are asking for a sponsor],


I’m am [Who you are <student, engineer, space whale> ], and we’re putting together a [Name of your hackathon] on [Start date of your hackathon]. I was thinking that [Company Name] might make a great sponsor for our hackathon. [List out reasons why you think the company is good fit.]


Let me know if this is something you may be interested in and I’d be happy to send your more details or set up a phone call.


Kind regards,
[Your name]


At the kickoff for your hackathon is the time when you set the rules, and expectations for the event. In terms of planning your day, I would argue that this is one of the most important parts of your execution of the event. So, when you are planning an outline for your kickoff, be sure to consider and include the following.


You may have heard that the technology industry has a pretty terrible track record of running events that that make woman and minorities feel comfortable. By making a more positive and inclusive experience, you are more likely to attract women and minorities to your event. As a technology event organizer, you have a tremendous opportunity to make a small difference and to make everyone feel comfortable and welcome.

My personal favorite hackathons are the hackathons that are positive, supportive, collaborative and welcoming to newcomers to the community and to the old pros. I have been to so many hackathons that feel competitive (in a bad way), support unhealthy eating and sleeping schedules, or foster secrecy. All of these things create an ugly dark event that leaves your attendees with a bad taste in their mouth.


Reiterate to everyone what the purpose of the hackathon is. You would be surprised how many people come to your event without having a good idea of what they are about to do. It’s also a great idea to talk about any previous events you have run or to get people excited about starting something new. Tell everyone about how awesome your event it!


Tell everyone who you are, and why you are putting it on the event. This is also a good time to give out your contact information incase anyone wants to get a hold of you during the event.


I think that a great way to start out the event is to thank the new comers to the event for taking a big risk and being brave. I like reminding everybody how hard it is to do what they are doing, and to remind the group to be patient and encouraging to new hackathon participants. I like to have everyone give a round of applause to the newcomers at the kick off. As an organizer, keep a list of projects and more senior mentors that you can pair your new comers with. You want to make sure that everyone at the hackathon feels like they have an important job to perform or else you will lose the new comers and likely, you will never see them ever again. It is in your power to make sure that they have a great time at their first hackathon.


At the day of the hackathon, we weren’t exactly sure what types of projects people would be submitting, so we wanted to leave the prize categories fluid till up till submission. This was challenging for some people at our hackathon. They wanted to have a clear understanding of the rules and how it was going to be judged. We also changed the submission time twice during the hackathon based on information about how people were submitting their projects. If I were to run this hackathon again, I would have been more clear up front about the rules and have a clear time table of events established up front.If I were to take this another step further, I would have a handout to give everyone with the rules, categories, and a timeline of events through out the day.


Your sponsors are funding your event, they expect to get something in return. Usually this is recognition for their time, money and efforts in front of their techie audience.


We wanted everyone to have fun at our hackathon, and we wanted to be serious about making sure that we ran an inclusive and diverse event. That’s why we put together a Code of Conduct for our hackathon. This code of Conduct was a conglomeration of lots of other anti-harassment policies put together by much smarter and much more diverse tech people than myself. I don’t want to pretend to be an expert on diversity in tech, but I do want to try my hardest to make sure everyone feels comfortable at my events. As with everything in this article, I am open to feedback.

Your Code of Conduct is more than a set of rules it is your way of setting the community norms at your event. Use your Code of Conduct as a means of creating a positive environment that fosters collaboration.

The Hackbright Academy’s code chimes in with four simple main guidelines:

  1. Be respectful.
  2. Be thoughtful.
  3. Be open.
  4. Be awesome.


When writing your own Code of Conduct, I would check out these awesome examples and take the parts that work best for you and your event. Here are some great examples:

If you’re interested in more, the Ada Initiative has a thorough list of conferences with anti-harassment policies.


Go over the schedule of workshops, lunch, end time, etc. You can also use this time to encourage people to take and share session notes and to record progress on projects.


In my experience, people groan and grumble when they hear that there is going to be a ice breaker activity, but having one has consistently made the vibes at events with them more positive and inclusive. I would highly recommend having one at your hackathon. This site has some great ideas for ice breakers for large groups.

I have also tried splitting into groups of anywhere from 5 to 10 people. Each person introduces themselves, and you can have a quick brainstorm of ideas for the hackathon as a group. This can be helpful if not many people have ideas prepared for your hackathon. It is also a good way for newcomers to meet other people and to possibly join a group.


This is going to be the shortest section, because it’s the easiest for the organizer. That’s because:



I feel so strongly about this. The only reason you should break the participants flow is if you are letting them know that food is there or to check in and to make sure that hacking is going smoothly. I hate it when I go to a hackathon, and my flow is interrupted.


You survived the whole hackathon, now we are at the end and we have just one last thing to do, presentations and awards!


Collecting information about each team’s project is always a pain in the butt. We tried a couple of different methods for collecting submissions. We have tried using GitHub and DevPost.


        • Setup a GitHub organization and add your hackers as users. Encourage them to commit their code through-out the hackathon, and wrap up the weekend with a nice README file of their project.


        • DevPost is a web application for running hackathons, it makes it easy to aggregate your submissions and to collect valuable team information.

I personally have no strong preference for either one, but whichever method you choose, be sure that you have a system for collecting information about your participants. It will be useful for the judging process, marketing materials, and future events.


Keep your final presentations short and stick to your time limit. For our hackathon, we had a very strict 1 minute time limit. This was perfect for event, it was enough time to quickly demo all of the projects and tell a couple of jokes. It keeps the ceremony from stalling, and from your presenters from rambling on and on. For your event, you might need to give your presenters more time, and that’s okay, just be sure to stick to your predetermined demo time. Your audience will respect you and you won’t eat up too much of everyone’s valuable time.You can check out our final presentations here, Stupid Shit Hackathon Honolulu: Presentations and Awards.



After your hackathon is over, be sure to meet up with your organizing team to debrief. Talk about all the things that went well, and write them down, you will be thankful to have these notes the next time you run a hackathon.


It’ll help you avoid your terrible mistakes again the next year.


Compute how much the event cost in total and per participant, just to know for next year.


Ask the attendees about what they liked and didn’t like. It’ll help you improve your event for next time.


Don’t know how to write up a wrap-up report? Check out this great guide to writing a report about your tech event. It helped me write my blog post about my Stupid Shit Hackathon.


Something that was important for me at my hackathon, was to put all of the submissions on our website. All to often, I find that hackathon submissions disappear and die the Monday morning following a hackathon. No one ever looks at that project or the code ever again. Something I appreciated about the Stupid Hackathon in New York is that they posted all of the projects with photos, videos, descriptions, links, and authors for all of their projects. It helps promote the event, and helps share the work that people worked so hard on at your event. I know that I have personally loved looking at the amazing projects created at the original Stupid Hack, and is something I wanted to bring to my hackathon. This is also something that I would like to continue doing at all of my future hackathons.

Do you have more ideas for how to run a hackathon — let me know. This was only my first event, and I know I have lots to learn. Or do you want to brainstorm strategies for how to run your next hackathon? Shoot me a message at joe@callmejoe.net



Special thanks to all of the people and organizations that helped me with planning the hackathon (In no particular order):

        • Ray Farias — Co-Organzier, This wouldn’t have happened without you
        • Jon Borgonia — For helping with the logistics and support
        • Kelli Borgonia — For helping helping me stay organized
        • Sean Nakamura — For helping me with collecting submissions
        • Victor Lee — For helping with getting sponsorships
        • Jason Sewell — For his vast hackathon planning experience
        • Russell Cheng — For helping Ray and I get prepped for speaking on the radio
        • Spencer Toyama — For supporting the event and providing food
        • Jesse Thompson — For making trophies and prizes for the hackathon
        • DevLeague — For hosting the event. You are amazing! (Full disclosure, I work for DevLeague)
        • Sudokrew — For sponsoring the event. 😀
        • HTDC — For hosting the space for the hackers

My name is Joe Karlsson, and I am a Honolulu based full-stack JavaScript instructor and engineer with a passion for exploring the creative potential of technology. You can follow me on: