Hacking for Sustainability

Each year Code2040 Fellows come together to leverage their talents and expertise to solve some of our society’s most pressing challenges. This year encourages fellows to position themselves as leaders in the fight for sustainability. We invite fellows to create solutions to help develop thriving Black and Latinx communities through the three pillars of sustainable development--social, environment, and economic. Sustainable development looks at these three pillars as the fundamental blocks to ensuring that as a society we meet the needs of the present without compromising resources for the future.

This site will be used for the 2 separate hackathons (SF/SV/PDX and NYC). Below is information on each hackathon. Please visit the separate websites for more information and agendas. 



Demo Day Location

Demo Day Time:

Person of Contact

West Coast (SF/SV/ PDX Fellows)

Twitter 355 Market Street, #900

San Francisco


Saturday, July 21st 10:00am- 3:30pm


Shellie Stamps: (she/ her) (e)shellie@code2040.org

 Alyshia Macaysa:(she/her) (e)alyshia@code2040.org

East Coast

(NYC Fellows Website)

Flatiron Schools 

11 Broadway, 2nd floor, New York, NY 10004



Saturday, July 21st EST 10:00am- 3:30pm



Hayley Beers: (she/ her) (e)hayley@code2040.org

Nia Mitchell: (she/her)





View full rules


Hack for Sustainabilty is open to all 2018 Code 2040 Fellows. 

If you have any questions please contact your site coordinator.


No avatar 100

Varies on location

Judging Criteria

  • Technology: 
    How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go "Wow"?
  • Design:
    Was there thought into the user experience? How well designed is the interface? For a website, this might be about how beautiful the CSS or graphics are. For a hardware project, it might be more about how good the human-computer interaction is.
  • Completion
    Does the hack work? Did the team achieve everything they wanted?
  • Learning:
    Did they try to learn something new? What kind of projects have they worked on before? If a team which always does virtual reality projects decides to switch up and try doing a mobile app instead, that exploration should be rewarded.