Twenty-six weeks, four sprints

The fellowship is a six-month programme built around four sprints. It is not
an internship with a certificate at the end — you work on live systems, and what you build is
used.

How the sprints run

Sprint one — foundation and immersion, weeks 1–6

Orientation into how we work, then guided execution. You contribute to documentation,
interface work, campaign support and internal tooling while you learn the domain. Ends with a
sprint-one certification and a review for progression.

Sprint two — delivery and ownership, weeks 7–12

You move from guided contribution to owning deliverables. Sprint planning, reviews, and
production-grade output across platform components, creator-facing systems and analytics.

Sprint three — specialisation, weeks 13–18

Deeper work in a chosen area, with closer collaboration with engineering and design leads.
Systems architecture exposure, longer-form execution, product experimentation.

Sprint four — acceleration, weeks 19–26

Independent delivery and process ownership. Fellows often lead an internal initiative, a
product module or a piece of research. Ends with a presentation and a full review.

Tracks

• Writing, documentation and founder’s office — brand and technical writing,
  
  research reports, long-form content.
• Design — interfaces, design systems, motion, campaign and brand work.
• Product engineering — front-end systems, APIs, internal tooling and
  
  dashboards.
• Software architecture — distributed systems, scalability, reliability.
• People and operations — hiring systems, onboarding, coordination.
• Marketing and community — growth, community, creator communication.

What you leave with

A portfolio of work that was actually used, a certification per completed sprint, a letter of
recommendation if you earned one, and a considerably better idea of whether this industry suits
you. Strong fellows are considered for full-time roles as they open.

How to apply · Verify a certificate