This hackathons is only open to students. Double check the event page for more information as this may mean only those from a particular university/country are eligible.
Event Type
online
73
Participants
6
Est. Projects
Organizers
Alex Johnson
alex@example.org
Jamie Rivera
jamie@example.org
Sam Chen
sam@example.org
Quality Score
Quality Score
72/100
High confidence
Organiser16/20
Event Maturity14/20
Sponsors18/25
Participants12/20
About the Event:
In a world driven by obscured signals and fragmented data, the ability to decode the truth is the ultimate power. The Rosetta Code Hackathon is a high-stakes engineering challenge designed to test your ability to bridge the gap between abstract data and real-world impact. This immersive experience pushes participants to navigate complex systems—from forensic medical recovery and cyber-infrastructure defense to deep-sea acoustic reconnaissance. It is more than just a coding competition; it is a test of collaboration, innovation, and technical grit. Only the most precise architects of logic will be able to decipher the chaos and claim their place among the elite.
Structure of The Event:
The hackathon is conducted in two distinct phases:
Round 1: The Online Qualifier (March 24th – March 29th): Teams will be presented with three distinct problem statements (Project Lazarus, Project AEGIS, and Project Abyssal Echo). Participants must strategically select and masterfully solve only one to qualify.
Round 2: The Hybrid Finale (April 3rd, 4th, and 5th): Shortlisted teams will move to a physical or testing ground (according to their convenience) where they will be given further task on the spot.
Judging Criteria:
Technical Accuracy: Correctness of the physics-based or logic-based corrections (e.g., Doppler sync, Hex-decoding, or status-code identification).
Code Readability & Design: Evaluation of the architecture, structured design, and documentation of the codebase.
UI/UX Quality: The effectiveness and clarity of the dashboard in visualizing the "Corrected Truth."
Efficiency: Points will be awarded for the speed and performance of the data processing engine.
General Rules:
Participants must register in teams of 2 to 4 members.
Only one problem statement is to be submitted for evaluation.
The use of AI is permitted, but teams must explicitly document and justify its implementation in their final report.
Any form of plagiarism or malpractice will result in immediate disqualification.
The decisions made by the organizing committee are final and binding.