The spirit of the competition

Hackathons are like marathons. Some people go to compete but most people take part to better themselves and have fun. Whatever the reason is that you're at a hackathon, make sure you're upholding the hacker spirit by collaborating with other teams, helping beginners, and having fun.

HackNYU Competition Rules:

  1. Maximum team size of 5 participants.
    1. Must be made up exclusively of participants.
    2. Team members should be present and checked in to the event.
  2. All the implementation of the project must be completed at the event by the team. Ideas can be come up in advance.
    1. Ideas do not have to be original, but the implementation must be original.
    2. Open source libraries, frameworks and starting points are allowed, but teams must disclose what they created at the event, and what was already made (make sure to respect any licenses). Judges will only consider new additions made during the hackathon.
    3. We have a strict no plagiarism policy. We may request a copy of the code to review (we will never steal your work).
  3. Teams can receive help from mentors, sponsors, and other participants; We highly encourage this!
    1. If you had any significant outside help or resources, please disclose their areas of contribution. It’s okay to get a lot of help! We judge projects in the context of your abilities, and how you made use of the resources available.
  4. Teams and participants can be disqualified and/or asked to leave at the organizers' discretion. Reasons might include but are not limited to: breaking the Competition Rules, violating the Code of Conduct, or engaging in any other untolerated behaviours. Use common sense and treat your fellow hackers with respect.

Judging + Expo:

Hacking will officially end at all locations by Sunday, March 25, at 12PM ET (NYC time). Teams need to submit to DevPost by 12PM.

NYC-based teams will pitch their projects at our hacker expo to judges for a chance to win (Shanghai- and Abu Dhabi-based teams can submit video demos along with their Devposts). Teams have a total of 4 minutes to interact with the judges for their track to pitch and answer questions. We recommend spending 1 minute on pitching and demo and the remaining 3 on answering questions the judges may have — keeping in mind the judging criteria (found on this page).

You are strongly encouraged to present a demo during your pitch of what you have built, even if your hack is broken or incomplete. If you can, refrain from using slides. Instead, show a live or interactive demo of your project!

You can also talk about what challenges you faced and what you learned when making your project. Demoing and pitching is a chance to share with others what you learned and tried to build — that’s what hacking’s all about! For being courageous enough to demo, you’ll receive a special MLH “I Demoed” sticker.