Team Formation

  • Your team may consist of up to four participants. All teams will be judged by the same standards, regardless of team size.
  • All team members must be registered participants of HackKU26, have checked in, and be present for the event.
  • If you do not have a team yet, don’t worry! There will be a team formation event after Opening Ceremony to find others to hack with. Additionally, there is also a team-building channel on the Discord to find teammates.

Competition Rules

  • All code for your project MUST be written during HackKU, between 9pm on April 17th and 9am on April 19th.
  • Your entire project must be written and created by only the participants of your team.
  • Your code must be made public on GitHub for judging purposes. We will use the GitHub to verify that both the above rules and deadlines of the competitions were followed. All teams may be subject to a code review.

Deadlines

  • 12:00 am on Sunday, April 19th - Devpost team registration deadline
  • 9:00 am on Sunday, April 19th - Final project submission deadline

Tracks, Challenges, & Prizes

  • There will be two main tracks at HackKU25: the General Track, and a Theme Track. (The theme of the Theme Track will be announced during the opening ceremony) Participants must choose ONE of these tracks to submit their project on, and will compete for the prizes associated with that chosen track.

  • There will also be prizes associated with various challenges and company sponsored tracks. Teams may choose to compete for as many or as few of these as they would like, regardless of which of the two main tracks they are competing on.

  • For more specifics, see below.

    Tracks, Challenges & Prizes

Submission & Judging

  • All projects will be submitted via Devpost.
  • Teams competing for prizes will give a short (5-minute), in-person demo of their project to judges.
  • All teams are encouraged to demo, even if your project is not complete. There is no downside to demoing your project! This is a chance to show off what you accomplished and learned during HackKU.
  • Judging decisions will be confidentially handled by the judges assigned to your project and will be based on your Github code, Devpost submission, and your In-Person Demo.

 

Finally, make sure you've read and agreed to the MLH Code of Conduct