HackPrinceton Spring 2018. March 30 - April 1.

600 developers and designers from across the country to create incredible software and hardware projects. For 36 hours this spring, from March 30 to April 1, we will provide a warm and collaborative environment for you to build out brilliant, innovative, and impactful ideas.

At HackPrinceton, you'll meet fellow hackers, learn new technologies, and work alongside seasoned mentors. We'll have free food, swag, workshops, lecture series, mentorship, prizes, game, free food, and more. Don't have a team, or even an idea? Don't worry! We'll give you the tools to build something incredible.

View full rules

Eligibility

  • All hacks must be built by accepted, confirmed, and checked-in HackPrinceton attendees. (This includes registered and checked-in Princeton students.)
  • Teams must consist of no more than four members.
  • Hackers must be a current student, or have left school within the past year, and present enrollment identification (i.e. student ID) to a HackPrinceton organizer if asked.
  • Due to university liability requirements, individuals must be at least 18 years old.

Requirements

Submissions are due on Devpost by 9:00 AM on Sunday, April 1. After you submit, you can edit your submission until the deadline, so you are encouraged to begin your submission early. We are not able to accommodate late submissions.

You must include videos, photos, or screenshots of the working product and a link to the source code (GitHub, etc.) of your project.

Judges

Irina Krechmer

Irina Krechmer
VP of Engineering at XO Group Inc.

Meng Shui

Meng Shui
Director of Design at THINX

Daniel Taboada

Daniel Taboada
CEO of Gold Media Tech

Becky Case

Becky Case
VP of Engineering at Birchbox

Geoff Cook

Geoff Cook
CEO of The Meet Group

Judging Criteria

  • Originality
    How original is the idea? Is it simply a repackaging of a previous project or is it something that has never been done before? Projects can also blend two concepts together in a refreshing new way.
  • Design
    Is the project something that looks and feels polished? Is the user experience and interface smooth and well-designed?
  • Technical Difficulty
    Does the project take on technical challenges? What parts of the project did your team invent, and how did you build upon existing tools and technologies?
  • Enjoyment
    Is the project zany, interesting or just plain amusing? Will it bring a smile to the face of those who see it, whether they are adults, teenagers or little kids?
  • Usefulness
    Can this hack be used in real life to better somebody's life? Is it enough to justify people wanting to use it?
  • Other
    Did the team members meet entirely at the hackathon? Did the team overcome any significant obstacles? Is the hack ambitious? Does the hack have any "wow" factors? Was the pitch particularly effective and memorable?