What a hackathon mentor actually does (and how to use one)

The mentor's job during a hackathon: unblock without building, ask the scoping question, run a mock pitch, and know when to step back — plus how teams should use the mentor hours they usually waste.

Trophy and certificate after a win
Trophy and certificate after a win

A hackathon mentor is not a senior developer who fixes your bug, and not a judge who tells you what to build. Having mentored 200+ students through TechVerse Enclave and coached teams before events, I think of the role as three interventions delivered at the right moments.

Intervention one: the scoping question

In the first hours, the most valuable thing a mentor says is: "What is the one thing you will demo, and can you show me a sketch of that screen?" Teams that cannot answer are about to build a platform. The mentor's job is to help them find the single path and let the rest go.

Intervention two: unblock without building

When a team is stuck at hour ten, the mentor asks questions until the team finds the fix, points to documentation, or suggests a simpler approach. The mentor does not type. A mentor who writes the code has removed the learning and, in most rulebooks, disqualified the team.

Intervention three: the mock pitch

Two hours before freeze, run the pitch with a timer and play the harshest judge in the room. Ask the questions in questions judges ask in hackathon Q&A. Then give one strength and one fix, the same way a good judge would.

How teams should use mentors

  • Book a slot early for scoping, not late for debugging.
  • Bring a specific question and the code or sketch it is about.
  • Ask what a judge would think of the demo path — mentors have usually judged.
  • Do not ask which idea is better; ask which one you can finish and demo.

For organisers

Schedule mentors in shifts with a visible board, brief them on the rubric, and separate mentors from judges where you can — a mentor who later judges the same team is in an awkward position. I am glad to take either role at student hackathons; organisers can reach me at pranjulrathour41@gmail.com.

MentoringHackathonsStudentsGuide
Pranjul Rathour
Pranjul Rathour
GenAI Engineer · Kanpur, Uttar Pradesh, India

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.

Keep reading

More on Hackathons

All Hackathons posts →
Campus talks · hackathon judging · mentoring

Want this as a live session at your college?

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges.

Pranjul Rathour, GenAI engineer in Kanpur