WildHacks is Northwestern Unversity's annual 36-hour hackathon.

Let's get lost together

WildHacks is Northwestern University's annual 36 hour hackathon.

View full rules

Prizes

$5,500 in prizes

WildHacks 2017 1st Place Prize

$2000

WildHacks 2017 2nd Place Prize

$1500

WildHacks 2017 3rd Place Prize

$1000

Best use of Cisco API (2)

Canakit Raspberry Pi and in touch screen displays

Best IoT Hack Using a Qualcomm Device

Qualcomm DragonBoard 410c + power source

Amazon Web Services - Best Use of AWS

$250 Amazon Web Services Credit

Best Domain Name from Domain.com

Raspberry Pi & PiHut Essential Kit

1517 Fund Scholarship

Judges

Marisa Gomez

Marisa Gomez
Coach, MLH

Michael Marasco

Michael Marasco
Director, Farley Center of Entrepreneurship and Innovation

Brad Boven

Brad Boven
VP of Engineering, Uptake

Zack Johnson

Zack Johnson
VP of Business Development, Visier Inc.

Rebecca Miller-Webster

Rebecca Miller-Webster
Chief Practice Officer and Director of Engineering, DevMynd

Bridget Hardy

Bridget Hardy
Uptake

Neal Sales-Griffin

Neal Sales-Griffin
CEO, Starter League

Mark Bertrand

Mark Bertrand
Senior Product Manager - Growth, Sprout Social, Inc.

Jake Albaugh

Jake Albaugh
Engineer, Codepen

Trevor Austin

Trevor Austin
Director of Engineering, Civis Analytics

Matt DeNapoli

Matt DeNapoli
DevNet Systems Engineer, Cisco Systems

Mert Iseri

Mert Iseri
CEO, SwipeSense

Zeke Linares

Zeke Linares
Contrary Capital

Ravi Bakhai

Ravi Bakhai
Contrary Capital

Leslie Jones Dove

Leslie Jones Dove
Contrary Capital

Daniel Bingyou

Daniel Bingyou
Contrary Capital

Andy Kaminski

Andy Kaminski
Senior Developer, Ford

Judging Criteria

  • Originality
    The hack should be unique and interesting. This can range from a new spin on a known idea to completely outlandish ideas. The hack should be something damn cool you’ve never seen before.
  • Utility
    Doesn't have to be business-ready, but should have the potential to be a useful in everyday life. Should also be intuitive and easy to use
  • Technical Complexity
    The hack should be technically impressive for 36 hour project. They should have code and a functioning prototype. Anything from frameworks, apis, algorithms to interesting languages can add to the technical difficulty of the project.
  • Polish/Design
    Should look or work beautifully. The closer it looks and feels to a professional-grade application, the better.