Web Engineering
Full-stack developerBuild and deploy production web apps end to end: interfaces, APIs, databases, tests and release pipelines. The track most of our hiring partners recruit from.
16 weeksNext cohort 12 Jan
Cohort 24 opens 12 January
Write code. Ship products. Get hired.
A 16-week, project-first bootcamp. Live instruction, real client work and a career team that stays until you are hired.
Graduates now work at
Four tracks, one method
Pick the job you want, then train for it
Every track runs the same 16 weeks of guided builds, code review and interview practice. What changes is the stack you specialise in and the roles we aim you at.
Data Engineering
Data / analytics engineerMove data from messy sources into models a business can trust. You finish with a warehouse project built on real, live data instead of a sample CSV.
16 weeksNext cohort 12 Jan
Applied AI
AI / ML engineerGo past notebooks. You learn to fine-tune, evaluate and serve models behind a real API, and to argue about accuracy with evidence rather than vibes.
16 weeksNext cohort 12 Jan
Cybersecurity
Security analystAttack and defend a live lab network. You learn to triage alerts, hunt threats and write the incident reports a security team actually files.
16 weeksNext cohort 12 Jan
Sixteen weeks, six modules, one shipped product
Weeks 1 to 6 are shared across all tracks and get everyone writing and reviewing code at the same standard. From week 4 you split into your track and build toward a final project for a real client.
Weeks 1-6
Core craft
All tracks together
Weeks 7-12
Specialise
Track-specific build sprints
Weeks 13-16
Client project
Plus interview loop
Weeks 1-3 Programming foundations Read, write and debug code without copying from a tutorial
You start at the terminal and finish the module shipping a small tool you wrote yourself. Sixty percent of scheduled time is spent typing, not watching.
- Command line, Git and the debugging loop
- Data structures, functions and error handling
- Automated tests for your own code
Week 1 lab
// fetch live data and render one card per seat
const res = await fetch("/api/cohorts");
const cohorts = await res.json();
cohorts
.filter((c) => c.seats > 0)
.forEach((c) => renderCard(c));Weeks 4-6 Systems and collaboration Work on a shared codebase with other people in it
You join a team of four, take tickets on a shared repository and get your pull requests reviewed by an engineer who does this for a living.
- Branching, code review and resolving real conflicts
- Databases, queries and schema design
- Reading an unfamiliar codebase under a deadline
Code review standard
// a merged pull request needs three things
const review = {
tests: "passing, and actually testing behaviour",
naming: "a reader can guess what it does",
scope: "one idea per pull request"
};Weeks 7-9 Track sprint one Your specialisation stack, built from an empty folder
Two-week builds with a technical brief, a demo at the end and a written retro. Every sprint raises the bar on performance, testing or scale.
- Ship a working feature set on your track stack
- Benchmark and profile your own work
- Present a demo to the cohort and take questions
Sprint 1 brief
// deliverable: one service that survives review
function sprint(brief) {
return {
due: "10 working days",
review: "staff engineer",
demo: "15 minutes, live"
};
}Weeks 10-12 Track sprint two Production concerns: scale, safety, cost
This is where hobby-level work becomes professional. You add monitoring, handle failure paths, and cut a cloud bill you can explain line by line.
- Deployment, monitoring and rollback
- Security review of your own application
- Cost and performance trade-off decisions in writing
Definition of done
// a feature is not done until all four are true
const done = [
"deployed and reachable",
"logged and alerting",
"tested at its edges",
"documented for the next person"
];Weeks 13-15 Client project Scope, build and hand over software for a real organisation
Small teams take on a brief from a nonprofit or early-stage company: a discovery call, weekly check-ins and a handover meeting with the client in the room.
- Scope a brief you did not write
- Run a weekly client check-in and keep a decision log
- Hand over code, docs and a training session
Handover checklist
// the client keeps working after we leave
const handover = {
repo: "transferred to the client org",
runbook: "deploy, rollback, restore",
training: "two recorded sessions"
};Week 16 Portfolio and interview loop Turn sixteen weeks of work into offers
Career week runs alongside the final demos: a portfolio review, three timed mock interviews and a referral push into our partner network.
- Portfolio, resume and profile rewrite with a recruiter
- Three mock interviews: technical, systems, behavioural
- Warm introductions to hiring managers who hire juniors
What we ask partners for
// the ask is specific, not a mass application
const ask = "one interview slot for a graduate";Taught by people who still ship
Every instructor works part time in industry and teaches part time here. They review your code, not just your attendance.
Web Engineering
Camila Ferreira
Spent nine years on payments infrastructure before teaching. Writes the JavaScript curriculum from bugs she hit in production.
Previously Stripe
Data Engineering
Adaeze Oyelaran
Builds data platforms for streaming services. Runs the warehouse project on live traffic data instead of a static sample set.
Previously Spotify
Applied AI
Elena Kowalczyk
MSc in machine learning, now shipping recommendation models. Teaches evaluation first, model architecture second.
Previously Ocado Technology
Cybersecurity
Amir Haddad
Runs incident response for a managed security provider. Keeps the teaching lab deliberately breakable so students learn to triage.
Previously Mandiant
Graduates, in numbers
We publish outcomes for every cohort, including the ones that disappoint. Figures below cover graduates who opted in to be counted.
87.4%
Placed in a technical role within 90 days of graduating
$96,400
Median starting salary across all four tracks, US dollars
1,184
Graduates since the first cohort in 2019
41
Hiring partners who interview our graduates each cohort
- Web Engineering
- $98,000
- Data Engineering
- $92,500
- Applied AI
- $112,000
- Cybersecurity
- $101,000
Median first-year base salary reported by graduates, three most recent cohorts. Sample data supplied with this template. Replace with your own verified outcome reporting before launch.
Eighteen seats. One start date.
Applications are reviewed on a rolling basis and the cohort closes when it fills. Applying takes about fifteen minutes and there is no technical test to sit.
- Next cohort starts
- 12 January
- Format
- 16 weeks, full time
- Where
- San Francisco, on campus
- Tuition
- $14,900
- Payment
- Upfront, monthly or income share
- Scholarships
- Six per cohort, need based
Get the full syllabus
Tell us which track you are considering and we will send the week-by-week breakdown, tuition options and the cohort calendar.
Syllabus on its way
Check your inbox in the next few minutes. If it has not arrived, look in spam for a message from admissions.
I came from retail management and had never opened a terminal. Five months later I was shipping React to production and reviewing other people's pull requests.
The warehouse project used our client's live data, so it broke constantly. Learning to fix that in front of the client is the part interviews dug into.
Career week was relentless in the best way. Resume rewritten, three mock interviews, and two warm introductions that both turned into offers.
The AI track assumes you can already code and then pushes hard on evaluation. My capstone model is still running in their production system.
Testimonials are sample content shipped with the template. Swap in your own graduate quotes and photos.