Hack&Roll is an annual 24-­hour Hackathon organized by NUS Hackers, a student­-run organization committed to spreading hacker culture. Designed to grow and strengthen the local hacking community, Hack&Roll 2014 will be an open platform for hackers to gather, collaborate, and build new things. In the spirit of hacking, we celebrate not just the most useful products, but also reward projects that are "awesome but useless" and for factors such as sheer overall coolness.



  1. This event is open only to:
    • Students of all levels in any educational institution in Singapore (yes, exchange students count as well!)
    • Anyone waiting entry into an educational institution - e.g. NSFs, PhD candidates, etc.
  2. A team can have between 1 and 4 members.


To be confirmed.

Hackathon Sponsors


First Prize

Per team member: 1 Pebble Watch, 1 Razer Naga, 1 Razer BlackWidow Tournament Edition, 1 Razer Goliathus Control, 1 Protag Elite and a 1-year SimplerCloud XS servelet subscription

Second Prize

Per team member: 1 Leap Motion, 1 Razer Orochi, 1 Razer Goliathus Speed, 1 Mechanical Keyboard and a 1-year SimplerCloud XS servelet subscription

Third Prize

Per team member: 1 Razer Abyssus, 1 Mechanical Keyboard and a 1-year SimplerCloud XS servelet subscription

The Best Freshmen/Non-Tertiary Award

Per team member: 1 Raspberry Pi

The Popular Choice Award

Per team member: 1 Arduino Leonardo

Devpost Achievements

Submitting to this hackathon could earn you:


Lee Wee Sun

Lee Wee Sun

Kan Min Yen

Kan Min Yen

Tan Kiat Chuan

Tan Kiat Chuan

Judging Criteria

  • Creativity (40%)
    Essentially, this is how new or innovative aspects of the team’s product are. This can be anything from the entire idea behind the product to the specific implementation of certain features: a product that isn’t novel in itself could still have a new and
  • Technical Accomplishment (30%)
    How well is the product built, from a technical perspective? Teams that demonstrate and/or explain the advantages of their chosen stack over the alternatives should do better in this area. Successfully executed complexity should be considered as well: a t
  • Polish (20%)
    Does the product look like something that could be launched right now? This category is mainly centred around how complete the product seems, considering the 24-hour time constraint. Aesthetics and functional completeness are the two main things to look o
  • Usefulness (10%)
    Does the project attempt to solve a meaningful problem? Most projects built at hackathons don’t enjoy the luxury of multiple iterations based on actual feedback from users. It’s hard to say if a project built in 24 hours can adequately solve the problem i

Tell your friends

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.