Bootcamp process
Five projects, four phases each.
The bootcamp is where the theory stops being theory. You take five briefs in your own technology and carry each one the way a delivery team would — scoped, designed, built and reviewed — with a trainer beside you rather than waiting at the end.
- 20
- hours of concentrated build time
- 5
- projects, rising to a full capstone
- 100%
- hands-on — nothing is demonstrated at you
Step by step
How every project runs
The same four phases each time. Five separate builds become one method you can repeat on the job — which is the actual thing an employer is buying.
- 1
Briefing and scope
Each project opens with a proper kick-off: what the thing has to do, the business reason it exists, which platforms and tooling the work sits on, and what counts as delivered. You get the reasoning, not just the task list — the same conversation a team has before any work starts.
- 2
Architecture and design
The shape before the code. You work through the infrastructure layout, how data moves, the deployment pipeline and the stack, and you argue for your choices out loud. It is the habit of thinking like the person who designs the system, not only the person who types it.
- 3
Build under supervision
The core of it — building, deploying and debugging with the trainer present and responding as you go. Feedback lands while the code is still warm, which is how the edge cases and the production-grade habits actually get learned rather than mentioned.
- 4
Review and defence
Every finished project is reviewed properly: the code, the architecture decisions, the documentation, and whether you can explain and defend the work you did. That last part is not a formality — it is the same skill an interviewer is testing when they ask what you built and why.
In detail
The five projects, in order
All five sit in the technology you enrolled in, so the portfolio you finish with is deep in one field rather than shallow across several.
01 · Foundations
A first build that puts the core concepts to work — environments configured, the basic workflows exercised, the fundamentals proven rather than assumed.
02 · Multiple moving parts
A larger solution with several components and an integration or two, applying the practices that are conventional in your stack rather than improvising.
03 · Architecture that scales
A design-led build: scalability, monitoring and the production-grade patterns your field actually uses, decided before they are implemented.
04 · An enterprise scenario
A realistic situation with services that depend on each other, security to harden and performance to tune — the kind of work that is waiting on the other side of the offer.
05 · Capstone
End to end, everything together: planned, designed, built, deployed and documented well enough to sit at the top of your GitHub profile.
What you get
What the fee covers
- Five briefed projects in your own technology, rising from foundations to capstone
- Twenty hours of guided build time with the trainer present throughout
- A live review of every project — code, architecture, documentation and your defence of it
- Work on the platforms employers actually run: AWS and Azure, Docker and Kubernetes, Terraform, CI pipelines
- A documented GitHub portfolio — real README files and a clean commit history, not a folder of exercises
- Morning and evening batches, so the bootcamp fits around work or study
This is the right starting point if
- You have the theory — from a degree, a previous course, or the job itself — and nothing shipped to show for it
- Your interviews go well until somebody asks what you have built
- You have just finished the training stage and want the applied half straight away
- You can already code but have never worked to a brief, a deadline and a review
Straight answers
What it is not
- Not a first introduction to the subject. It assumes the fundamentals are already there
- Not a watch-along. Every hour of it is you building, with somebody watching the work
- Not a placement service on its own — pair it with marketing if the goal is an offer
The bootcamp is the middle stage of pathways 1 and 2, and the opening stage of pathway 3 for anyone who already holds the theory. See the four pathways.
The rest of the programme