Skip to content
← All opportunities

Hackathon

hackathonRemoteOnline
Apply on National Institute of Technology (NIT), Arunachal Pradesh →

Opens the company's own listing — Aspirova never mirrors applications.

Sign in to save
Deadline: 25/10/2026

Skills for this role

Skills we detected for this role.

  • Git
  • UI/UX Design

Opportunity brief

Overview

Ideate. Innovate. Build. Conquer.

The ADDOVEDI 2026 Hackathon is a 24-hour continuous software development and innovation competition (NIT Arunachal Pradesh), organised by Coding Pundit, Dept. of CSE. Build a working MVP for the problem statement, then pitch and demo it to the judges. Held on campus, 28-30 October 2026.

Guidelines

  • Eligibility: to be announced by the organisers. Carry a valid student ID.
  • Team size: 2 to 4 members. One team per participant.
  • Seats: only the top 25 teams, first come, first served by registration time.
  • Format: 24-hour continuous hackathon, three stages: Idea Pitch, Prototype Development, Final Demo.
  • Problem statement: released by the organisers. A focused, working MVP beats a large unfinished one.
  • Duration: 24 hours. Date, venue and clock times announced by the organisers.
  • Judging: 100 points: problem and solution 25, UI/UX and product 25, technical implementation 25, presentation and Q&A 25.
  • Registration: sign up on the Addovedi website, register for Hackathon to get your Team ID, then register on Unstop with the Team ID + the leader's Addovedi ID.
  • Registration fee: Rs. 50 per member (each team member pays Rs. 50).
  • Prize pool: Rs. 30,000+ (including goodies).

Rules

  • Any language, framework, database or API is allowed. Deployment is optional.
  • AI tools are allowed but earn no extra marks. You must be able to explain every important part of your code.
  • Keep a public GitHub repository from the start. Commit regularly. The repository freeze time is strict.
  • Plagiarism, collusion, faking Git history or functionality = disqualification.
  • Do not attack or access other teams' or organisers' systems. Report any vulnerability you find.
  • No secrets or API keys in the repo. Credit major external resources in the README.
  • Arrive on time. Late arrivals may lose build time. Follow organisers, volunteers and judges.
  • Organisers' decisions are final. Material changes are announced to all participants.

More like this

Related opportunities