Connect, Build, and Empower organizations to change lives across the world.

At Opportunity Hack, you can network, share ideas, and build solutions that enable impact and social innovation!

About the challenge

For Opportunity Hack 2022, as we continue to scale our global impact, it's important for us to easily conduct hackathons and continually deliver impact to nonprofits, so this year all of our projects will involve scaling ohack.dev.

This is the first time we've asked hackers to only focus on our nonprofit, instead of others.  We need more investment in our internal system before we feel comfortable scaling our existing process we started in 2013.

In-Person: Tempe, Arizona @ ASU

Want to join the hackathon in-person? We've been able to secure ECG101 on ASU Tempe Campus with limited seats: Please RSVP here. RSVP by December 9th at 5pm Arizona Time.  Only people who RSVP can attend.

ASU Tempe Arizona Parking Options

Tax Writeoff: If you're traveling to support us, you can typically deduct this from your taxes since we are a 501c3.  If you'd prefer to be reimbursed for your parking costs, please send us a DM/email/Slack.

 

Get started

1. Head over to ohack.dev and Opportunity Hack Inc. to see the projects and code you'll be working on.  You can also see a similar view on our GitHub Issues Page (incase ohack.dev goes down during the hackathon).

2. Share ohack.dev, our social media posts and fundraisers, for our hackathon and help us gather donations!  The more donations we receive, the more our prize money will increase.

3. After you register on DevPost, you'll be given a link to join our Slack which is where all of our hackathon collaboration happens.

4. Review the code! Frontend is React and Backend is Python - these are the primary code repos that should be forked and modified during the hackathon.  

 

Are you looking to help out in other ways?

Mentors: Sign up here (read more about hackathon mentorship here)

Judges: We are not asking for judges this year - trusted advisors to Opportunity Hack will be our judgdes

 

Schedule

Saturday 12/10

9am PST / 10am MST (Arizona): Doors open for checkin at ASU Tempe (for those with an in-person RSVP).

9:30am PST: Hackathon kickoff via livestream

10am: Hackathon officially starts

11am PST / Noon MST (Arizona): Lunch is served

12pm PST: Everyone must be registered in DevPost, signed into Slack, and team formation is completed.

1pm PST: Snacks served (in Arizona)

4pm PST / 5pm MST (Arizona): Dinner served

5pm PST: Arizona location closes for the night, we'll move everything to online and will re-group with you in the morning.

We think that these off-hours are important for folks to regroup, unwind, and recharge.  You are encouraged to hack through the night if you want, only if this is possible with your schedule.

Sunday 12/11

9am PST / 10am MST (Arizona): Doors open for checkin at ASU Tempe (for those with an in-person RSVP).

9:30am PST: Day 2 Hackathon kickoff via livestream

10am PST: In-person Hackathon officially restarts in Arizona

11am PST / Noon MST (Arizona): Lunch is served

2pm PST: Demo videos should be completed and added to DevPost projects

3pm PST: All code must be committed to GitHub fork.  Update DevPost submission with link to GitHub code fork.

4pm PST / 5pm MST (Arizona): Dinner served

5pm PST: Official end of the hackathon: All project submissions (DevPost, GitHub, Demo Video) will be locked at this time. Arizona location closes for the night.

To normalize between in-person and online, we will review all videos submitted async over the next 24 hours.

Winning teams will be announced via livestream (similar to 2020).

Monday at 12:30pm PST: Winners announced via live stream

 

Requirements

What to Build

1. Teams must be between 2 and 5 people - all team members must either have committed code or worked on your video submission since the start of the hackathon

2. Winners must have a PayPal account with the account in good standing in order to receive the prize

 

What to Submit

1. You must have all code checked into GitHub as a fork for frontend and backend code repos

2. You must provide a video demo of your work. Video must be less than 4 minutes long. It should include a brief intro (about 20 seconds), a discussion on the problem (~40 seconds), how you solved the problem (~2 minute), and how you met the judging criteria (~1 minute).

 

Hackathon Sponsors

Prizes

$1,750 in prizes

1st Place

$1,000 prize to split amongst the team.

Since you likely won't have fully completed the project during the hackathon, you will be able to fundraise additional prize money to reward your team when you complete your project (usually this happens by March).

Fundraise using this donation link: http://tiny.cc/ohack22-completionprize 100% of the proceeds will be rewarded when the team completes the project.

2nd Place

$500 prize to split amongst the team.

Since you likely won't have fully completed the project during the hackathon, you will be able to fundraise additional prize money to reward your team when you complete your project (usually this happens by March).

Fundraise using this donation link: http://tiny.cc/ohack22-completionprize 100% of the proceeds will be rewarded when the team completes the project.

3rd Place

$250 prize to split amongst the team.

Since you likely won't have fully completed the project during the hackathon, you will be able to fundraise additional prize money to reward your team when you complete your project (usually this happens by March).

Fundraise using this donation link: http://tiny.cc/ohack22-completionprize 100% of the proceeds will be rewarded when the team completes the project.

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Greg

Jot

Jot

Nicolle

Gina

Bryon

Judging Criteria

  • Scope of Solution
    (10pts) How big an impact will your solution have on the community? 50% Solves 100% of the solution 50% Complexity of problem solved
  • Documentation
    (10pts) Good documentation on how to use and setup their system 50% Code and/or UX is well documented so that anyone can understand the solution by reading 50% Simple and easy to understand solution, easy to navigate
  • Polish
    (20pts) How much work is left? 100% No work remaining, this is ready to ship
  • Security
    (10pts) Did you consider security? 50% No security holes that would allow for data extraction - leverages existing Auth0 foundation 50% Role based security implemented

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.