Remote-first private corporate batches in CET (UTC+1), onsite in Netherlands by arrangement — taught by a practitioner who runs DevOps in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches DevOps as platform engineering: golden paths and templated repositories, GitOps promotion with declarative environments, policy as code enforced before merge, signed artefacts with provenance and a bill of materials, and error-budget practice that decides when releases pause. Sessions run in CET, use the attendee's own repositories where the client allows it, and every control is demonstrated by breaking it live and watching the guardrail refuse the change.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For DevOps that means a trainer who has run it in production — platform engineering the Dutch way — golden paths, GitOps promotion, policy as code and a supply chain that survives an EU audit — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Onsite delivery in the Netherlands is a travel engagement with three to four weeks' lead time; the client provides the room, network access and a screen, the trainer brings the lab, materials and assessment, and travel and accommodation are itemised separately rather than absorbed into the day rate. Live online is the default and runs in CET (UTC+1) across a standard Dutch working day, with the window shifted where a team also spans India or the United States. Quotes are issued in EUR with INR retained as the source price; purchase orders and supplier onboarding are completed before the first session and VAT treatment is stated explicitly on the invoice. Batches run 8 to 30 engineers, and the agenda is rebuilt around your own cluster setup, policy tooling and compliance drivers during a discovery call.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private DevOps batchDevOps is the discipline of making software delivery a single, owned flow rather than a relay between departments. In the Netherlands that idea has already been absorbed and moved past: the interesting question in most Dutch organisations is no longer whether developers should run what they build, but how a small platform group gives forty product teams a paved road they will actually choose to use.
That reframes DevOps as a product problem. The platform team has internal customers, a backlog, an interface and a support burden. Its deliverables are golden paths — a templated repository, a pipeline that already knows how to build and sign, an environment that appears from a pull request — and its success is measured by adoption and by how much cognitive load it removes from the teams it serves.
Sitting under all of it is a regulatory floor that is unusually specific by international standards. Personal data handling under GDPR, security-incident and supply-chain obligations arriving through EU network-and-information-security rules, and operational-resilience expectations for financial entities all land in the same place: the pipeline. So Dutch DevOps work tends to combine developer-experience thinking with a level of evidence and provenance that many teams elsewhere only encounter during an audit.
The Dutch market has an unusually high density of platform and site-reliability roles relative to its size, and a labour market that mixes permanent teams with a large, mobile contractor population. That combination rewards standardisation: when a quarter of your engineers may rotate within eighteen months, an undocumented bespoke delivery path is an operational risk rather than a competitive advantage.
Regulation is tightening in the same direction. Supply-chain and incident obligations mean an organisation increasingly has to state where a binary came from, what was in it, and who approved its release. Provenance, signing and software bills of materials move from good hygiene to a documented control.
Meanwhile cost and energy are now engineering metrics rather than finance ones, with reporting obligations pulling infrastructure efficiency into the same conversation as sustainability disclosure. Engineers who can build a paved road, prove what it produced, and show that it runs efficiently sit at the intersection of three separate pressures — which is exactly why that profile is hard to hire here.
The operating model before the tooling. Who the platform's customers are, what the paved road promises, how support and on-call work between platform and product teams, and how adoption is measured rather than mandated.
Topics: Team topologies and the platform boundary · Defining the paved road and its promises · Platform backlog, interface and support model · Adoption metrics and developer experience surveys · Cognitive load as a design constraint · When to say no to a bespoke request
Making the right way the easy way. Repository templates and scaffolding, a pipeline that ships with the template, environment definitions generated rather than copied, and a versioning strategy for templates so improvements reach existing services.
Topics: Repository scaffolding and service templates · Pipelines delivered with the template · Generated environment definitions · Template versioning and update propagation · Service catalogue and ownership metadata · Documentation as part of the path
Declarative delivery with Git as the intended state. Repository structure for environments, reconciliation with Argo CD or Flux, promotion between environments as a reviewed change, secret handling in a declarative world, and what to do when a human changes something by hand.
Topics: Repository structure for environments and tenants · Reconciliation with Argo CD or Flux · Promotion as a reviewed pull request · Sealed and external secrets in a GitOps model · Drift detection and self-healing behaviour · Rollback by revert
Releasing without a change-freeze culture. Feature flags and their lifecycle, canary and blue-green strategies, automated rollback driven by service level indicators, and an error-budget policy that decides when the platform stops shipping.
Topics: Feature flags and flag debt · Canary and blue-green release strategies · Automated rollback on SLO burn · Defining SLIs and SLOs per service · Error-budget policy and release throttling · Incident review and corrective actions
Guardrails that fail fast. Writing policy in Rego or a policy engine of choice, testing policies like code, enforcing them before merge and again at admission, and handling exceptions without dismantling the control.
Topics: Policy engines and where they run · Writing and unit-testing policy · Pre-merge policy checks on infrastructure code · Admission-time enforcement in clusters · Exception handling with an expiry · Reporting policy violations without alert fatigue
Answering where a binary came from. Reproducible builds, dependency policy, software bills of materials, provenance attestation, signing and verification, and how those artefacts satisfy security-incident and supply-chain obligations landing across the EU.
Topics: Reproducible builds and pinned dependencies · Generating and storing an SBOM per release · Provenance attestation for build steps · Signing artefacts and verifying at deployment · Vulnerability triage and exploitability context · Mapping technical artefacts to regulatory obligations
GDPR obligations expressed as engineering practice. Test data that is not a copy of production, pseudonymisation and minimisation, log hygiene, retention as a pipeline concern, and the technical inputs an impact assessment actually needs.
Topics: Test data strategy without production copies · Pseudonymisation and minimisation techniques · Keeping identifiers out of logs and traces · Retention and deletion in pipelines and backups · Data-processing records from infrastructure code · Technical inputs to an impact assessment
Infrastructure economics as an engineering metric. Cost attribution per service, right-sizing from real utilisation, autoscaling and scheduling choices, spot and burst capacity, and the reporting that increasingly accompanies sustainability disclosure.
Topics: Cost attribution and tagging discipline · Right-sizing from utilisation data · Autoscaling and scheduling for efficiency · Spot, burst and workload placement · Energy and carbon reporting inputs · Making efficiency visible to product teams
We rebuild the agenda around the tools you actually run.
Request a custom agendaGenerate a new service from a template and reach a deployed, observable environment without writing pipeline code by hand — then version the template and propagate the change.
Build a GitOps repository for three environments, promote a release through review, then introduce manual drift and watch reconciliation put it back.
Add a canary stage driven by service level indicators, deploy a deliberately degraded build, and let the automation abort and roll back without human intervention.
Write and unit-test policy that blocks a non-compliant infrastructure change, enforce it pre-merge and at admission, then add an exception that expires.
Produce a signed artefact with a bill of materials and provenance attestation, verify it at deploy time, then trace a vulnerable dependency to the running services affected.
Assemble the golden path, GitOps promotion, guardrails and supply-chain evidence into one platform offering, and take a real service onto it end to end.
Engagements for the Netherlands come from a market that is small in headcount but unusually senior in composition. The recurring customers are payments and banking technology groups, logistics and transport platforms built around the ports and Schiphol freight flows, energy and grid operators, health-technology firms, high-traffic consumer platforms, and the European technology hubs of multinationals that chose Amsterdam or Utrecht for their EMEA engineering. Interconnection density is genuinely high here, which means latency-sensitive and traffic-heavy platforms are more common than the population would suggest.
The engineering culture shows up in the brief. Teams already run what they build, so the request is rarely a foundational DevOps course; it is platform engineering, GitOps promotion, policy as code and supply-chain evidence, delivered to people who will argue with you productively. Kubernetes is close to a default, contractor turnover makes documented golden paths a necessity, and compliance drivers — data protection, security-incident obligations, operational resilience for financial entities — arrive as engineering requirements rather than paperwork. Efficiency and energy reporting increasingly appear in the same conversation, because infrastructure cost and sustainability disclosure now share a data source in the Netherlands.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Helped to understand more on overall DevOps concepts.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.