An all-female hackathon organized by the Women in Technology Society!
SheHacks is a 12 hour, student-run hackathon open to all female-identifying individuals. If you like to code, hack, and design, or simply want to learn more about technology, come to Western University on March 25th for our hackathon at North Campus Building! We welcome you into our community of women in tech.
We welcome participants from all over Canada, with a particular emphasis on Western University, Waterloo University, Laurier University, McMaster University, York University, and University of Toronto!
Our event is focused on encouraging women in technology. As such, SheHacks features all-female participation, from the attendees, mentors, volunteers, to the judges!
When submitting your hack, please include a good representation of your work. This could be a link to your code (Github, bitbucket), screenshots of the project or a video walking through how your project works.
Projects must be submitted by 9PM on March 25, 2018. Make sure to choose the prize categories you want to be judged on. We encourage you to pick multiple prize categories, even if your project is incomplete. This hackathon is focused on being a learning experience; we'd love to see what you've learned!
How to enter
SheHacks registration is now full! We're excited to welcome our 150 confirmed attendees to hack with us on March 25th, 2018. We do currently have a waitlist going on, which you can register for on www.shehacks.ca
Overall Criteria for All Categories - Technology
Technology: How effective was the technology used to achieve the group's overall goals? How difficult was the technical problem chosen?
Overall Criteria for All Categories - Design
Design: Is the user interface clear and easy to use? Does it look aesthetically pleasing or professional-looking? Does the workflow make sense, and is it intuitive to use?
Overall Criteria for All Categories - Learning
Learning: Did the team partner with new people and collaborate together? Did the team learn and try something new with the hack? Were they able to work on a different category or platform for the project?
Overall Criteria for All Categories - Quality
Quality: How well does the hack work from start to finish? Did the team scope the features of the hack well, given the time frame of the hacking period? How well were the features implemented for the project, in terms of the working condition?
Overall Criteria for All Categories – Impact
Impact: Does the hack tackle an existing problem in the world today? Does the hack improve on current solution methods or technologies?
Best Use of API
Does the project incorporate StdLib's API in a creative manner?
Is the team able to clearly explain their idea and what the hack does? How well did the team present their hack and respond to questions? Does the hack seem like something people would want to buy and use outside of the hackathon?
Best Use of Data Analytics
Is the hack a creative use of technology? Does it make use of data in a creative way?
Best Use of Blockchain
Does the project incorporate some form of blockchain technology? Does the hack provide a solution to a problem?
Best Almost Hack
How close is the prototype to a finished product? Do most of the functionalities and user interface items work? Did the team achieve their overall goals with the hack? How will the team improve on the current prototype for the future?
Best Solo Hacker
Was the hacker able to complete the project on their own? Did the hacker present their idea clearly?
Best Overall Hack
How well did the team perform from all of the above criteria?