Spring forward with us at Princeton University's premier 36-hour hackathon.

For 36 hours on March 31st - April 2nd, HackPrinceton will bring together 500 developers and designers from across the country to create incredible software and hardware projects.

At HackPrinceton, you’ll meet fellow hackers, learn new technologies, and hone your skills alongside seasoned mentors. We'll have free food, swag, workshops, mentorship, prizes, games, and more. Come with or without a team or an idea, and we'll inspire you 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 2nd. 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

No avatar 100

Vlad Sheykhet
Director at Vitech

No avatar 100

Vishal Srivastava
Head of Data Science at Clarity Money

No avatar 100

Bill Reynolds
CTO and Co-Founder of Promia

No avatar 100

Lena Henke
Software Engineer at Floored

No avatar 100

Jon Beyer
Software Developer at White Goose Tech

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?