Sponsored by
Run by
Collaborating with
About
Cam Hack is a 32 hour hackathon for the innovative minds at the University of Cambridge. Over an action-packed weekend, students come together to design and build technology projects from the ground up. We welcome participants ranging from curious beginners to seasoned coders. Expect plenty of free stash, food, and mini-events throughout this hackathon. Over £1000 worth of prizes are to be won!
Schedule
Saturday 2nd November
- 10:00 Opening ceremony
- 10:45 Hacking begins!
- 13:00–15:00 Lunch + Sponsor merch + Registration
- 17:00–19:00 Game night
- 19:00–20:00 Dinner
Sunday 3rd November
- 09:00–12:00 Breakfast
- 13:00–15:00 Lunch + Sponsor merch
- 18:00 Hacking ends!
- 18:00–19:00 Dinner
- 19:00 Judging begins
- 20:45 Finalist presentations
- 21:30 Awards ceremony
Rules
Entry
- The maximum team size is 4. Any bigger, and we might have to split you up. Solo participation is allowed, but hacking is better with other people!
- Due to departmental rules, participants must be students at the University of Cambridge.
House rules
- Please do not bring food into the Intel lab! All food must stay downstairs in the street. 🍕
- You must not bring or consume alcohol at the hackathon.
- We don't recommend it, but you can stay overnight in the lab if you want. 😴
- All participants must follow our Code of Conduct.
Submission
- All work on projects must be done at the hackathon. Using existing open source code is allowed if credited, but the project should be substantially new.
- Working on a project and open sourcing it for the sole purpose of using the code in the hackathon is against the spirit of the rules and is not allowed.
- AI assistants (Copilot, ChatGPT, etc.) are allowed when writing code, but don't go overboard. For example, using AI assistants as a tool to help you code is fine, but asking one to generate a whole website or the core logic of your application is not allowed. Images generated by external (not part of your project) AI models must be credited, but such use is discouraged.
- After hacking finishes, representatives for each track will go around to look at each demo. You are free to look at other projects, as long as one team member is available to present a demo of their project.
- If you discover a breaking bug during your demo with a trivial fix, that's okay to rectify. 🐛
- Submissions will be made to Devpost.
FAQ
Organising Committee
- Jeremy Chen
- Athena Eng
- Adarsh Arun Ganeshbabu
- Arya Golkari
- Oliver Greenwood
- Thomas Griffiths
- Swarnim Jain
- Eugene Kang
- Carol Khor
- Varun Latthe
- Dylan Moss
- Vedaangh Rungta
- Zeynep Takci