Hack the change you wish to see in the world.

Hack the Change is a social impact Hackathon focusing on apps that solve problems related to international development and humanitarian aid Hack the Change seeks to create viable and sustainable technology-based solutions to challenges faced by developing countries. The event encourages people to look at international and local issues from a tech/engineering perspective, rather than a policy perspective. It thus provides an avenue to bring together developers, engineers, NGOs, and entrepreneurs to solve real world problems and make an immediate impact. Our event is one of the many growing projects in the field of information and communication technologies for development (ICT4D). This year will be the third annual Hack the Change event, and we are excited to see what results continue to come out of this exciting intersection of people.



View full rules

Eligibility

  • Hackers - Any undergraduate student currently attending university is welcome to participate. In order to be successful in a hackathon, students should have some background in computer science, although beginners are definitely welcome! We'll do our best to place you on a team with more experienced people you canlearn from, or you can come with more experienced friends
  • Mentors - We are always looking for professionals and other experienced coders interested in serving as mentors for students during the hackathon
  • Non-hackers - If you don't know how to code but are interested in what Hack the Change and the field of ICT4D are all about, feel free to come for the speakers and presentations at the beginning and end, or just to see what the hackathon is like!

Requirements

  • What to work on: The problem statement that is assigned to your team from our list, or a problem statement that fits within the scope of the event (see Rules).
  • Platforms: Anything goes, as long as it makes sense for the problem statement you are working on and for the organization/population who will be using it.

Judges

Ben Brockman

Ben Brockman
IDInsight

No avatar 100

Dani Bicknell
Penn Graduate School of Education

No avatar 100

Deepti Chittamuru
Penn Graduate School of Education

No avatar 100

Dhairya Pujara
Ycenter

No avatar 100

Fatima Zahra
Penn Graduate School of Education

Jordan Landis

Jordan Landis

No avatar 100

Mirko Visontai
Google

No avatar 100

Nathan Castillo
Penn Graduate School of Education

Ryan Villanueva
IBM

Judging Criteria

  • Completeness
    How fully does the product address the problem statement? How much of what was asked for was covered, or at least considered? How much progress seems to have been made?
  • Functionality & Quality of Code
    How well was the code written (bug-free, straightforward to use, etc.)? How well does the final product work?
  • Creativity & Innovation
    How creative is the solution? Does it take any new or innovative approaches to the task posed in the problem statement? Does it generate interesting ideas about future work on this topic?
  • Future Usability
    How well has the team set up this code to be used by the organization that submitted the problem statement? How easy will it be for an organization to use the project as is? How well has it been documented, how readable is the code, etc.?
  • Presentation
    How well did the team convey what their goals were, w they were trying to to do, what they ultimately achieved and didn’t achieve, and how they envision it being used?