Cutie Hack 2026

about this event

Cutie Hack is UC Riverside's 12 hour, beginner-friendly hackathon organized by the Association for Computing Machinery (ACM) at UCR, bringing together students from all backgrounds to learn skills, build projects, and create innovative solutions.

Cutie Hack's goal is to create a place where students can build with the freedom of their creativity. Established for students by students, it has since become a community space and a place where students can turn their ideas into impactful innovations.

Throughout November 21, 2026, Cutie Hack provides builders of all years, majors, and skill levels the chance to develop projects, present to a panel of industry judges, and compete for tracks and prizes!

To be considered for the tracks and prizes: 1) ALL PARTICIPANTS are REQUIRED to register and be accepted through the website cutiehack.com (registration info to be released). 2) The GitHub repo link must be submitted (to our Devpost) before hacking ends. 3) Majority of your team must be in person for judging. The distribution provided is the minimum amount of people from your team that is required to be in person for judging: Teams of 1: 1 person; Teams of 2: 2 people; Teams of 3: 2 people; Teams of 4: 3 people.

Connect with us: Core links include cutiehack.com (website), cutiehack@gmail.com (email) and all links. Socials include Instagram, Discord, and LinkedIn. More opportunities: acmucr.carrd.co (ACM) and linktr.ee/citrushack (Citrus Hack - our sibling hackathon).

Get started by following these steps: 1) Register: All participants must register (and be accepted) at cutiehack.com (through our participant application) and on our Devpost. 2) Form a Team: Teams can have 1 to 4 members. 3) Plan Your Project: This year there are 5+ tracks (see submission requirements). You and your team are free to build your project around these tracks, but it is highly encouraged to plan it around this year's theme - dreams x Alice in Wonderland! 4) Build: Start coding once hacking kicks off on November 21 at TBA. All projects must be started and completed during the 12 hour period. 5) Use GitHub: Your code must be hosted on GitHub. Ensure that all commits are time stamped during the hackathon window to qualify for judging and to be considered for the tracks. 6) Submit Your Project: Turn in your project through Devpost by the deadline. 7) Judging: Majority of your team must be present in person to pitch your project to judges on November 21 at TBA. Be ready to present your project and answer questions from judges.

when