Nobody becomes a hackathon judge by applying to a listing — organisers ask someone whose judgement they already trust, usually because of something public: a rubric they published, a talk they gave, projects they've clearly evaluated before.
What actually builds that trust
- A published, reusable rubric — see a hackathon judging rubric organisers can copy — that shows you think about scoring before anyone asks you to.
- Mentoring at hackathons first; mentors who give sharp, structured feedback are the pool organisers pull judges from.
- Being visibly active in the student-hackathon community — organising, speaking, writing — so your name is the one that comes up.
Making yourself easy to invite
Put a standing offer somewhere organisers can find it, with the logistics already answered: on-site or remote, what you need in a briefing, how many teams you can fairly assess. I keep mine on the invite page for exactly this reason.
See what hackathon judges look for for the method itself once you're on a panel.
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.
