About the challenge
Engineering students at the University of Waterloo engage in a rigorous, collaborative, and innovation-driven environment. They navigate courses, design projects, labs, co-op terms, team-based activities, and campus-wide services throughout the academic year. While these experiences are foundational to the Faculty’s commitment to experiential learning, they also involve a variety of tools, processes, and systems that students interact with on a daily basis.
As Waterloo Engineering continues to evolve, opportunities arise to streamline, enhance, or reimagine aspects of student life through software. These improvements can take many forms: making information easier to access, improving communication, supporting academic success, simplifying logistics, increasing inclusivity, or helping students balance academic, professional, and personal responsibilities.
Your challenge is to design and build a software tool, application, or system that meaningfully improves some aspect of student life for engineering students at the University of Waterloo. Your solution should address a clear need or opportunity, whether it relates to academics, organization, collaboration, wellness, productivity, or campus engagement. Solutions must be primarily software-driven, though teams may incorporate hardware as a supporting element where appropriate.
Teams may consider:
-
How do engineering students interact with their academic, co-op, and extracurricular environments?
-
Where do friction points or inefficiencies naturally occur?
-
How can thoughtful software design reduce complexity or enhance the student experience?
-
What solution could have practical, lasting value for engineering students?
Your project does not need to solve every problem. Instead, it should focus on one specific area, delivering a meaningful, usable solution that demonstrates creativity, strong engineering design, and relevance to the Waterloo Engineering community.
Unique solutions are awarded.
Requirements
What to Submit
You may only present/demo the material you have submitted. Presenting non-submitted material will result in disqualification.
Final Project Submission
- A working version of the software solution (e.g., deployed app, runnable project, or executable demo).
- Source code submitted via a shared repository or compressed file.
Project Documentation
- A README or document explaining:
- The problem being solved
- Key features and functionality
- Technologies used
- Instructions for running or accessing the project
- Citations
Optional Presentation Slides
- A slide deck summarizing the project, suitable for judging and audience presentation may be included but are not required..
Optional Supplementary Materials
- Diagrams, design sketches, or short demo videos may be included but are not required.
Prizes
First Place - Per Person On Team
Second Place - Per Person On Team
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
To Be Announced
Judging Criteria
-
See Competitor Package
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.