Hack for 24 hours

Welcome to NTU's first of its kind hackathon, a competition that lasts for 24 hours round the clock. The Graduate Student Club of the School of Computer Science and Engineering (SCSE-GSC) proudly announces the inaugural grand edition of 24Hackathon in collaboration with NTU-GSA.
This is a campus wide hackathon to be held on 15-16 February 2020 (Sat-Sun) and we invite participation from the whole of NTU student community. We present to you one of the rare opportunities for collaboration of Undergraduate and Postgraduate students in NTU to exchange skills, ideas and connect.
The competition is to develop creative and innovative solutions focused on the themes "Gender Equality", "Sustainable cities and communities" and "Climate Action". Teams with the most innovative and scalable business solutions can win exciting prizes.
This is a team event and registrations are in teams of three. You can either sign up as a team or as an individual and we shall help you find a team in the latter case.

View full rules


$600 in prizes


Devpost Achievements

Submitting to this hackathon could earn you:


Students of all levels in NTU, Singapore can sign up for the event. This is a great opportunity for those aiming to learn big and pursue a career in business or information technology. Admission is free. Just register online and wait for confirmation. We'll provide food, caffeine, Wi-Fi and a place for you to hack for the entire duration of the event.


Submission Guidelines:

Each team, identifiable by a team name, will have to furnish the following upon completion of the hackathon. Each submission must have three components, namely the platform, the code base and the documentation. Each of these three components are elaborated below. Participants should note that failure of providing any component will lead to disqualification.


Beginning of the Hackathon (Saturday 1pm):

Formal problem statement including definition of the target and brief description and outline of the approach. This is like an abstract and must not me more than 200 words.

End of the Hackathon (Sunday 12pm):

Every participating team is expected to provide their final submission in three sub-folders as described below. The format for submission is to be strictly adhered to.

  • The platform, which may include (one or multiple), but is not limited to:
    • A dashboard
    • An interactive website
    • An app
    • YouTube link for video (in case of some related live demo)
  • Code base (will not be retained or used after evaluation):
    • To be uploaded on GitHub with necessary ReadMe file
    • To be appropriately commented along and uploaded for code-review and evaluation
  • Documentation
    • A short presentation (up to 5 slides) describing the submission, touching upon:
      • Approach
      • Outline of methods
      • Impact and scope
    • One/two-page statement mentioning:
      • The development tools used to build the project
      • SDKs used in the project
      • APIs used in the project
      • Any assets or data repositories used in the project
      • Any libraries used in the project
      • Any components not created at the hackathon

Presentation for Judges’ Evaluation:

After the hackathon is over, all the teams will need to present their work in front of the panel of judges final evaluation. The code will be separately be reviewed by the Code Review team. Each team will be allotted a maximum of five minutes. The presentation will be as follows.

  • Pitch: This is a one-two minute talk to be delivered by one member of each team, using the previously submitted deck of slides.
  • Demo/App/Dashboard/website review: This is a one-two minute demonstration of the app or dashboard or the likes developed by the team during the hackathon.
  • Q&A: The judges, may choose to ask questions and seek clarifications regarding the presentation of the teams, for about a minute, should they feel the need to.




Judging Criteria

  • Relevance:
    Does the proposed solution address the particular problem in the right way?
  • User experience, Design & Polish:
    Does the user feel immersed and transported to the context of the problem at hand? How well designed and polished is it?
  • Innovation & Originality of Idea:
    Does the idea or project show creative thinking? Does it stand out from the crowd? Is your idea unique and original? Are there similar mechanics, methods or experiences already out there?
  • Code & Technical Merit:
    What is the quality of your code? How often did the team commit? Was there a technical challenge that was overcome?
  • Artwork/Multimedia Integration:
    Were the audio/visual effects created at the Hack? Did it add to the overall experience in a novel way?
  • Judges’ Discretion (bonus):
    Not necessary, optional for exceptional cases. Was it exceptionally fun, insightful or impactful on the judges?


  • Machine Learning/ AI
  • Social Good