Weekly AI coding contests your team will actually show up for
Run private AI coding challenges that keep engineers sharp, build peer review habits, and create the kind of team culture that makes people stay. Free to start. No installs.
Why it works
Why engineering teams need AI coding contests
Keep engineers hands-on with AI tools
A 30-minute weekly AI coding contest is lower overhead than a lunch-and-learn, more engaging than a tech talk, and more effective at keeping your team fluent with the AI tools they use every day.
Healthy competition builds real culture
Friendly rivalry creates shared memories, inside jokes, and pride in craftsmanship. It's the kind of thing that makes developers tell their friends where they work and actually mean it.
Peer review that happens organically
The voting phase isn't just scoring. It's your whole team reading each other's code, AI prompts, and approaches. That casual cross-pollination teaches more than a formal PR review cycle.
How it works
How weekly AI coding contests work
Create a private team contest
Write a brief: 'Build a CSS animation', 'Create a REST endpoint', 'Design a dark-mode dashboard'. Set 30–60 minutes. Drop the invite link in Slack.
Everyone builds with an AI assistant
Participants join from a browser, no install, no setup. Claude is already in the editor. They build the challenge and auto-submit when time runs out.
Review code, vote, and see who wins
All submissions go live for the team. Everyone reviews the code, AI prompts, and live previews. The team votes. The leaderboard updates in real time.
Build collaboration through peer review
After every contest, all submissions (code, AI prompt history, and live preview) are open for the whole team to explore. Voting isn't just scoring; it's your team reading each other's work, borrowing techniques, and building shared taste in what good code looks like. No awkward PR comments required.
Platform features
Everything engineering teams need
Private invite links
Only people with your link can join. Nothing is publicly listed.
Flexible time limits
15-minute sprints to 90-minute deep dives. You set the pace.
Claude AI built in
Every participant gets Claude in their editor, the same AI your team uses daily.
Full submission review
See the code, the AI conversation, and a live preview for every entry.
Unlimited participants
10-person startup or 200-person org. No seat limits.
Up and running in 2 minutes
No config, no installs. Create a contest, share the link, done.
Real example
Example: Friday Engineering Challenge
Friday @ 4:00 PM: 45-minute team sprint
Contest opens
Brief drops in Slack: 'Build a dark-mode pricing page'. 8 engineers join via link.
Live coding
Everyone codes with Claude in the browser. No install. Auto-submit at 4:45.
Voting & review
All submissions visible. Team reviews code + AI conversations. Everyone votes.
Winner declared
Leaderboard updates. Winner gets bragging rights (and a Slack emoji) until next Friday.
Benefits
Benefits for engineering teams
Engineers stay fluent with AI tools they use on real projects
Cross-team exposure to different coding styles and problem-solving approaches
Organic mentoring as seniors and juniors compete on the same brief
A weekly ritual that's actually worth blocking the calendar for
Peer code review without the formality of a pull request process
Leaderboard bragging rights that outlast any Zoom happy hour
Who it's for
Who should use it?
Engineering Managers
Building team culture without adding more meeting overhead.
Senior Developers
Who want to share techniques and see how teammates approach problems.
CTOs & Tech Leads
Keeping engineers engaged and building a team identity.
L&D Teams
Running measurable skill-building activities developers actually enjoy.
FAQs
Common questions
How long should a team coding contest take?
30 to 60 minutes is the sweet spot for most engineering teams. Long enough to build something meaningful, short enough to run weekly without fatigue. Many teams do 45 minutes on Friday afternoons.
Can we keep contests private to our team?
Yes. Every contest generates a private invite link. Only people with the link can join. Nothing is listed publicly. Perfect for internal team challenges.
What kind of challenges work best for engineering teams?
Open-ended creative briefs work best: 'Build a dark-mode landing page', 'Create a real-time leaderboard component', 'Design a REST API for a todo app'. Avoid algorithm puzzles: they reward memorization, not craft.
Do participants need to install anything?
No. Everything runs in the browser. Participants click the invite link, join the contest, and start coding immediately. Claude is already in the editor.
How does voting work after a team contest?
Once the timer ends, all submissions are visible to every participant. Each person votes for their favourite. Results are tallied and the leaderboard updates live. No judges, no panels.
Is Vibe Coding Game free for engineering teams?
Yes, free to start, no credit card required. Create a contest, invite your team, and run your first challenge today.
Also worth exploring
Start your first team contest
Create a contest, paste the link in Slack, and see who builds the best solution. Free to start. No credit card.