JavaScript has not runIf it is turned off or blocked, everything about the event is on this page. If the site is still loading, it will appear in a moment.
Global Virtual Hackathon 2026
Build it, then defend it. A free, international online hackathon for students aged 14 to 18, hosted by Canadian International School, Singapore. Teams build a working project under a sealed challenge, then defend it in a personalised, on-camera interview drawn from their own code. Finalists defend it again, live, before the judges.
Key facts
- Who can enter: students aged 14 to 18 at any school worldwide, in teams of 2 to 4. Each student can be on one team only.
- Cost: free to enter. No purchase is needed, and none improves a team's chances.
- Divisions: Junior (ages 14 to 15) and Senior (ages 16 to 18), judged separately. A team's division is set by its oldest member, so if anyone on the team is 16 or over, the whole team enters Senior.
- Prizes: in each division, $1,000 USD for first place and two runner-up prizes of $250 USD each. That is six cash prizes, $3,000 USD across the two divisions. Finalists, shortlisted and longlisted teams, and three special awards per division, are also named.
- Format: online. Seven days to build under a sealed challenge, then a recorded on-camera interview with the whole team together in one room, then a live interview with the judges for finalists.
- 2026 theme: Unveiling Technology. The specific challenge is sealed until the opening ceremony on 19 November 2026.
- Dates: registration 28 September to 13 November 2026; challenge revealed 19 November; submissions close 23:59 AoE on 25 November; judging 26 November to 8 December; closing ceremony and results 9 December 2026.
- Adults involved: every team names a supervising teacher at a member's school, who confirms the team, and a parent or guardian signs consent for every member.
- AI tools: allowed and expected for building. Every team must understand its own work and be able to explain it.
- Host: Canadian International School, Singapore. Contact: organisers@gvhackathon.com.
Prizes and recognition
Each division, Junior and Senior, awards its own prizes. All amounts are in US dollars.
- First place: $1,000 USD cash.
- Runner-up: two per division, $250 USD cash each.
- Finalist: reached the live final. Nine teams per division are invited, including the three placed teams.
- Shortlisted: among the strongest entries in the division, close behind the finalists.
- Longlisted: entries that stood out to the judges.
- Participant: every team that submits a complete, valid entry.
- Special awards: Best Explanation, Best Defence and Most Ambitious Build, in each division. They recognise exceptional work in one area and are decided separately from the overall placings.
Only first place and the runner-ups carry cash. Each team is listed once, at the highest level it reached, and the sizes of the shortlist and longlist are not fixed. Results are published on the results page and announced at the closing ceremony on 9 December 2026. Every winning project is a public repository that its team can point to on a university application.
How prizes are paid. A prize goes to the team and is shared equally among its members unless the team agrees otherwise. Cash prizes are paid in US dollars by bank transfer once the organisers have verified the winning team. Because the students are minors, the money goes to a parent or guardian, or to the team's school, nominated by the team to pass on each member's share. Any taxes, fees or charges are the recipient's responsibility. Employees, contractors and judges of the organiser, and their immediate family, cannot win prizes. The organiser may decline to award a prize if no eligible entry meets the standard.
How it works
- Register your team. Sign up once with a shared team account. List your 2 to 4 members and name a supervising teacher.
- Get confirmed. Your teacher confirms your roster and uploads each member's signed consent form, and the organisers approve your teacher.
- Build under the brief. The challenge is revealed at the opening ceremony. You have seven days to build and submit a working project.
- Present your work. Answer a personalised on-camera Q&A. Finalists are invited to a live interview with the judges.
Round 1: the project
A working, publicly accessible project, a public source-code repository, a written project page and a short demo video, submitted by 23:59 AoE on 25 November. It must be the team's own original work, built during the event under the challenge. Open-source components and third-party tools are fine if you have the right to use them and follow their licences.
Round 2: the recorded interview
The whole team answers on camera together, in one continuous take, with every member visible throughout. The questions are written in advance from the team's own submission and source code, so they are grounded in the decisions the team made, and they climb from a warm-up to a genuine stretch. They are held on the organisers' servers and released one at a time, in order, only once recording has begun. A team records up to 10 minutes of answers inside a 40-minute window to read the instructions, record and submit, and gets one attempt. If a dropped connection, illness or another problem outside your control stops your team, email organisers@gvhackathon.com as soon as you can, and the organisers may allow another attempt. If a team member needs a reasonable adjustment, tell the organisers before your window opens.
Round 3: the live final
Finalists, nine teams per division, have a live video interview with the judges. More than one adult from the organisers is present throughout, and no judge meets a team alone. It is not recorded. A team's supervising teacher, or a parent or guardian, can attend as an observer if they ask beforehand.
Timeline
Deadlines close at 23:59 AoE (Anywhere on Earth, UTC-12). A deadline has not passed until the date is over everywhere on the planet, so no team loses hours to its timezone. The same moment in UTC is given in brackets.
- Registration: 28 September to 13 November 2026. Closes 23:59 AoE on 13 November (11:59 UTC on 14 November).
- Opening ceremony and challenge reveal: 19 November. The build window opens at 00:00 AoE that day (12:00 UTC on 19 November).
- Build period: 19 to 25 November, the same seven days for every team.
- Submission: closes 23:59 AoE on 25 November (11:59 UTC on 26 November).
- Judging: 26 November to 8 December.
- Closing ceremony and results: 9 December 2026.
2026 theme: Unveiling Technology
So much of what we use every day goes unquestioned, and is barely understood by the people who depend on it most. The challenge is to take one piece of it and make it genuinely understandable to someone who has never thought to ask how it works.
The theme is public. The specific challenge is sealed until the opening ceremony on 19 November, so no team can build ahead. The full brief appears on the site when the event starts.
How judging works and how it stays fair
- People make every decision. Human judges watch every interview and set every score. Two judges score each team independently, and their scores are checked against each other for agreement. Nobody is ranked or eliminated by a machine.
- One standard per division. Every team in a division is judged the same way, with the same weighting, on four things: the product, the recorded interview, the code and, for finalists, the live final. The criterion-by-criterion wording is not published in advance, so that teams build the best thing they can rather than the thing that scores.
- Where AI helps, and where it does not. A team's submission text and uploaded source code go to an AI provider, which writes a project summary, review notes, and the personalised interview questions with an answer key for the judges. It never scores, ranks or eliminates anyone. It can flag an entry as an obvious non-starter, and a person reviews every one of those before anything happens to it. The interview recording is not read by an AI service.
- Judges declare what they are close to. A judge with any connection to a team (their own school or organisation, a relative, a student of theirs, or any prior involvement with the project) declares it and is reassigned rather than scoring that team. Judges never see each other's scores before submitting their own.
- Decisions are final. The organisers do not have to give individual feedback or publish detailed criteria. The finer details of the anti-cheating measures are kept private on purpose.
Judges
These are the people who run and judge the event.
Leadership team
- Ruchika Dutt (Organiser and head educational judge). A Computer Science educator at the Canadian International School, Singapore, she teaches AP Computer Science and IB Diploma Computer Science and also serves as an IB Computer Science examiner. Her work centres on designing authentic learning experiences that strengthen students' computational thinking, programming skills and ability to address real-world challenges. In July 2026, she represented CIS at the College Board AP Annual Conference in Las Vegas, sharing how intentional curriculum design can connect MYP, AP and IB Diploma Computer Science and prepare students for advanced study. She holds a Master of Computer Applications and a certificate in Artificial Intelligence and Machine Learning from IIM Kozhikode.
- John Philip Green (Head product judge and speaker). Technology entrepreneur in Singapore and the founder and former CEO of CareGuide, a group of care marketplaces used by millions of families across North America. He has built several software companies and earned a Bachelor of Mathematics from the University of Waterloo.
- Saurabh Bhattacharya (Head technical judge). Principal for Applied AI Solutions at Amazon Web Services in Dubai, with about twenty years across architecture, cloud, and machine learning. He works with teams around the world and speaks often on cloud and AI.
Judging panel
The wider panel that scores teams alongside the leadership team.
- Tanay Agrawal (Technical Judge). Tanay Agrawal is co-founder and CTO of Quivly AI, a Y Combinator F26 company building AI agents for B2B post-sales teams. A Carnegie Mellon University alumnus, he previously worked at Atlan and JPMorgan, with experience across software engineering, product development and applied AI.
- Freddy Lim (Community Impact Judge). Freddy Lim is the founder of Claude Singapore Community and Claude Labs, where he leads enterprise AI strategy, hands-on labs and builder workshops across Southeast Asia. A Tatler Asia Changemaker and hackathon champion, he works with organisations such as the Lifelong Learning Institute to make AI accessible to everyone.
- Tarang Nair (Product Judge). Tarang Nair is a Founding Engineer at Nebula, where he builds Noether, an AI-powered patent-intelligence platform. He is also a co-founder at Exydio, an AI platform for businesses, and Purpal, an autonomous AI product-management agent. He serves as a judge and mentor at hackathons internationally.
- Dhiraj Ramnani (Technical Judge). Dhiraj Ramnani is a staff software engineer who has spent over seven years building and scaling large-scale advertising infrastructure, spanning audience automation, real-time data systems, indexing, retrieval, and semantic and generative systems. Dhiraj is a technical leader for ads targeting and audience automation infrastructure.
- Yanice Yang (Product Judge). Yanice Yang is a product designer specializing in AI agentic experience. As Lead Product Designer at AtlasNova.AI, she translates complex AI capabilities into intuitive tools, combining user research, interaction design, and prototyping to help people create, evaluate, and confidently guide AI to run the operation and content generation work.
A wider group of judges and organisers helps run and score the event, and not all of them are listed here. Before anyone joins the panel, the organisers check their identity and professional background, the school runs its own safeguarding checks, and the judge accepts written confidentiality terms, as the Safeguarding Statement sets out.
Rules in brief
- Students must be 14 to 18 when they register. Teams have 2 to 4 members, and each student can be on one team only.
- The event is open worldwide, except where taking part or receiving the prize would be unlawful. The team and its teacher check that taking part is allowed locally.
- Every member must be together in person, on a computer, for the recorded interview. You can build the project however you like before then.
- Every team names a supervising teacher at a member's school, who confirms the team. The organisers verify the teacher.
- If being together in person, or having a teacher at your own school, would make it genuinely impossible for a student to take part, email organisers@gvhackathon.com before registration closes. The organisers can approve an exception at their discretion in extenuating circumstances. Exceptions are agreed in advance, case by case, and the safeguarding requirements still apply in full.
- A team has one shared account and lists its members. There are no separate student logins.
- The work must be the team's own, made during the event under the challenge, and building with AI tools is allowed. Plagiarism, work a team cannot account for, and pre-built or off-theme projects are grounds for disqualification. So is getting outside help during the interview, or submitting anything other than a genuine live recording.
- You keep ownership of your project. The repository must be public, and you choose its open-source licence. The organiser receives a non-exclusive licence to use it to run, judge and promote the event, including showing the project with the team name and members' first names. Using a student's image, likeness or interview recording in promotion needs a separate, optional consent.
- Everyone follows the Code of Conduct. The terms are governed by the law of Singapore.
The full rules are in the Terms of Participation.
How to register
Registration runs on this site from 28 September to 23:59 AoE on 13 November 2026, and needs JavaScript. A team signs up once, at gvhackathon.com/signup, under one shared account. It lists its 2 to 4 members with their names, ages and contact emails, the name and email of each member's parent or guardian, and a supervising teacher. The teacher then confirms the team and uploads each member's signed consent form, and the team cannot submit its project until every form is in.
For supervising teachers
You confirm that the students on the team are who they say they are, are the right ages (14 to 18), and are normally at your school. You are the named adult who vouches for the team. You do not run the event or mark the work.
- Follow the link the organisers email you and sign in, or create a teacher account.
- Collect a signed parental or guardian consent form for every member of the team, and keep your own copy. The team prints each one from its portal with the details filled in.
- In your dashboard, accept the Supervising Teacher Agreement, then upload each student's signed form.
- Confirm the team.
That takes a few minutes. After that you are the point of contact: you raise any safeguarding concern promptly, handle the students' details responsibly, and encourage honest work. The students build the project themselves over seven days in November and sit their interviews online. You are a point of accountability, not a mentor or a marker. More on the page for teachers.
Safeguarding and privacy
The students taking part are aged 14 to 18, and the event is built around that. Contact runs through the portal and organiser email rather than private channels, judges are vetted before joining, the Round 2 interview is recorded, and the live final always has more than one organiser present.
- Safeguarding lead: Ruchika Dutt, ruchika.dutt@cis.edu.sg. Secondary contact: Peter Fremaux, peter.fremaux@cis.edu.sg. Anyone with a concern should tell a supervising teacher and email the safeguarding lead.
- Consent: a parent or guardian signs consent for every member, including a member who is already 18. It covers taking part and the recorded interview. It also asks to show the project afterwards, which is required, and to use the student's image and voice to promote the event, which is optional.
- Privacy: a team's submission text and source code are read by an AI service, and its interview recording is not. Anyone can ask for a copy of everything held about them. The Privacy Policy sets out what is collected, where it goes and how long it is kept.
Common questions
Who can enter?
Students aged 14 to 18 at any school worldwide, in teams of 2 to 4.
Which division are we in?
Junior is ages 14 to 15 and Senior is 16 to 18. Your division is set by your oldest member, so if anyone on the team is 16 or over, the whole team enters Senior.
How much does it cost?
Nothing. Entry is free.
Do we need a teacher?
Yes. Every team names a supervising teacher at a member's school, who confirms the team. Send them the page for teachers, which explains what that involves. If no teacher at your school can do it, email organisers@gvhackathon.com before registration closes. We can make exceptions at our discretion in extenuating circumstances.
Does the team need to be together in person?
For the Round 2 interview, yes. Your whole team is recorded together on camera in one continuous take, so every member must be in the same place, on a computer, at that time. You can build the project however you like before then. If that is genuinely impossible for someone on your team, email organisers@gvhackathon.com before registration closes. We can make exceptions at our discretion in extenuating circumstances.
Is it one account per team?
Yes. A team signs up once with a shared account and lists its members. There are no separate per-student logins.
What do we build?
A working project under a sealed challenge revealed at the opening ceremony. Your project code repository must be public.
How is it judged?
Your project is judged on the product and its code, a personalised on-camera Q&A, and, if you make it through, a live interview with the judges. Human judges make every decision.
Is AI allowed, and how do you keep it fair?
Building with AI tools is allowed and expected. What we check is that the work is yours and that you understand it, which is exactly what the on-camera interview tests. See how we keep it fair.
When does it run?
Registration opens 28 September 2026 and closes at 23:59 AoE (Anywhere on Earth) on 13 November. The challenge is revealed at the opening ceremony on 19 November, which opens the build window at the start of that day AoE, and submissions close 23:59 AoE on 25 November. That is seven days for every team, wherever they are.
Legal documents
There are six. Two are forms that someone has to sign before a team can take part, and the other four set out the rules and explain how the people taking part, and the information they give, are looked after. Each has a version and a date at the bottom, and the version a team accepted is stored with its registration.
- Parental / Guardian Consent. A parent or guardian signs one for every member of the team. It covers taking part and the recorded interview, and asks two things: that the project can be shown afterwards, and that the student's image and voice can be used to promote the event. Only the first is required.
- Supervising Teacher Agreement. The teacher who confirms a team signs this. They vouch for the roster, collect and upload the signed consent forms, and stay the adult the organisers contact if something goes wrong.
- Terms of Participation. The main rulebook: who can enter, how the deadlines work, what a team hands in, who owns what it builds, and how the prizes are paid. Registering a team counts as accepting it.
- Code of Conduct. How everyone is expected to behave, what happens if they do not, and where the line falls on using work that is not your own.
- Safeguarding Statement. About the adults around the students: it names the safeguarding lead, explains what a judge goes through before they are allowed near a recording, and sets out how to raise a concern.
- Privacy Policy. What is collected, where it goes and how long it is kept.
Contact
Organisers: organisers@gvhackathon.com. Safeguarding lead: ruchika.dutt@cis.edu.sg.
Pages on this site: home, judges, how we keep it fair, for teachers, results and legal documents. Signing up and logging in need JavaScript.