Rebuilding Apprenticeship

For GCC and engineering leaders · cohorts from January 2027

The work that trained your freshers is going. So is the pipeline that produced your seniors.

Engineering's constraint has moved to specifying what to build, proving it's right and running it in production. That's what your centre needs to own products rather than execute tickets, and engineers who can do it are already the scarcest people in the Indian market. Rebuilding Apprenticeship is a ready-to-run programme that grows them from your own fresher intake, mentored by your seniors.

24 weeks
or a 12-week intensive
10–20
juniors per cohort
~2 h
senior time per junior a week
2–3
design partners for January
Quarterly programme reportfor your parent org
  • 01Competency movement6 competencies per junior, rated with written evidence
  • 02Defects foundPlanted-bug hunts, early in the programme vs late
  • 03Spec qualityAgent runs needed to meet acceptance tests
  • 04OperationsServices deployed, incidents handled, postmortems written
  • 05InvestmentSenior hours spent, stated plainly
Judgement made visible, so the programme can be defended as an investment, not a training cost.

Why another round of tool training won't fix it.

Every centre is running AI and framework training. Almost every centre can show pilots. Very few can show engineers who own outcomes, and that is what decides whether a centre is defended or shrunk.

Framework familiarity is the cheapest thing in the market

Any engineer can add an agent framework to their profile after a course. Far fewer have specified a system, proved it right and run it in production. An interview separates the two in minutes, and so does the first incident.

Licences and training are the small part

The organisations getting results had strong fundamentals first: tests they trust, small batches, teams that operate what they build. Tools amplify what's already there, including its gaps.

Ownership needs judgement, and judgement isn't taught

Freshers used to acquire it over years of corrected implementation work. That work is going, and every company saving on juniors is dismantling the supply of the seniors it will need most in five years.

We built the curriculum that teaches judgement on purpose, so your seniors only supply the part that only they can: the questions.

The programme

Five elements and two practices, in 24 weeks.

01

Fundamentals, unassisted

AI OFF

Someone who has never written a concurrent program by hand won't see the race condition in one an agent wrote. In their first weeks, juniors build a small service, its storage and its tests from nothing, with the tools switched off.

For exampleBuild a key-value store with a write-ahead log, then survive a simulated power cut.

02

Reading

AI OFF

Engineers spend more time reading code than writing it, and reading is hardly taught. Juniors explain unfamiliar code, including code written by agents: what it does, where it fails, what they'd test. A senior listening learns exactly what they understand.

For exampleA live 30-minute explain-back on a codebase they've never seen.

03

Verification as a craft

AI OFF → OBSERVED

Given a change, how do you establish that it's right? Juniors hunt planted defects of increasing subtlety, from off-by-ones to isolation anomalies, write the test that breaks the change, and learn when not to trust a passing test.

For exampleA timed hunt on an agent-written PR with three hidden defects.

04

Specification

AI ON

Directing an agent well is mostly stating what is wanted, what constraints apply and how success will be recognised. Juniors specify, watch the agent build it, and find out from the result what they left unsaid.

For exampleWrite a spec, run the agent, then write a spec-gap retrospective.

05

Early ownership

AI ON

Each junior owns a small, real service from design to operation, with agents as their means, and is paged when it fails. A senior mentors with an explicit brief: ask questions, withhold answers.

For exampleTwelve weeks running a webhook relay with an SLO, a runbook and an on-call rota.

Incidents

Fortnightly game days with injected faults, real roles and blameless postmortems. Nothing teaches how systems fail like watching one fail.

Admissions for rate of learning

Curiosity, clear reasoning and plain writing predict growth better than familiarity with a framework, which is now the cheapest thing on the market.

Week
15913172124
  1. FND
  2. RDG
  3. VER
  4. SPC
  5. OWN
  6. INC
AI off: build the reference model AI on: direct and own Game days, fortnightly

What a week looks like

01

Work in the sandbox

Each exercise opens a real environment with a service, storage, planted defects or injected faults. AI tools are switched on or off per exercise.

02

Submit evidence

Code, tests, explanations, specs, runbooks. Automated checks run first, and every check states what it can't judge.

03

Explain it back

A senior asks questions from the exercise's question bank and withholds answers. That conversation is the real assessment.

04

Build a portfolio

Ratings on six competencies, with written evidence for each. The junior owns it.

For companies

An investment in the engineers you'll be shortest of.

  • ·The full curriculum: you don't need to hire a curriculum designer
  • ·Hosted sandbox, planted defects, fault injection and a logged agent
  • ·Your seniors review, ours do, or a mix
  • ·Capstones on real low-risk internal services, if you have them
  • ·Cohort analytics and a quarterly report written for your leadership

In a market where graduates have been told their profession is disappearing, a serious apprenticeship is also a strong reason to join you.

Join the January beta →

For senior engineers

Ask the questions that made you good.

  • ·Review submissions with rubrics and question banks already written
  • ·Run 30-minute explain-backs and mentor a capstone
  • ·Calibrated against other reviewers, so your ratings carry weight
  • ·Paid per review in open cohorts; recognised contribution in company ones

Your job is to ask and not tell. Most seniors take three or four juniors.

Become a founding reviewer →

For juniors

Become the engineer who can tell.

  • ·Build the mental models agents can't give you
  • ·Learn to read, verify and specify, the skills hiring is shifting toward
  • ·Own a real service and be on call for it
  • ·Leave with a portfolio rated by senior engineers

Through your employer, or through an open cohort.

See the programme for developers →

Design-partner beta

Two to three companies. Cohorts starting January 2027.

We're looking for engineering organisations that hire freshers or interns and are willing to commit senior time to teaching judgement. In return for pilot pricing, we ask for honest feedback, a reference and a 6-month follow-up with your managers.

  • →10–20 juniors or interns per cohort
  • →1 senior per 3–4 juniors, about 2 h a week each
  • →12-week intensive or 24-week standard
  • →Python, TypeScript or Go
  • Talk to us about the beta

Questions

Isn't banning AI tools backward?+

Only for the first weeks, and only for the fundamentals. It's arithmetic by hand for a child with a calculator: slow and artificial, and the only way to form the reference model that later judgement depends on. From week 9, agents are the main tool.

How much senior time does it take?+

About two hours per junior per week, covering reviews, explain-backs and mentoring. One senior can advise three or four juniors. This is the real cost of the programme, and we say so plainly. The curriculum, rubrics and question banks make that time count.

How is this different from a bootcamp or our fresher training?+

Most fresher programmes teach frameworks and how to build with AI. This one teaches judgement of what AI builds: reading, verifying, specifying and owning. It's measured on defects found, spec quality and how a service runs, not on course completion.

Which languages?+

Python, TypeScript and Go at launch, and Java next. Concepts are language-agnostic; every exercise ships as a variant in each language.

Can juniors join without an employer?+

Yes. Open cohorts are open to any junior who wants to join, reviewed by our network of senior engineers.