All micro-internships
Micro-internship brief ≈16h across several days — expect review waitingbuilder

Make your first real open-source pull request

One merged PR on a real project outweighs ten tutorial certificates. Find a real open-source project, use AI to decode the unfamiliar codebase, pick a genuinely useful small contribution — docs fix, good-first-issue, translation — and take it through the full PR process.

AI Application DevelopmentContent StrategyProduct Localisation

Posted by The AI Internships

The work brief

  1. 01Find a target: GitHub topics like good-first-issue, projects you actually use, or regional and language-specific open-source communities. Read their CONTRIBUTING.md first.
  2. 02Pick something real but small: a docs error you verified, a reproducible bug from their issues list, a missing translation. AI can help you understand the codebase — the judgement is yours.
  3. 03Fork, fix, and open the PR with a proper description: what, why, how you tested. Follow their checklist.
  4. 04Engage with whatever happens — review comments, CI failures, silence (in which case, note your follow-up plan).

What you’ll produce

3 deliverables

Submission standard

Submit the PR link (must be a real, public PR you authored), why you chose this contribution, and the story of the process. Merged is great; a well-handled open or rejected PR also passes. Include your AI workflow: tools, best prompts, and what you changed from the AI’s output. Include your GitHub profile URL so we can confirm the PR was authored by you on a real external project.

  • Link to your public pull request

    Link to YOUR public pull request — it must be authored by your own GitHub account on a real external project, with the description and any review/CI activity visible. A PR to your own throwaway repo fails the authenticity gate.

    Public linkRequired

  • Why this project and this contribution — and how you verified the problem was real

    Written responseRequired

  • The process story: CONTRIBUTING rules you followed, review feedback or CI failures, what you learned

    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.

  • Your GitHub profile URL (to confirm you authored the PR)

    Must be the same account that opened the PR — lets us confirm the contribution is really yours.

    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.

Real contribution

29%

The PR exists, is theirs, targets a real project, and adds genuine value.

Process followed

14%

Contribution guidelines followed; PR description is professional.

Engagement & learning

29%

Handled feedback/CI/silence maturely; reflections are specific.

Really your PR on a real project

29%

Fails if the PR is dead/private, is on your own toy repo, or the author doesn't match your profile — the contribution must be yours on an external project.

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.