we're back and ready to hack!! qwer hacks at ucla is major league hacking's first LGBTQIA+ hackathon and aims to increase the visibility of and celebrate the queer and trans community in STEM, as well as engage and bring together queer individuals and allies through empowering tech talks, technical and community building workshops, and the development of innovative products meant to help underrepresented groups!
this year, in a space that celebrates identity, intersectionality, and community, we'd like you to create a future you want to see. we could live in a world where Black trans lives not only matter, but thrive, non-binary individuals have access to inclusive and respectful healthcare, public policies work to make life easier for marginalized groups, our education system celebrates and uplifts underrepresented voices, and our diverse identities are reflected both on our screens and behind the scenes.
$1,875 in prizes
Healthcare Track (3)
First place: Fitbit HR
Second place: Headspace subscription
Third place: Yoga mats
Education Track (3)
First place: Digital subscription to Masterclass
Second place: Leetcode or audible subscription
Third place: Portable Chargers
Entertainment Track (3)
First place: Projector
Second place: Polaroid
Third place: Speaker
Public Policy Track (3)
First place: Wireless chargers + $200 donation to charity of choice
Second place: Wireless chargers + $150 donation to charity of choice
Third place: Wireless chargers + $100 donation to charity of choice
Best Use of Google Cloud
Google Branded Parkland Academy Backpack
Best Domain Registered with Domain.com
PowerSquare Qi Wireless Phone Charger & Domain.com Backpack
Best Hardware Hack Sponsored by Digi-Key
Grove Beginner Kits
Submitting to this hackathon could earn you:
Anyone who is ...
a) above 18
b) attending our hackathon
c) enrolled in a postsecondary academic institution
can submit their projects to Devpost!
QWER Hacks Judging Guidelines
the spirit of the competition
Remember that hackathons are like marathons. Some people go to compete but most people take part to learn new skills and have fun!
After hacking finishes, teams will record a video that demos what they have built. It is totally okay (and even expected) that your hack is incomplete and contains bugs. Completion is only a minor part of the judging criteria (10% of your total score). Demoing is a chance to share with others what you have learned, what you tried to build, and your motivation—that's what hacking's truly about!
This year, to better accommodate those with internet issues or who will have difficulties presenting projects live, hackers will be submitting 2-minute prerecorded videos that judges will then view and discuss together. Your face does not need to be shown in the video, if you feel uncomfortable doing so. To be fair to all hackers, only the first 2 minutes of longer videos will be watched by judges. In other words, there will NOT be any live Q&A time between the judges and the teams. This may cause some hackers to worry that they have not incorporated all the relevant, or evaluated, components of their hack in their video. Have no fear! Below, we provide a checklist of what questions to answer in your demo video to succeed.
- Did the hack address a clearly defined problem space that benefited from this development? Did your team explore a new application domain (e.g. conservation, education, etc.) with which you weren’t previously familiar?
- How relevant and creative was your project in solving an issue within the track you chose to follow?
- What technologies did your team leverage? Did your team try to learn a new technology?
- Was your team methodical and collaborative in your hacking process? Did your team overcome any obstacles or major goal changes during hacking?
- Did your team put thought into the user experience? What accessibility considerations did you make?
Please keep in mind that the usage of fancy vocabulary, and especially your English-speaking abilities, will have absolutely no influence on your score. However, you will be evaluated on your team’s summary and showcasing of your project, which should be adequately explained and easy to follow.
how technologically impressive is the hack? did the hack address a clearly defined problem space?
did the team put thought into user experience? are there explicit attempts to improve the hack's accessibility?
does the hack successfully work in the way the team says it should?
did the team try a new technology? did they overcome any major obstacles while hacking?
how relevant + important was the project focus to the team's chosen track?
communication + presentation
how well does the team explain their technical ideas and motivation from a high-level, intuitive perspective?