Four tracks. Three entry levels each.
A track is the outline we start from. After profiling, the cohort gets its own plan: modules cut or added, the order changed, and the cloud, languages and tools named. These pages show what a typical plan covers.
Developer
Write software that survives production.
For people starting as developers and for developers who want to own what they ship. Language and framework are chosen per cohort. The engineering habits are the same everywhere.
who applies
- Career switchers with some coding exposure who want a first developer job
- Junior developers who have never run their own code in production
- Developers who inherited the build, deploy and monitoring and want to understand it
- Testers, analysts and support engineers moving into development
entry levels
- FoundationsYou have written some code in courses, scripts or personal projects, but never worked in a team codebase.
- Working developerYou ship features, but deploys, pipelines and incidents happen to you rather than by you.
- Senior / leadYou lead features or a small team and want to raise the engineering bar.
DevOps & platform
Build the pipeline, the infrastructure and the on-call that comes with it.
For people moving into DevOps from support, sysadmin or development, and for DevOps engineers moving toward platform and SRE work. Cloud provider and tooling are chosen per cohort.
who applies
- Support and helpdesk engineers who want to move into infrastructure
- System administrators moving from hand-managed servers to cloud and infrastructure as code
- Developers asked to own CI/CD and Kubernetes
- DevOps engineers moving toward platform engineering and SRE
entry levels
- EntryYou know Linux basics and some scripting, but have not run CI/CD or cloud infrastructure yourself.
- DevOps engineerYou run pipelines and some cloud already, mostly learned on the job, with gaps you can feel.
- Platform / SREYou want to design platforms other teams build on and own reliability for them.
Security
Make security part of the engineering job, not a department down the hall.
For engineers and administrators who need to harden, detect and respond, and for people moving into security engineering. Defensive, hands-on, built on real stacks.
who applies
- System administrators and DevOps engineers who own security without a security team
- Developers who need application security beyond a checklist
- IT staff moving into a security engineer role
- Security analysts moving from tickets to engineering
entry levels
- EntryYou run systems or write code, and security is something you hear about after the fact.
- Security engineerYou already handle vulnerabilities and audits and want structure and depth.
- Senior / leadYou are building a security function and need it to stick with the engineering teams.
Systems administration
Run Linux systems, networks and storage like they matter. They do.
For people entering systems administration and for administrators moving to automation, virtualisation and hybrid cloud. Everything is done on real machines first, then automated.
who applies
- IT support and helpdesk staff moving to server administration
- Windows administrators adding Linux
- Administrators who run everything by hand and need automation
- Small-company IT generalists responsible for servers, networks and backups
entry levels
- EntryYou use Linux a little and support users, but have not built and run servers yourself.
- SysadminYou run servers already and want to stop doing things by hand.
- Senior / infrastructure engineerYou own the whole environment and are moving it toward hybrid cloud.
Not sure which track?
Choose “not sure” when you apply. The profiling call maps your skills against all four and we recommend one, with the reasons written down.
Tell us where you want to get to.
Applying takes five minutes. Profiling is free and you keep the skills map. The cohort, the plan and the price come before any commitment.
Cohorts are forming now for all four tracks. We reply within two working days.