HuskyHacks 1 at Northeastern University

HuskyHacks is Northeastern University's first 24-hour CCIS hackathon. Over 100 students will form teams and have from the afternoon of April 2 to the evening of April 3 to build something amazing. The possibilities are limitless; learn a new language, power on your Particle for the first time, try on an Oculus Rift, and turn your dreams into reality. Students will be allowed to innovate using any software or hardware tools, as long as they are working on a fresh project. No previously started projects will be allowed. Over 100 HuskyHacks participants will be chosen based on application, and the event will be held in West Village H April 2-3.

 

The schedule of HuskyHacks will be as follows:

  • 10:00-11:00AM Saturday: Registration
  • 10:45AM: Lunch
  • 11:00AM: Opening Ceremony
  • 12:00PM: Hacking Begins
  • 12:15PM: Idea Pitches and Team Formation
  • 6:00PM: Dinner
  • 2:00AM Sunday: Late Night Snack
  • 10:00AM: Hacking Ends/Devpost Submissions Due
  • 10:15-11:00AM: First Round of Judging
  • 11:00AM: Brunch
  • 12:00PM: Project Demos Final Judging
  • 2:00PM: Closing Ceremony and Prizes

 

View full rules

Eligibility

HuskyHacks 1 is open to any Northeastern undergraduates regardless of major or college.

Requirements

Submissions will be due on Devpost by 10:00AM on Sunday April 3.

How to enter

Follow our application form at HuskyHacks.com to submit an application. 130 hackers will be admitted via a lottery system and they will need to present Husky ID to register at the event on April 2. 

Judges

No avatar 100

A Team of Hackathon Professionals

Judging Criteria

  • Technical Difficulty
    Is the hack technically interesting or difficult? Is it just some lipstick on an API, or were there real technical challenges to surmount? This is the most important criterion that your hack will be judged upon for the general prizes.
  • Originality
    Is the hack more than just another generic social/mobile/local app? Does it do something entirely novel, or at least take a fresh approach to an old problem?
  • Polish
    Is the hack usable in its current state? Is the user experience smooth? Does everything appear to work? Is it well designed?
  • Usefulness
    Is the hack practical? Is it something people would actually use? Does it fulfill a real need people have?