WildHacks is Northwestern's overnight hackathon taking place in-person April 5-7 2024. As Northwestern's largest hackathon, WildHacks is an opportunity for students to learn programming skills and develop a final project in a collaborative and inclusive environment. Through workshops, mentorship, and prizes, WildHacks aims to be an inclusive event that welcomes students of all skill levels, majors, and backgrounds.

Visit https://www.wildhacks.net for more information.

If you're a participant, https://guide.wildhacks.net has all the information you'll need.

Hackathon Sponsors

Prizes

$13,659 in prizes
Grand Prize - First Place Overall
1 winner

Grand Prize - Second Place Overall
1 winner

Grand Prize - Third Place Overall
1 winner

Track Prize - Urban Planning
1 winner

Track Prize - Productivity
1 winner

Track Prize - Wellness
1 winner

Additional Prize - Best Design
1 winner

Additional Prize - Best Technology
1 winner

Challenge - Crowd Favorite
1 winner

[MLH] Most Creative Adobe Express Add-On
1 winner

[MLH] Best Domain Name from GoDaddy Registry
1 winner

[MLH] Best DEI Hack sponsored by Fidelity
1 winner

[MLH] Best Use of Starknet
1 winner

[MLH] Best Use of Kintone
1 winner

[MLH] Best Use of AI in Education
1 winner

[Capital One] Best Financial Hack
1 winner

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Joe Hummel

Joe Hummel
Professor of Instruction in Computer Science at Northwestern University

Sruti Bhagavatula

Sruti Bhagavatula
Assistant Professor of Instruction in Computer Science at Northwestern University

Lydia Tse

Lydia Tse
Software Engineer at Google; Adjunct Lecturer in Computer Science at Northwestern University

Brylan Donaldson

Brylan Donaldson
Associate Director at The Garage at Northwestern

Andrew Seto

Andrew Seto
Strategy Analyst at Accenture

Ronit Basu

Ronit Basu
Software Engineer at Domino Data Lab

Ian Wallace

Ian Wallace
Strategy Analyst at Accenture

Sahar Siddiqui

Sahar Siddiqui
Strategy Analyst at Accenture

Judging Criteria

  • Technical Complexity
    The hack should be technically impressive for a 24-hour project. They should have code and a functioning demo. Anything from frameworks, APIs, algorithms, & more to interesting languages can add to the technical difficulty of the project.
  • Usefulness
    The hack doesn't have to be business-ready but should have the potential to be useful in everyday life. It should also be intuitive and easy to use.
  • 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.
  • Design
    The hack should look and work beautifully. The closer it looks and feels to a professional-grade application, the better.
  • Presentation
    The demo video should be engaging and show how the project would be used. It should also explain the mission and intended outcome behind the project.

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.