Learn, Build, Share. The finale of the Spring 2016 student hackathon season.

Welcome to MLH Prime.

Watch live video from MLH on www.twitch.tv

Are you ready for our season finale hackathon? We’ve invited our most respected community members from the past season to hack incredible projects. We can’t wait to see what you’ll build

All hacks and hackers at MLH Prime must abide by the MLH Code of Conduct.

View full rules

Eligibility

Hackers must be in school/college/university or have graduated in the last year to be eligible to win. MLH staff and advisors are not eligible to compete for prizes, but may enter hacks in the event.

Requirements

Hacks must be awesome, creative, and built on site at the event. All hacks must adhere to the MLH Code of Conduct to be eligible for presentation.

 

Note: There will typically only be up to 5 prizes per team. The rules allow for larger teams, but prizes (especially sponsor prizes) may not be available for every team member in this case.

How to enter

Any hacker who has participated in a Major League Hacking (MLH) event in the past year is eligible for MLH Prime: Spring Finale 2016. The invites are hand selected by MLH Staff around a few criteria, including number of events attended.

Judges

Chris Kennedy

Chris Kennedy
Design Lead @ WeWork

Julia Neznanova

Julia Neznanova
Director @ Friends of Ebay

Adrian Catalan

Adrian Catalan
Innovation Lab Lead at GalileoU

Anat Gilboa

Anat Gilboa
Software Engineer at AmEx

Kaylyn Gibilterra

Kaylyn Gibilterra
Senior Software Engineer at Capital One Labs

Judging Criteria

  • Technology
    How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go "Wow"?
  • Design
    Did the team put thought into the user experience? How well designed is the interface? For a website, this might be about how beautiful the CSS or graphics are. For a hardware project, it might be more about how good the human-computer interaction is.
  • Completion
    Does the hack work? Did the team achieve everything they wanted?
  • Learning
    Did the team stretch themselves? Did they try to learn something new? What kind of projects have they worked on before? If a team which always does VR projects decides to switch up and try doing a mobile app instead, that exploration should be rewarded.