2016 was a great year for HackDartmouth. We had such a great time with all you hackers at our first three events that we just had to throw another one for hackers of all levels. Thus, we present to you: HackDartmouth’s HackDay II!

This time, we're narrowing our focus to Dartmouth students combining experiential learning with friendly competition in a closer, more intimate environment. We will be offering student-run workshops the evening before the event. Come familiarize yourself with the latest tech and API’s or learn to code from the area’s greatest hackers.

The day of the event features twelve hours of coding, swag, and amazing prizes! So mark your calendars for April 8th, 2017 with workshops the evening before. Check out our website for more the schedule and more details!

Eligibility

All hacks must be built at Dartmouth by registered and accepted participants.

Teams may include up to four members. Teams must consist of ONLY beginners to be eligible for beginner prizes. 

Requirements

A valid submission is a hack produced at HackDay from start to finish. Submissions must be made to DevPost by 9PM Sunday April 8th. Please include an accurate description and photos of the hack. 

Submissions must demonstrate significant effort (ie. no homework or "Hello World" projects) in order to be considered for prizes and Tiles.

Hackathon Sponsors

Prizes

$3,476 in prizes
Google Home
4 winners

Beats X
2 winners

Apple TV
1 winner

Amazon Echo Dot
6 winners

Chromecast
4 winners

Fire TV Stick
1 winner

Anker 10,000mAh Power Bank
2 winners

Tile
80 winners

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Tim Tregubov

Tim Tregubov
Technical Director of DALI Lab

Thomas Cormen

Thomas Cormen
Professor of Computer Science

Judging Criteria

  • Creativity
    How creative or innovative is the idea behind the project?
  • Viability
    How relevant is the project's use case to a real market?
  • Intuitiveness
    Is the overall UX intuitive? Does the flow make sense?
  • Value
    How quickly does the project's value become apparent upon initial use? Would it require documentation to use?
  • Feasibility
    Does it actually work? Could it scale?
  • Uniqueness
    How well does this project mashup different technologies?

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

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