Documented projects
Each with a short write-up: the problem, your approach, the trade-offs, the result, and how it was evaluated.
You don't build throwaway practice projects. You contribute to real, in-progress work — so what you graduate with is evidence you can do the job on day one.
Every build in a CapabilityNext programme is a genuine project: real requirements, real data, real constraints, and a real review. It's assessed the way a senior engineer reviews a pull request, not marked like a worksheet.
Each with a short write-up: the problem, your approach, the trade-offs, the result, and how it was evaluated.
A complete project on a real brief, demoed at a showcase. The piece you walk an interviewer through.
A practitioner who reviewed your work and can speak to how you think, not just that you attended.
It's structured to map onto what technical interviews actually ask about: architecture decisions, evaluation, cost, and what you'd change.
Requirements and data that look like the job.
Handle the messy parts, keep a write-up as you go.
Written notes plus a live review of your choices.
Demo it at a showcase and defend the trade-offs.
Before a programme runs, we work backwards from a real hiring need: the responsibilities, the tools, and what those interviews screen for. The curriculum, projects and capstone are shaped to that profile, so on completion you're ready for a specific kind of role and can start applying immediately. See the salary and skills map for each role →
Tuned to AI roles: technical rounds, take-homes, and how to present your portfolio.
A mentor goes through both with you before you apply.
Where we have them, we make them.
An honest caveat: we don't guarantee any individual offer. That still comes down to your interviews.
The kind of work that comes out of a cohort. These are illustrative examples of the standard we aim for, not named student projects.
RAG assistant over a long handbook, scored against a fixed test set of questions and held to a fixed cost per query.
End-to-end pipeline: feature store, containerised serving, drift alerts and an automated retraining trigger.
Detection + OCR pipeline turning scanned invoices into structured JSON, evaluated on a held-out set.
An example of the format every submission gets. Student stories will appear here once graduates have agreed to share them.
Clear separation of ingestion and query code, and a test set you built before tuning anything.
Chunk size was chosen once and never compared. Try two alternatives and report retrieval hit-rate for each.
Add a “can't answer from these documents” path and show how it behaves on out-of-scope questions.
Tick the courses you have taken to see how ready you would be for an AI/ML engineer role, and what it typically pays.
More roles on the career & salary map.
Tell us the role you're aiming for and we'll map it to a track.
Talk to an advisor