A hackathon that hands out a vague theme ('build something for education') gets back thirty completely incomparable projects, and no rubric can fairly rank an app against a hardware demo against a research notebook.
Write problem statements with judging already in mind
- Name a real user and a real constraint: 'help a first-generation college student pick electives' scores more consistently than 'improve education'.
- State what a working submission must be able to do, at minimum, so 'execution' has something concrete to check against.
- Keep problem statements narrow enough that teams choosing the same one produce genuinely comparable projects.
The organiser's real job here
A good problem statement does half of a judge's calibration work before the event even starts, because it constrains what 'good' can look like. Spend the time here; it pays off in every judging round that follows.
See how to run a college hackathon: an organiser's guide.
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.
