All micro-internships
Micro-internship brief ≈17h across ~3 days — playtest with real peoplebuilder

Vibe-code a browser game — and playtest it for real

Vibe-coding — building software by directing an AI — is a real skill with a real catch: the AI writes bugs confidently. Build a small browser game with AI, get 3 real people to play it, and fix what their playtesting exposes.

AI Application DevelopmentAnalytical Reasoning

Posted by The AI Internships

The work brief

  1. 01Design a small, finishable game: one mechanic, a score, a fail state (dodge game, quiz race, typing challenge, memory game).
  2. 02Build it with AI assistance (HTML/JS via any AI assistant or builder). You must understand enough to change constants and fix small bugs yourself.
  3. 03Deploy it publicly (GitHub Pages/Vercel/Netlify) and push the code to a public repo.
  4. 04Watch 3 real people play. Log what confused them, what broke, their scores — then ship at least 2 fixes from that list.

What you’ll produce

4 deliverables

Submission standard

Submit the playable URL, the repo, and the playtest log with your shipped fixes. We will play it. Include your AI workflow: tools, best prompts, and what you changed from the AI’s output. Link the specific commit(s) where your playtest fixes landed; they must come after your first build.

  • Public URL where we can play your game

    Public linkRequired

  • Public GitHub repo

    Public GitHub repo — commit history must show the initial build AND the post-playtest fixes as separate dated commits, not one paste. A single dump commit fails the authenticity gate.

    Public linkRequired

  • Playtest log: 3 real players, what confused/broke, their scores

    Written responseRequired

  • The 2+ fixes you shipped from playtesting, and what you changed in the code

    Written responseRequired

You’ll complete these inside your private workspace.

What you must submit as proof

This brief requires evidence an AI can’t fabricate.

  • Link to the commit(s) where you shipped your post-playtest fixes

    GitHub commit/compare URL showing the 2+ fixes landing AFTER your first build — proves iteration, not a one-shot.

    Public linkRequired

Submissions without this evidence cannot be submitted.

Protect other people in your proof. Blur faces, names, phone numbers and email addresses before you upload, and refer to anyone you worked with by role or number ("Listener 1", "the stall owner"). Your proof is only ever used to check your work — it is never published, never appears on your certificate, and is never shown in your public portfolio.

How your work is evaluated

The passing benchmark is 70/100.

Playable game

29%

The game loads, plays, and has a working score/fail state.

Real playtesting

29%

The log has the texture of real sessions — confusion, bugs, scores.

Fixes shipped

14%

Fixes trace directly to playtest findings and show code understanding.

Fixes trace to real commits

29%

If the game URL is dead, the repo is a single dump, or the fix commits don't exist or don't postdate the playtest, this fails regardless of the log's wording.

How we grade your AI usage

30% of your score

Using AI is the point — it’s the skill this certificate proves. You’ll answer three short questions about how you used it: what you asked, what was wrong with its first answer, and what you changed. Specific, honest answers score high. “I pasted the brief and submitted the answer” scores near zero.