Private corporate batches, live online cohorts and 1-on-1 mentoring in custom-built training on the tool you actually run, when it does not have a page of its own — 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
Rajesh has 20 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, and has trained more than 10,000 engineers. That breadth is what makes a custom engagement viable: most unlisted tools are a variation on a category — configuration management, artifact storage, CI orchestration, observability, secrets, service mesh, ticketing — and the transferable depth is in the category, the integration points and the failure modes, not the vendor's menu labels. Where a technology falls outside that range, we say so and decline rather than deliver a shallow course.
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 Others that means a trainer who has run it in production — custom-built training on the tool you actually run, when it does not have a page of its own — 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 Others batchOthers is the catch-all entry in the DevOpsSchool trainer directory — the page for the tool you run that does not have a page of its own. We publish detailed syllabuses for a few hundred technologies, and that still leaves out plenty: an internal platform, a niche vendor product, a language or framework we have not written up yet, a regional compliance tool, or a combination that only makes sense inside your organisation. This page exists so that request has somewhere to land instead of falling through a gap.
What we offer here is not a stock course with the name changed. It is a custom engagement: a discovery call to establish what your team runs and what they need to be able to do afterwards, a syllabus written for that, labs built against your topology, and delivery as a private batch onsite, live online or hybrid. If we do not have credible depth in the technology you name, we will tell you so rather than take the booking — that is the honest boundary on this page, and it is the reason the rest of it is worth reading.
The practical starting point is a short description of your stack: the tool or tools, the versions, what your team can already do, what they need to be able to do, and roughly how many people. From there we can usually say within a day whether we can deliver it well, what shape the course would take, and how long it would need. Use the enquiry form at the bottom of this page and tell us your stack — that is genuinely all we need to begin.
Every organisation runs something that no public course covers. It might be an in-house deployment platform, a vendor product with a small install base, a specialised protocol or standard, or an unusual combination of otherwise ordinary tools. Those are precisely the areas where knowledge is concentrated in two or three people, where onboarding is slowest, and where a departure is most expensive.
Generic training does not solve that. A public course on a nearby technology teaches concepts the team must then translate, and translation is where the value leaks out. What works is a syllabus built around the actual estate, with labs that use the actual topology and examples drawn from the actual failure modes the team has lived through.
There is also a timing argument. Custom training is most valuable at a transition — adopting a new platform, absorbing a team through reorganisation, taking a system back in-house from a vendor, or preparing for an audit. Those moments have a window, and a bespoke two- or three-day engagement inside that window is worth considerably more than a generic course six months later.
Before anything is written. A structured conversation about what you run, who is attending, what they can already do and what they must be able to do afterwards. This is where the course is actually designed — and where we tell you honestly if we are not the right people to deliver it.
Topics: Tool inventory: what you run and which versions · Current team capability and the gap to close · Target outcomes stated as capabilities, not topics · Attendee roles and prior background · Constraints: time, location, access, security review · Success criteria and how the engagement will be judged · Honest capability assessment and where we decline
Turning the scope into a course. We map the tool onto its category — configuration management, CI, artifact storage, observability, security, data — because that is where the transferable structure lives. Modules are sequenced along the natural learning progression, each with real topics, an assignment and a capstone, and the whole thing is reviewed with you before delivery.
Topics: Mapping an unlisted tool onto a known category · Sequencing modules along the learning progression · Depth calibration: awareness, working knowledge or ownership · Assignments and capstones per module · What to cut when the time available is shorter than the ideal · Vendor documentation, source code and internal runbooks as source material · Syllabus review and sign-off with your technical lead
Where the training becomes real. Attendees provision their own environment — free-tier cloud, local virtual machines or your own non-production estate — and we design the labs to run in it. Access, licensing, network restrictions and data handling all get settled before day one rather than eating the first morning.
Topics: Choosing between free-tier cloud, local VMs and your non-production estate · Licensing and trial access for commercial products · Network, proxy and firewall constraints in corporate environments · Test data: synthetic, masked or a sanitised extract · Pre-work so attendees arrive with a working environment · Lab repositories and reproducible setup scripts · What attendees keep afterwards
The first delivered module in almost every custom course. What the tool is, the problem it exists to solve, its architecture and components, how it is installed and configured, and where it fits in your estate — including an honest comparison with the alternatives and where it is the wrong choice.
Topics: The problem the tool solves and its position in the market · Architecture, components and data flow · Installation, configuration and initial setup · Core concepts and terminology · Comparison with alternatives, including where it loses · How it fits your existing architecture · Sizing, capacity and deployment topology
The work the tool exists to do, taught through the tasks your team performs every week. The primary objects and commands, the standard workflows end to end, configuration management and change control, and the operational tasks that are currently tribal knowledge.
Topics: Primary objects, commands and interfaces · The standard workflow end to end · Configuration structure and where settings actually take effect · Change control and safe modification in production · Routine operational tasks and runbooks · Automating repetitive work · Common mistakes and how they present
How the tool connects to everything else, and who is allowed to do what. Authentication and directory integration, role-based access, secrets handling, audit logging, and the APIs, webhooks and plugins that connect it to your CI system, ticketing, monitoring and identity provider.
Topics: Authentication and directory or identity-provider integration · Roles, permissions and least privilege · Secrets handling and credential rotation · Audit logging and evidence for compliance · APIs, webhooks and plugin or extension points · Integration with CI, ticketing, monitoring and alerting · Network exposure and hardening · Backup, restore and disaster recovery
The final module in most engagements. Monitoring and alerting, performance and scaling, upgrade and patch strategy, and a structured method for diagnosing failure rather than guessing. Then the handover: assessment, documentation, and how the team keeps the capability after the trainer leaves.
Topics: Monitoring, metrics and alerting for the tool itself · Performance tuning and scaling · Upgrade paths, patching and version strategy · A structured troubleshooting method for this specific tool · Reading its logs and diagnosing common failures · Documentation and knowledge transfer · Per-attendee assessment and capability reporting · Follow-up support and the forum
We rebuild the agenda around the tools you actually run.
Request a custom agendaA structured session with your technical lead to inventory the tools, versions, integration points and constraints, and to convert them into a syllabus with agreed outcomes.
Attendees provision their own environment against your constraints — cloud, local or non-production estate — with reproducible setup scripts they take away.
Each attendee completes the tool's primary workflow from a clean starting state without assistance, which is how capability is actually demonstrated rather than assumed.
Build a working integration between the tool and one other system you run — CI, ticketing, monitoring or identity — using its real API or plugin surface.
Work through a deliberately broken instance using logs and a structured method, find the root cause, fix it, and write the runbook entry.
The final exercise is built from a real requirement in your backlog, so what attendees produce during the course is something the organisation can actually use.
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
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.
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
| 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.