Skip to content
SaaSFarersOpen Source · Open Journey
InternshipsOn live client projects

Real code, real users, real review

Most internships are a certificate and a slide deck. Ours is a branch, a pull request, a reviewer who will send it back, and a feature that ends up in front of someone's customers.

The difference

What an internship should be

An internship is your first exposure to the thing courses cannot simulate: other people depending on your work. Ambiguity you have to resolve. A codebase you did not write. A reviewer who is not impressed by effort, only by correctness. A deadline attached to someone's business.

That is why ours sit on live client projects. Scoped carefully so a learner can contribute safely, but never fake.

What you will not be doing
  • Writing documentation nobody reads
  • Rebuilding a tutorial project as "the intern task"
  • Sitting in a room waiting for something to be assigned
  • Working on a fake project invented to keep interns busy
  • Leaving with a certificate that says nothing about what you did
How it runs

Twelve weeks, structured

  1. 01
    Week 1 · Onboarding

    Environment set up, codebase walkthrough, architecture briefing, and your first small merged pull request. Everyone ships something in week one.

  2. 02
    Weeks 2 to 4 · Supervised delivery

    Well-defined tasks with a named reviewer. You learn the review standard, the test standard and how the team communicates.

  3. 03
    Weeks 5 to 8 · Owned feature

    A feature of your own, from clarifying the requirement through design note, implementation, tests and release behind a flag.

  4. 04
    Weeks 9 to 11 · Production exposure

    You join standups and release calls, and you will handle at least one real production issue with someone experienced beside you.

  5. 05
    Week 12 · Review and reference

    A written assessment against the bar we hire at, a reference letter describing your actual contribution, and a conversation about what comes next.

What you leave with

Evidence, not adjectives

A public commit history

Your pull requests, the reviews on them, and the iterations. Hiring managers can read how you think.

A real reference

Written by the engineer who supervised you, describing what you built and how you handled being wrong.

Stories you can tell

Interviews are won on specifics. You will have three or four you can talk about for ten minutes each.

Questions

Internship FAQs

Internships that form part of an Academy track are included in the programme fee rather than separately paid, because they are supervised training on real work. Interns who move into a longer engagement after the programme are paid at our standard early-career rates.

The internship is part of every track.

Pick a track, complete the core modules, meet the assessment bar, and you are on live work. Applications for the next intake are open now.