HACKATHON — 48 HOURS
Code Conqueror India 2026
A national online hackathon in one forty-eight-hour window: one problem statement, one working product. Free to enter, teams of one to four, with ₹30,000 in prizes, paid internship and incubation opportunities for the top three.
- Date
- 28 Oct — 30 Oct 2026
- Starts
- 10:00
- Runs for
- 48 hours
- Joining
- Details sent to everyone who registers
- Kind
- hackathon
- Who it is for
- Students, developers, designers and first-time builders.
Code Conqueror India 2026 is a national-level online hackathon run in a single forty-eight-hour window. The problem statement lands an hour before the clock starts, and what you submit at the end of it is what is judged.
Submissions are scored on one published sheet, out of 100, and it is on this page before you start.
The problem statement is issued by the organisers one hour before the hackathon starts. Everyone receives it at the same time, and every team builds against the same brief.
₹30,000
Prize pool
48
Hours to build
1–4
Per team
Free
Entry fee
[ Brief ] // What you are being asked to do
Build a working solution to the problem statement you are given, in forty-eight hours.
What you leave with
- A product that runs, and a repository anyone can open
- The thinking written down: the problem as you read it, what you built, and where it would go next
- A certificate for every member who files their own submission inside the 48 hours
- Something to show that is yours rather than a tutorial's
Team size
1 to 4. Every participant belongs to one team only.
Who can come
Undergraduate and postgraduate students across engineering, management, arts, commerce and the sciences, alongside developers, designers, AI and no-code builders and first-timers. Registration is open nationally.
[ Schedule ]
- Until Mon 26 Oct, 23:59Registration open. Form a team of one to four and join the official group.
- Wed 28 Oct, 09:00The problem statement and the official PDF format go out, to everyone at the same moment.
- Wed 28 Oct, 10:00The forty-eight hours open. Build the one workflow that solves it.
- Fri 30 Oct, 10:00Submissions close. Everything on the list is in, or it is not.
- After the eventFinal results once the submitted projects and participant eligibility have been verified.
[ Judging ]
Understanding of the problem statement20 points
Have you read what was actually asked? Who holds this problem, what it costs them today, and which part of it you took on rather than all of it.
The solution, and whether it runs25 points
A judge opens your link and completes the main journey without being talked through it. Forty-eight hours is short, so rough edges are expected — a broken middle is not.
Technical depth and reliability20 points
How well have you used what you chose? Do the integrations, data flows and AI components hold together under ordinary use?
Originality of approach15 points
Every team has the same brief. What is different about your reading of it, or the angle you took on it?
Usability and real-world fit12 points
Could the intended user work it out without a walkthrough? Is it practical in the setting it is meant for?
Documentation and what comes next8 points
Could someone else run this from the repository? And is the next step a credible plan rather than a wish list?
[ What you get ]
- ₹30,000 in prizes, shared among the top three teams — awarded as cash, as AI or platform credits, or as a combination of them
- Paid internship opportunities for the top three teams
- Incubation and product-development opportunities for the top three teams
- A complimentary .XYZ domain for every participant
- $100 in Inkloom AI credits for every eligible participant
- $500 in Adaption Labs credits for every eligible participant
- 100+ reward recipients across the hackathon
- A certificate for every participant who files their own submission inside the 48 hours
- A Winner Certificate naming the rank, for the three winning teams
[ How the 48 hours run ]
One problem statement, forty-eight hours, and an entry from every person who built. The problem statement is released by the organisers an hour before the clock starts, so every team begins from the same brief at the same moment. There are no qualifying rounds and nothing to clear first. Every participant submits: the project is filed once per member rather than once per team, and each person names the role they held on it — Backend, Frontend, AI / ML, Design / UI-UX, Product / Research or Presentation / Demo — and writes in their own words the part they built. Those two answers are what your certificate prints, so a member who files nothing has nothing recorded and is not issued one. Taking part is free from start to finish. No promotional posts, no social links and no video demonstrations are required; only the documents and project links listed here.
- A link to the working project, which a judge must be able to open and use without being talked through it
- The source-code repository, with whatever access judges need to read it
- A project PDF on the official format: the problem as you read it, who has it, your solution and the workflow through it
- The list of features you completed, and anything you knowingly left undone
- The technology stack, and a short summary of how it is put together
- Testing notes for the main journeys
- Where the product would go next, if you carried on with it
- Team and participant details
- Your own role on the project, and the part you built, in your own words — these are the two lines your certificate prints
[ Rules ]
- The product must be built inside the official hackathon window — the forty-eight hours this event runs for. Work that existed before the clock started does not count.
- We verify this. Submissions are checked, judges may ask a team to evidence that the work was done inside the window, and we do not discuss how those checks are run.
- A project found to have been built before the event does not win, however good it is. There is no partial credit for this and no appeal.
- You may research, plan and discuss ideas before the event. Thinking is not building.
- Existing libraries, APIs, frameworks and open-source components are allowed.
- Templates or code you wrote earlier must be clearly disclosed in the submission.
- Only work done during the event counts towards judging.
- AI, no-code and low-code tools are allowed, and the significant ones must be disclosed.
- Taking part is free. There is no participation fee at any stage of this event, nothing to pay to be judged or certified, and nobody from We Code Coders will ask you for money.
- Every participant belongs to one team only.
- The project must be the team's own work.
- Plagiarised, copied or misleading submissions are disqualified.
- Respect software licences, intellectual property and user privacy.
- Projects must not promote illegal, harmful or discriminatory activity.
- One submission per participant, not one per team. Every member files their own entry for the same project, names the role they held on it and states the part they built; a second entry from the same person is not counted.
- A participant who files no entry of their own is not recorded as having taken part, and is not issued a certificate, even where the team's project was submitted by somebody else.
- Everything on the submission list has to arrive before the forty-eight hours are up. There is no late window.
- Judges may ask for repository access or other proof of development at any point.
- Organisers may remove anyone who disrupts the event or breaks community guidelines.
- Do not ask an organiser, judge or volunteer to break a rule, waive a requirement or make an exception in your favour. You may ask once; when the answer is no, that is the answer.
- Pressuring, forcing, threatening or intimidating an organiser, judge or volunteer disqualifies the whole team, not only the person who sent the message.
- The judges' decision is final.
- We will announce the top 3 teams in the official group, along with the project URL of what each of them built. No participant's personal details, and nothing further from a team's submission, are shared or passed on unless we have that team's consent.
- Only the top three are placed. The three winning teams are named with a link to what each of them built, and their certificates print the rank; no other team is given a position, no ranking list is published, and no certificate below winner carries a placing.
- Scores, judging sheets, internal notes and comparative breakdowns are not shared, and there is no personal feedback, re-evaluation or second presentation.
- About the prize pool: it is the total value of the prizes shared among the winners. A prize may be given as cash, as AI credits, as both together, or as just one of them. We will tell the winners exactly how theirs is made up, and we thank you for your understanding.
- We understand the wish for transparency, but that does not mean we share every detail of every round. We have automated the sending of mails and we follow that system as it is, as already stated on this event page. For transparency, we announce the top 3 in the official group itself, and that is the most important part. This is how much transparency we will deliver, and not more than that, because we have more events to manage. What we have promised, we will always deliver.
[ Certificates ]
One certificate, and everyone who builds gets one. Every participant who files a valid entry of their own inside the forty-eight hours is issued a certificate — you do not have to place, and there is nothing to pay for it.
- A Certificate of Participation, for every member who files a valid entry of their own inside the window.
- A Winner Certificate naming the rank — first, second or third — for the three winning teams.
- Registering is not taking part. A participant who files no entry of their own, or whose entry is not valid, is not issued a certificate — including where the rest of the team submitted.
- Your certificate names the role you declared and the part you built, in the words you submitted them in. That is why every member files their own entry rather than one per team.
- Each participant receives one certificate only: a winning team's members are issued the Winner Certificate rather than both.
- Only the top three are placed. The group announcement carries those three team names and a link to what they built, and their certificates print the rank — first, second or third. No other team is told a position, and none is printed on its certificate.
- Submissions are judged by Inkloom, as every event in this series is, and final results are declared one week after the hackathon ends.
- Certificates are distributed within 10 days of the results being announced, not from the day the event ends.
[ Questions ]
How does it run?
One window, forty-eight hours long. The problem statement lands an hour before it opens, you build, and you submit once before it closes. There are no qualifying rounds.
Is it free?
Yes. Registration is free, taking part is free, and there is no participation fee at any stage — not to be judged, and not to be certified.
Are problem statements provided?
Yes. The organisers release the problem statement one hour before the hackathon starts, to everyone at once. There is nothing to prepare against beforehand.
Who submits for the team?
Everybody, separately. Each member files their own entry for the same project before the window closes, names the role they held — Backend, Frontend, AI / ML, Design / UI-UX, Product / Research or Presentation / Demo — and says what they built. Nobody submits on anyone else's behalf, and a member who files no entry is not recorded as having taken part and is not issued a certificate.
Will everyone get a certificate?
Everyone who builds and files their own entry, yes. Every member who makes a valid submission inside the forty-eight hours is issued a Certificate of Participation, and the winning teams are issued a Winner Certificate naming their rank instead. Registering without submitting does not earn one, and neither does leaving the submission to a teammate.
Can I take part on my own?
Yes. Solo entries are allowed, and so are teams of up to four.
Can beginners enter?
Yes. The event is built for first-timers and experienced builders alike, judged on the same criteria.
Can my team come from different colleges?
Yes. Members can be from different institutions, cities or backgrounds entirely.
Can I use AI tools?
Yes. Disclose the significant ones in your submission.
Can I use something I built earlier?
No. The product has to be built during the window, and submissions are checked. Disclosed reusable components are fine; a finished project is not.
Is deployment compulsory?
You need a link judges can open and use. If you cannot deploy, provide a reliable executable the judges can run.
Are social media posts required?
No. Nothing on LinkedIn, Instagram or anywhere else is part of a submission, and no video demonstration is required.
Where are results announced?
We will announce the top 3 teams in the official group, along with the project URL of what each of them built. That is the whole announcement. Only those three are placed — no ranking list goes up, no other team is given a position, and a Certificate of Participation does not print one. Nobody's personal details are shared without their consent.
When do results and certificates arrive?
Submissions are judged by Inkloom, and final results are declared one week after the hackathon ends, once every eligible submission has been reviewed. Certificates follow within 10 days of the results being announced.
[ Partners ]
Title sponsor
Official event partner
Domain partner
Organised by
[ Terms and agreements ]
Entering is acceptance. Taking part means you accept these terms in full — the participation notice, the certificate policy, judging and conduct. The link goes out with the joining instructions, and everyone is asked to read the whole page beforehand. This event is free from start to finish: one round, with nothing to pay to enter, to be judged or to be certified.