A rubric that lists innovation, execution, impact and presentation without weights leaves every judge silently applying their own — which is exactly the inconsistency a rubric is supposed to prevent.
A weighting I use and explain to teams upfront
- Execution, 35%: does the demo actually run on an input the team didn't rehearse.
- Problem clarity and impact, 30%: is there a real person with a real problem behind this, not just a technology showcase.
- Innovation, 20%: a genuinely new angle, not necessarily a new technology — a clever use of an existing one counts.
- Presentation, 15%: clear communication, not production value — a plain, honest pitch should never lose to a polished, vague one.
Why execution outweighs innovation
A brilliant idea that doesn't run teaches a judge nothing about the team's engineering; a working, unglamorous solution teaches a lot. Weight rewards what you actually want the competition to select for.
See judging AI hackathon projects: what to check for how execution gets verified in practice.
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.
