DevOps and Cloud Native Training
Corporate training on Kubernetes, DevOps and SecDevOps, built around your stack rather than a demo environment.
Why catalogue training often is not enough
A standard Kubernetes course teaches Kubernetes. That is useful, and it is also why certifications exist. But the following week participants go back to a cluster configured in its own particular way, with corporate constraints, inherited decisions and a pipeline that looks nothing like the one in the exercise. The gap between the example and reality is where most of the learning evaporates.
There is also a question of level. In nearly every group I train the internal spread is wide: two or three people already have experience, the rest are starting from zero. A single programme bores the former and loses the latter.
How I build a programme
Before defining the curriculum I talk to the technical leads and check the participants’ actual level, usually with a short questionnaire. It tells me how much time to spend on fundamentals and which topics can be assumed. It costs very little and noticeably changes how much the days deliver.
The programme alternates explanation and practice in short blocks. The lab part uses an environment aligned with yours: if you work with GitLab CI the lab is on GitLab CI, if your cluster runs on AKS the exercises run on AKS. That removes the mental translation step that usually prevents people from applying what they learned.
Sessions are spread over time where possible, rather than compressed into one intensive week. Between sessions participants try what they saw on real work, and the next session starts from the difficulties that surfaced. That is when the programme produces the most value.
What remains afterwards
Course material and recordings stay with the company and can be reused for future hires. A few weeks later I schedule a follow-up session dedicated to the problems the team ran into in the meantime: it is short, but it is the part that really consolidates adoption.
The experience behind these programmes is operational before it is didactic. I worked on the same problems as a DevOps Engineer, as a Cloud Native Engineering Manager and as a consultant, and the examples I use in the room come from there.
What's included
- Preliminary level check and goal setting with the technical leads
- Tailored curriculum, in English or Italian
- Hands-on labs on environments aligned with your stack
- Course material and recordings handed over to the company
- Follow-up session a few weeks later, on the problems that surfaced in between
Frequently asked questions
Which topics do you teach?
Kubernetes from fundamentals to production operations, Docker and containerisation, Terraform and Infrastructure as Code, CI/CD pipelines with GitLab CI and GitHub Actions, GitOps with Argo CD, secrets management with HashiCorp Vault, SecDevOps practices and Platform Engineering foundations. Tracks can be combined according to your goals.
Are courses delivered in English or Italian?
Both. For teams spread across countries I run sessions in English, with material in the same language.
How is this different from an off-the-shelf course?
The labs. A catalogue course uses a demo application that looks nothing like what participants manage every day, and the gap between the example and reality is where most of the learning is lost. The programmes I build start from your repositories and your tooling, so the work done in the room is directly reusable.
How long does a training programme take?
An introductory module on a single topic takes one or two days. A full Kubernetes track, from fundamentals to operations, typically runs across four or five days spread over time, so participants can apply what they saw between sessions.
Are courses delivered remotely or on site?
Both. Remote works well with groups of up to about ten people; on site is preferable when the programme includes working sessions on the team's concrete problems.
