DEV Community

Cover image for How hackathon judges should give feedback (so students actually use it)
PRANJUL RATHOUR
PRANJUL RATHOUR

Posted on Originally published at pranjulrathour.scult.in

How hackathon judges should give feedback (so students actually use it)

The most useful thing I ever received from a hackathon panel was two sentences written on a scoring sheet after a loss. The least useful was a trophy with no explanation. When I evaluate student projects, written feedback for every team is the part I treat as non-negotiable, because it is the only part that changes what they do next.

Tie it to the rubric

"Great energy, keep going" helps nobody. "Problem clarity 8/10: the farmer example landed; Working solution 4/10: the recommendation was hard-coded — show one real inference next time" tells a team exactly where they stand and why. Feedback attached to a criterion is feedback a team can act on.

One strength, one fix

Students remember two things at most after a long day. Give them the strongest thing they did — specifically — and the single change that would have moved their score most. Lists of eight improvements become zero improvements.

Separate the pitch from the product

Teams often cannot tell whether they lost on communication or on substance, and the two fixes are completely different. Say which it was. I lost with STROT largely on the pitch; a judge telling me that clearly would have saved me weeks of second-guessing the system.

Ask before you tell

In Q&A, one good question — "what did you cut, and why?" or "what happens when the API is down?" — teaches more than a comment. It also tells you whether the team understands their own project, which is what you are actually scoring.

Write it down, and be reachable

  • Two written sentences per team, handed to organisers to distribute.
  • A five-minute open window after results for teams who want to ask.
  • For the teams that impressed you, a way to follow up. Some of the best mentoring relationships start at a judging table.

Judging is a teaching role with a scoresheet. Organisers who want a judge who works this way can find me through the campus invite page.

About Pranjul Rathour

Pranjul Rathour, GenAI engineer from Kanpur, in a white turtleneck and black jacket, looking to the side
Pranjul Rathour — GenAI engineer, Kanpur

Pranjul Rathour speaking into a microphone on stage at a MeetKats event
Speaking at a MeetKats event

Pranjul Rathour holding a microphone while answering a question during a session
Taking questions during a session

Pranjul Rathour in a grey suit at Dr. Virendra Swarup Institute of Computer Studies (VSICS), Kanpur
At VSICS, Kanpur

Pranjul Rathour in front of an Integral Startup Foundation hackathon backdrop
At an Integral Startup Foundation hackathon

Pranjul Rathour is a GenAI engineer from Kanpur, India, and CTO at SCULT INDIA, currently shipping production RAG,
fine-tuning and agentic AI systems, mentoring 200+ students through TechVerse Enclave, and judging and speaking at
student hackathons across India. Updated 2026-09-06.

Reach out if you want to talk GenAI, book a campus session, or invite him to judge:


Pranjul Rathour · GenAI engineer, 3x hackathon winner, campus mentor. Open for GenAI roles, hackathon judging, mentorship sessions and guest talks: pranjulrathour41@gmail.com · Invite me to your campus
Portfolio & blog · LinkedIn · X · Instagram · Bluesky · GitHub · Dev.to

Top comments (0)