Apply Now
Home · Curriculum

Curriculum

Sixteen weeks, four phases. Filter by track to see what each week actually covers.

Weeks 1–2 · Foundations

Command line, Git, HTTP and how the internet actually moves a request. Everyone takes this, whatever the track.

shared_core
weeks 1–2

Week 15 · Interview Practice

Live technical interviews with engineers from partner companies, recorded and reviewed with you.

shared_core
week 15

Week 16 · Demo Evening

You present your client project to a room of hiring managers. Attendance is not optional.

shared_core
week 16

Weeks 3–5 · JavaScript & TypeScript

The language properly: closures, async, types. Most bugs later on are a gap from these three weeks.

full_stack
weeks 3–5

Weeks 6–8 · React & State

Components, hooks, data fetching, and the state decisions that decide whether an app stays maintainable.

full_stack
weeks 6–8

Weeks 9–10 · Node, Postgres & APIs

Building the back end your front end has been mocking, then replacing the mocks.

full_stack
weeks 9–10

Weeks 11–14 · Client Project

A real brief from a partner company, in a team of four, with a real deadline and a real stakeholder.

full_stack
weeks 11–14

Weeks 3–5 · Python & SQL

Python for data work and SQL beyond SELECT — window functions, CTEs and query plans.

data_track
weeks 3–5

Weeks 6–8 · Analysis & Visualisation

pandas, statistics that survive contact with a stakeholder, and charts that do not mislead.

data_track
weeks 6–8

Weeks 9–10 · Machine Learning

Regression, classification, evaluation. When a model is the answer and when a query is.

data_track
weeks 9–10

Weeks 11–14 · Deployed Project

A model behind an API, monitored, with the data pipeline that feeds it. Not a notebook.

data_track
weeks 11–14

Weeks 1–6 · Linux & Networking

Evenings. The layer everything else sits on, taught before any cloud console is opened.

cloud_track · part_time
weeks 1–6

Weeks 7–12 · Containers & CI/CD

Docker, pipelines, and making a deployment boring enough to do on a Thursday afternoon.

cloud_track · part_time
weeks 7–12

Weeks 13–18 · AWS & Terraform

Infrastructure as code, cost control, and what to do at 2am when it is on fire.

cloud_track · part_time
weeks 13–18

Weeks 19–24 · Production Project

Take an existing app and make it observable, resilient and cheap. In that order.

cloud_track · part_time
weeks 19–24
FAQ

The questions we get every intake

No, and most of our graduates do not have one. What you do need is to have written some code before applying — a finished tutorial is enough. We will tell you straight if you are not ready yet, and what to do about it.

No. Eighty-one per cent of our graduates are hired within six months and we publish that figure with its methodology. Anyone offering a guarantee is either pricing the risk into your fee or defining "job" generously.

Not on the full-time track — it is nine to six with evening work on top. The cloud track is deliberately part-time for exactly this reason and runs over twenty-four weeks instead.

You get extra sessions at no cost, and if it is not working you can defer to the next cohort once, free. About one student in ten does this and most of them finish strongly.

Yes — six monthly instalments at no interest, or a deposit plus deferred payment starting three months after you are employed. Both are on the application form and neither costs more than paying upfront.