Private corporate batches, live online cohorts and 1-on-1 mentoring in remote instructor-led technical training — platform and toolchain, lab access, engagement, assessment and multi-timezone delivery — taught by a practitioner who runs it 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
This programme is taught from the delivery side, by a practitioner who has run technical training remotely to distributed engineering teams at scale — 10,000+ engineers trained across DevOps, SRE and security subjects. It covers the mechanics that decide whether a remote session works: getting a lab environment reachable through corporate network restrictions on day one, session length and checkpoint rhythm, breakout facilitation, handling the wide skill spread that appears in every corporate batch, recording and follow-through, and scheduling across timezones without one region permanently drawing the worst slot. Every technique is demonstrated by running the course itself the way it teaches.
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 Online that means a trainer who has run it in production — remote instructor-led technical training — platform and toolchain, lab access, engagement, assessment and multi-timezone delivery — 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.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
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 Online batchOnline instructor-led training is live, scheduled technical teaching delivered over a conferencing platform with hands-on work happening in parallel — not recorded video, and not a webinar. The distinction matters because the failure modes are completely different. A recorded course fails when the content is wrong. An online live session fails when the trainer cannot see that half the group has been stuck on step four for twenty minutes.
What actually makes it work is a small number of concrete mechanisms. A platform configured deliberately — breakout rooms, chat that someone is watching, screen sharing at a resolution where terminal text is legible, recording that starts automatically. A lab environment every attendee can reach on the first morning, which is the single most common point of failure, usually because corporate laptops block what the labs need. A rhythm that alternates short demonstration with hands-on work rather than an hour of slides. A second channel — a persistent chat space — where questions accumulate without interrupting. And explicit checkpoints, because in an online session silence means nothing at all.
The organisational side is equally practical. Sessions have to be scheduled across timezones without one region always taking the unpleasant slot, split across days rather than run as an eight-hour block, recorded and hosted so absentees and the rest of the organisation can use them, and assessed so somebody can report whether the training worked. Getting those right is what separates online delivery that produces measurable capability from online delivery that produces attendance.
Distributed engineering teams are now the default rather than the exception, and the training that supports them has had to follow. A team of twenty spread across four countries cannot be brought together for a week, and increasingly there is no budget to try — so the choice is between live remote delivery and self-paced video that most people never finish.
The quality gap between those two options is large and widening. Live remote training done well produces better outcomes than in-person for technical subjects, because every attendee works on their own machine in their own environment, everything is recorded, and the chat channel captures questions people would never ask out loud. Done badly it produces an eight-hour video call with muted cameras and nothing learned. The difference is almost entirely mechanical: lab access, session length, checkpoint discipline and facilitation.
Most organisations also run far more internal enablement than they realise. Onboarding, platform adoption, migration training, security awareness, brown-bag sessions and internal certification are all training, usually delivered by engineers who were handed a deck and no method. Teaching those people how remote instructor-led delivery actually works is one of the cheapest capability investments an engineering organisation can make.
The honest inventory of what you lose, what you gain and what has to be replaced by an explicit mechanism. Attention and the shorter online attention span, the loss of peripheral awareness, the gain of every attendee working in their own environment, and the formats that translate badly.
Topics: Live online versus recorded video versus webinar — three different products · What the trainer loses: peripheral awareness, informal questions, over-the-shoulder help · What the attendee gains: own machine, own environment, recording, chat · Attention spans and the case against the eight-hour day · Formats that translate badly and what replaces them · Cameras, presence and what you can reasonably require · Setting expectations with attendees and their managers before day one
The concrete setup. Choosing and configuring a conferencing platform for teaching rather than for meetings, the persistent chat channel that carries questions and links, screen sharing where terminal text is actually readable, and the trainer's own hardware and network — the failure of which stops everything.
Topics: Conferencing platform selection and the features that matter for teaching · Breakout rooms, polls, reactions and hand-raising as teaching instruments · The persistent chat channel: Slack, Teams or the platform's own · Screen sharing: resolution, font size, terminal legibility, dual screens · Recording setup, storage and automatic capture · Trainer hardware: audio first, camera second, network third · Backup plans for platform, network and power failure · Collaboration surfaces: shared documents, whiteboards, code sharing · Accessibility: captions, transcripts, colour and contrast
Course design, not slide design. Deriving objectives from what attendees must be able to do afterwards, building modules around a demonstration-and-practice cycle, sequencing so each hands-on block depends only on what has been covered, and cutting the material that exists only because it was in the original deck.
Topics: Objectives written as capabilities, not topics · Module structure: demonstrate, practise, check, consolidate · Timing: how much material actually fits in a remote day · Sequencing so no lab depends on uncovered material · Designing exercises that fail informatively · Assignments and a capstone that proves capability · Prerequisites and pre-work that people will genuinely do · Handling mixed skill levels within one design · Materials: slides, lab guides, repositories and what each is for
The module with the highest failure rate in real delivery. Choosing between attendee-provisioned cloud accounts, local containers and hosted environments; getting through corporate proxies, VPNs and locked-down laptops; and the pre-flight check that finds those problems before the first session rather than during it.
Topics: Attendee-provisioned cloud accounts versus hosted sandboxes — the real trade-off · Local environments: Docker, virtual machines, dev containers · Cloud development environments and browser-based terminals · Corporate laptops: proxies, VPNs, blocked ports, admin rights, antivirus · The pre-flight check and how to make people actually run it · Cost control on attendee-owned cloud accounts · Lab guides that work when the trainer is not looking over a shoulder · Sharing a broken environment for diagnosis without screen-sharing chaos · Resetting, restarting and recovering a broken lab mid-session · What attendees keep after the course ends
Running the room when you cannot see it. Checkpoint techniques that produce real signal, managing the chat channel as a second stream, breakout rooms that are worth the disruption, helping a stuck attendee without stalling everyone else, and assessment that measures capability rather than attendance.
Topics: Explicit checkpoints and why silence means nothing · Polls, reactions and quick-fire questions as signal · Managing chat as a parallel channel without losing the main one · Breakout rooms: sizing, briefing, timing, returning · Pair and mob exercises remotely · Helping one stuck attendee without stalling the group · The dominant participant and the silent one · Energy, breaks and pacing across a full day · Assessment: quizzes, code review, capstone evaluation · Feedback collection that produces actionable change
The logistics that quietly determine whether people attend. Splitting a course across days rather than running a marathon, finding overlap windows that do not always punish the same region, cohort sizing, and running the same programme repeatedly across regions without the quality drifting.
Topics: Day length, session blocks and break structure · Finding a fair overlap window across three or more regions · Rotating unfavourable slots rather than fixing them on one region · Split-cohort delivery when no overlap exists · Cohort size and its direct effect on hands-on support · Public holidays, release freezes and scheduling around delivery pressure · Attendance, calendar discipline and manager commitment · Running the same programme across regions consistently · Coordinating co-trainers, moderators and lab assistants
What happens after the session, which is where most training value is lost. Producing recordings people actually use, hosting material so it survives the quarter, supporting attendees while they apply what they learned, and reporting outcomes in terms a sponsor will accept.
Topics: Recording quality, editing effort and what is worth the time · Chaptering, indexing and making a recording searchable · Hosting: LMS, internal wiki, video platform and access control · Lab repositories and keeping them working after the course · Post-course support: office hours, forums, follow-up sessions · Reinforcement: spaced follow-up and applied assignments · Measuring outcomes beyond a satisfaction score · Reporting to the sponsor who paid for the training · Building an internal training capability that outlasts one trainer
We rebuild the agenda around the tools you actually run.
Request a custom agendaConfigure platform, chat, recording, screen share and audio, then run a demonstration while deliberately failing your primary network and recovering.
Write and run a pre-flight check against a locked-down machine, then get a simulated distributed group into a working lab environment against real network restrictions.
Take an existing module, rewrite its objectives as capabilities, remove everything that does not serve them, and re-time it against a real novice.
Deliver a full teaching block including demonstration, hands-on work, three checkpoints and a facilitated breakout, then receive structured feedback.
Build a multi-day schedule across three regions with rotating slots, moderator roles, cohort sizing and a contingency for a trainer being unavailable.
Deliver the complete package: curriculum design, lab access plan, schedule, delivery method, assessment, recordings and an outcome report for the sponsor.
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
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
I was looking to improve my understanding of AIOps, and this training helped me achieve that goal. Rajesh Kumar explained the subject in a structured and practical manner. The sessions on different AIOps concepts were informative.
| 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.