A tie at the top of the leaderboard, resolved by an organiser's gut call in the final ten minutes, is the single fastest way to make a hackathon's results feel arbitrary to every team that didn't win.
Decide the process before the event, not during it
- First tiebreaker: the highest-weighted rubric criterion alone (execution, in most rubrics) — whoever scored higher there wins the tie.
- Second tiebreaker: a live follow-up question to both teams, scored blind by the panel without discussion.
- If still tied, both teams share the placement rather than a coin flip deciding it.
Tell teams the process upfront
Publishing the tiebreak rule alongside the rubric, before the event starts, means nobody feels like the rule was invented to produce a particular winner. See a hackathon judging rubric organisers can copy.
GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).
Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.
