Your first hackathon as a first-year: how to be useful with limited skills

A first-year's guide to being valuable on a hackathon team before you can code well: user research, the pitch, testing, seeded data, and the habits that get you invited back.

Walking a room through evaluation criteria
Walking a room through evaluation criteria

When I spoke to 100+ first-years at the VSICS induction seminar, the most common question afterwards was some version of "how can I join a hackathon when I barely know programming?". The honest answer is that a team has more jobs than coding, and the non-coding ones are where first-years win.

Jobs that need judgement, not syntax

  • User research — talk to five people about the problem in hour one and bring back quotes. Most teams skip this; judges notice when it was done.
  • The pitch — draft the story, run the rehearsals with a timer, prepare Q&A answers. See the pitch deck template.
  • Test data — write the realistic seed data that makes the demo look alive.
  • Testing — click through the demo path every hour and report what breaks. You are the first user.
  • Documentation — the README and the submission form, written while the coders code.

How to learn during the event

Sit next to the builder and ask to own one small, real piece — a form, an API call, a page. Ask questions at the checkpoints, not every ten minutes. Take notes on decisions and why they were made; that is the architecture lesson no lecture gives you.

What gets you invited back

  • Doing the unglamorous job completely.
  • Saying "I don't know how, show me once" instead of guessing silently.
  • Staying calm when the demo breaks.
  • Following up after the event — a message with what you learned and what you want to build next.

What I tell first-years

Year one is for foundations and for showing up. Do one hackathon as the person who makes the team look organised. By year two you will be the person who builds, and you will already know how the room works. The three-year roadmap I gave at the induction is in what I told 100+ first-years.

HackathonsFirst-yearsStudentsMentoring
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