A certification you can fail.

AI-Native Delivery

Teams adopting AI-assisted engineering who want the throughput gain to survive contact with review and production.

Length

5 weeks, part-time

Commitment

~5 hours per week

Prerequisite

Working engineering team with a live codebase.

Modules

1. 01The transaction-cost argument — why generation getting cheap moves the constraint
2. 02Building verification capacity — trusted suites, fast pipelines, small changes
3. 03Review practice when the author did not type it — intent, invariants, accountability
4. 04AI in the pipeline — migration, test generation, triage, and which uses are traps
5. 05Provenance and governance — what a regulated estate has to be able to evidence
6. 06Re-baselining — measuring and reporting when throughput shifts under you

AI Engineering

Engineers building LLM applications, retrieval systems and agents who need them to hold up in production.

Length

8 weeks, part-time

Commitment

~7 hours per week

Prerequisite

Professional software engineering experience. Python or TypeScript.

Modules

1. 01Architecture of an LLM application — boundaries, state, failure behaviour
2. 02Retrieval that works — chunking, hybrid search, reranking, grounding and citation
3. 03Evaluation harnesses — golden sets, rubrics, LLM-as-judge and its failure modes
4. 04Testing non-deterministic systems and running evals in CI
5. 05Agents with bounded authority — permissioning, idempotency, blast radius, injection
6. 06Inference economics — routing, cascades, caching, context budgets, unit cost
7. 07Operating it — tracing, drift, incident response and model migration

Agentic Systems Engineering

Engineers building systems that act on their own, and the leads accountable for what those systems do unsupervised.

Length

7 weeks, part-time

Commitment

~6 hours per week

Prerequisite

AI Engineering certification or equivalent production experience with LLM systems.

Modules

1. 01What makes a system agentic — and the case for the workflow you already have
2. 02Architecture patterns — loops, routers, orchestrator-worker, and the cost of multi-agent
3. 03Tool design and MCP — interfaces built for a model rather than a human
4. 04Context engineering and memory — the scarce resource nobody budgets
5. 05Bounded authority — permissioning, reversibility tiers, human-in-the-loop, injection
6. 06Trajectory evaluation — replay harnesses, step and cost budgets as assertions
7. 07Operating one — sandboxing, durable execution, circuit breakers, and how to stop it

Web3 & Smart Contract Security

Engineers moving into contract development, and teams preparing a protocol for audit and mainnet.

Length

10 weeks, part-time

Commitment

~7 hours per week

Prerequisite

Strong general engineering background. Solidity familiarity helps but is not required.

Modules

1. 01Delivering software you cannot patch — moving iteration upstream
2. 02Solidity and the EVM execution model, written defensively
3. 03Stating invariants explicitly and checking them mechanically
4. 04Fuzzing, property-based testing and mainnet forking with Foundry
5. 05Vulnerability classes and adversarial review practice
6. 06Upgradeability, timelocks and multisig topology as trust decisions
7. 07Key management and operational security — where most real losses occur
8. 08Audit preparation — scoping, freezing, documenting, triaging findings

Mobile Delivery

Mobile teams whose release cadence is set by store review rather than by their own decisions.

Length

5 weeks, part-time

Commitment

~5 hours per week

Prerequisite

A shipping mobile application.

Modules

1. 01Store review as a transaction cost, and the release train that absorbs it
2. 02Decoupling shipping from revealing — flags, remote config, kill switches
3. 03Staged rollout with automated halt criteria tied to release health
4. 04Version fragmentation, API compatibility and forced upgrade
5. 05Release health instrumentation and acting on it

Practitioner

Scrum masters, product owners, tech leads and engineers running team-level delivery.

Length

4 weeks, part-time

Commitment

~5 hours per week

Prerequisite

None. Some delivery experience helps.

Modules

1. 01Align — outcome contracts, constraint registers and decision rights
2. 02Locate — value-stream mapping and building a flow baseline for your own team
3. 03Flow mechanics — WIP, batch size, queueing and the economics of delay
4. 04Engineering baseline — what has to be true technically for any of this to hold
5. 05Facilitation under pressure — planning, review and retro that change something

Lead

Delivery leads, engineering managers and coaches accountable for multiple teams.

Length

8 weeks, part-time

Commitment

~6 hours per week

Prerequisite

Practitioner certification or equivalent assessed experience.

Modules

1. 01Dependency mathematics — census, classification and elimination strategy
2. 02Team topology design — boundaries, interaction modes and cognitive load
3. 03Pressurise — designing a thin slice through real governance gates
4. 04Portfolio flow — measurement that survives an executive audience
5. 05Funding and demand management — intake, capacity and saying no
6. 06Coaching the system — working with managers rather than around them

Architect

Those designing an operating model: heads of engineering, transformation leads, CTOs.

Length

12 weeks, by nomination

Commitment

~6 hours per week plus a field engagement

Prerequisite

Lead certification and a live operating-model remit.

Modules

1. 01Diagnosis at organisational scale
2. 02Governance as pipeline design — evidence by default in regulated estates
3. 03Funding model change — project to product, and the CFO conversation
4. 04Wave design and the internal coaching cadre
5. 05Distributed and multi-vendor operating models
6. 06Designing the engagement to end — exit criteria and handover