Vibe Coding hackathons 2026
Hackathons that ask or recommend you to build with AI coding tools such as Kiro, Claude Code or Cursor, or that give a prize for it.
Right now we list 3 open Vibe Coding hackathons. 3 list a cash prize; the largest is $150,000 (Google Quantum AI - Verifiable Quantum Circuit Compilation). 3 say solo entrants are welcome. None say they are open to entrants in every country. The next submission deadline is 2026-11-30 10:00 UTC (2026 Qoder Campus Creativity Competition); the latest is 2027-01-20 23:59 UTC (Google Quantum AI - Verifiable Quantum Circuit Compilation). Updated 2026-11-20.
A vibe coding hackathon is built around AI coding tools. You describe what you want in plain language, and a tool such as Claude Code, Cursor, Kiro, GitHub Copilot, Windsurf, Replit or Lovable writes much of the code while you steer, test and fix it. Some events require a specific tool, some give a separate prize for the best project built with one, and some only recommend it.
We list a hackathon here when its own page asks for, recommends or rewards building with AI coding tools. The tool names come from each event, so check which one an event expects before you start.
- 2026 Qoder Campus Creativity Competition · 2026-11-30 10:00 UTC
- Kiro · Kiroween 2026 · 2026-12-04 22:00 UTC
- Google Quantum AI - Verifiable Quantum Circuit Compilation · 2027-01-20 23:59 UTC
Questions
Do I need to know how to code?
Less than at a classic hackathon, but it still helps. You need to read what the tool writes, run it, and notice when it is wrong. If an event is aimed at beginners, its page usually says so.
Do these events require a specific tool?
Often. Many sponsored events require or reward their own tool and may give free credits for it. Read the rules, because a project built with a different tool may not qualify for that prize.
Is AI-written code allowed?
In this category, yes; it is the point of the event. Other hackathons may limit AI-generated code or ask you to disclose it, so check the rules before you reuse a vibe-coded project elsewhere.
How should I present a vibe-coded project?
Show the working product first. Some events also ask for your prompts, a session log or a short note on how you used the tool; include them when the rules ask.
What should I test before submitting?
Run the main user journey from a fresh start, using the same setup a judge will receive. Check an empty input, an invalid input and a failed request as well as the successful path. Read the generated code around those cases so you can explain what the application does when something goes wrong.
How do I keep an AI coding session focused?
Write down one user, one problem and one working result before asking for code. Build that path in small steps, running it after each change. Keep a version that works before trying a larger revision. In the demo, distinguish the features you tested from ideas that are still unfinished.
Other categories
Guides: For students · New to AI · Experienced builders
One email a week
New events that match your topics, every Monday. Unsubscribe anytime.