Key Tenets for a Successful Hack Day

Posted on 04 August 2015

by James Hrisho - Information Architect

Whole Team Meeting

On July 23rd, our engineering team had our first ever Hack Day. This was a whole day for all developers and quality assurance people to self-assemble on teams to work on any project they want to - culminating in a demo session at the end of the day. The teams were actively encouraged not to use this time to get ahead of our backlog, but rather, work on pet projects, prototypes using cutting-edge technologies, and generally creative approaches to problems.

Preparing for the event

We announced the Hack Day to the full team about a week before the event, giving those who didn’t already have a project in the back of their head time to think about what they wanted to achieve. We then collected those ideas in a spreadsheet with a signup portion. People inspired by a project then joined that team and potentially could begin planning with their new team members. In addition to the spreadsheet, I put together a Github repository of APIs and SDKs from AWS, Github, Google Apps, JIRA and HipChat. We use these tools regularly and many of the project ideas included potential integrations. If you are planning a hack day for your team or a general hackathon, having these tools in a centralized place helps get a team moving right away. Lastly, we decided on some key tenets of the day:

  1. Failure is perfectly fine. We are exploring new ideas and failure can be part of that.
  2. Your project might not make it to production.
  3. Open source your project if it is possible.
  4. Try to have something to demo by the end of the day.
  5. Try to work with someone you don’t normally work with and don’t work alone.
  6. This should go without saying – but have fun!

With our tenets set, our resources assembled and projects mostly planned, we were ready for our event.

Day Of


At 8:30AM, the team started to arrive at the office and breakfast was served. People were organizing their thoughts and mostly still waking up. At 9:00AM, we started pitches for each project. While some team members knew what they were going to work on, almost half the team was still up in the air. Each person with an idea was able to pitch to the team in hopes of recruiting members to their cause. Again, a tenet of the event was to not work alone, so it was important for people to put their best foot forward with their pitch. By the end of the pitch session the teams were formed and people got to work.

Tyler pitching his app Will pitching his app Shayna pitching her app Fern pitching his app

Other than a quick break for lunch at noon, the teams worked straight through from 9:30AM to 6:30PM, when our demos occurred. This time was completely uninterrupted, the teams were able to get into the flow and think through their prototypes. The ability to work uninterrupted, allowing a developer to make a large impact into a project in a short amount of time, would come to be the biggest insight from the event.

Anamta Ethan and Will Tommy And Arthur Chris and Zach


At 6:30PM we had dinner and put together the order of who would be demoing. As each team stood up and demoed their work, I was completely blown away by the creativity and the level of sophistication in projects in just one day. The other striking piece was how confident the team was demoing to a large group of people. Demos can be scary, but the culture of humility that we’ve fostered made people feel comfortable. They could stand in front of their peers, show off their in-progress work with a big smile on their faces. They were proud of what they had achieved.

So what did we work on?

Here is a list of just some of the projects:


Maxwell TestBot - An automated testing framework based on Selenium built in Node. Each workflow can be built out using a series of components written in TOML files. Those components then can be mixed and matched to create many different testing scenarios.

Laura and Shayna

MaxVotes - An internal tool to crowdsource ideas and suggestions to our platform built in Ruby. It has a voting system to bubble up the best ideas and a karma system to see who the best idea generators are.

Chris and Zach

4 Strength 4 Stam Leather Belt - Creating a ton of testing scenarios can be tough. This project, built in PHP, helps aid in that by simulating and creating test users in our system en masse.


MongoAdmin - A MongoDB administration tool built in Go. It has the ability to do basic MongoDB functions, finds, find by id, inserts, deletes, and adding and removing of indexes.


PLUG-AND-PLAY - A framework for internal dashboards that lets a developer add different components to make up a large scale dashboard built in Python.

Cory and Tommy

OnDemand - The ability to launch on demand instances of an environment running any branch of code, built with Docker.

Will and Emmma Crushing Code

Mercury - A tool to integrate GraphQL, the new query language format from Facebook with Mongoose and RESTful APIs built in Node.


Tinder for Maxwell Socializing - Built in React-Native, you can post lunch and after-work events, swipe left to ignore or swipe right to commit to come. It also has an internal chat for each event you commit to.

Frank and Will

Maxwell Utils - A dashboard for tools that our internal teams use for administering our system built in PHP.

Emma and Anamta

Bug Reporter - A system that lets anyone report bugs with all of the details necessary to get started: browser version, currently logged-in user, etc., built in PHP.

Wrap Up

After our event we had a short retrospective. It let us review what worked, what didn’t and what we will do better next time. The general consensus was that this was a huge success and that we will absolutely will be doing another hack day in the near future. The work was inspired, innovative, and got people excited about next steps for their projects. We’ve already identified several projects from the event as potential open source candidates and will be introducing those projects as they become open and reach milestones. Other projects will work their way into our system as features for customers and stakeholders.