Private corporate batches, live online cohorts and 1-on-1 mentoring in day-by-day training structure — session pacing, cognitive load, lab time budgets, multi-day arcs, capstone placement and recovery when a day overruns — 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 builds a daywise plan for every private engagement before the first session: a time budget per block covering demonstration, hands-on work, questions and recovery; environment setup verified before day one rather than discovered on it; each day opening with reinforcement of the previous one; and a named cut list so an overrun costs optional material instead of the capstone. Twenty years across DevOps, SRE and Security and 10,000+ engineers trained across corporate batches inform the pacing decisions that matter — where the hard module belongs inside a week, how much lab time a task genuinely needs against how much it was estimated to need, how to keep a mixed-ability group together with stretch and catch-up work, and how a five-day onsite block is restructured into half-days across timezones without losing the arc.
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 Daywise that means a trainer who has run it in production — day-by-day training structure — session pacing, cognitive load, lab time budgets, multi-day arcs, capstone placement and recovery when a day overruns — 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 Daywise batchA daywise plan is the layer between an agenda and a delivered course. The agenda says which modules exist and in what order; the daywise plan says what happens between nine and five on each specific day — which module starts when, how long the demonstration runs before people touch a keyboard, where the labs sit, when the breaks fall, and what gets cut if the morning overruns. Without it, an agenda that looks sound on paper turns into a first day where environment setup eats four hours and a final day that sprints through the material everyone actually came for.
The daywise view exists because attention and capacity are finite in a way that a topic list does not show. People absorb dense conceptual material better in the morning and hands-on work better after lunch. A day with no practice does not stick; a day with nothing but practice does not generalise. Three consecutive days of new concepts produce a group that has stopped retaining anything by the third afternoon, whatever the feedback form says.
A good daywise plan is therefore an explicit set of decisions rather than a timetable printed after the fact. It allocates a time budget to demonstration, hands-on work, discussion and recovery; it front-loads the environment so day two does not inherit yesterday's broken setup; it places reinforcement of the previous day at the start of the next one; it names, in advance, which content is optional and which is load-bearing when time runs short; and it positions the capstone with enough runway that it is actually finished rather than described.
Multi-day technical training is expensive in a way that is easy to underestimate. Twenty engineers offline for a week is a week of delivery capacity, and the sponsor who approved it will ask what changed. The most common reason nothing changed is not weak content — it is a delivery plan that ran out of time on precisely the material that would have transferred.
Remote and hybrid delivery has made the problem sharper. A schedule designed for a room does not survive being moved to video: attention spans compress, the informal debugging help that used to happen over a shoulder disappears, and a five-day block often has to become ten half-days spread across two weeks in a timezone that suits three offices. That is a different plan, not the same plan delivered through a webcam.
There is also a fairness argument inside the room. A mixed-ability group is normal, and a plan with no slack punishes the slowest quarter and bores the fastest. Building in stretch tasks, catch-up windows and an explicit cut list is what allows one trainer to keep a spread of experience levels moving together instead of optimising for the middle and losing both ends.
The artefact itself. What a delivery plan has to state beyond a timetable — objectives per day, block-level time budgets, prerequisites due before each day, environment checkpoints, the cut list and the contingency — and how it relates to the agenda it implements.
Topics: Agenda versus daywise plan: two different documents · Per-day objectives and the end-of-day check · Block structure and time budgets · Prerequisites due before each day · Environment checkpoints and readiness gates · Cut lists, optional content and stretch content · Contingency and recovery slots · Who the plan is written for: trainer, sponsor and attendee
Why plans overrun, expressed as capacity rather than as a scheduling error. How much genuinely new material a group can take in a day, why demonstration time and lab time are not interchangeable, and how to estimate a hands-on task without the optimism that causes every overrun.
Topics: Cognitive load and the limits of new material per day · Attention across a day and across a week · Estimating lab duration honestly, and why estimates are consistently low · Demonstration, guided practice and independent practice · Spacing, interleaving and retrieval practice · Break structure and its effect on retention · Signals that a group has stopped absorbing · Adjusting pace in flight without abandoning the plan
The day that most often goes wrong. Getting every attendee to a working environment without spending the day on it, reading the real baseline of the group rather than the assumed one, and reaching a first genuine result early enough that people believe the week will be useful.
Topics: Pre-delivery prerequisite verification and who owns it · Setup strategies: pre-provisioned, guided, or containerised fallback · Handling the attendee whose machine will not cooperate · Baseline assessment without making anyone defensive · Reaching a first working result inside day one · Setting expectations, ground rules and the cut list openly · Late joiners and partial attendance · What must be true at the end of day one
Designing the hours between start and finish. Opening with reinforcement, placing the hardest conceptual block where attention is highest, protecting hands-on time from being borrowed, positioning the post-lunch slot deliberately, and closing with a check that shows whether the day landed.
Topics: Opening: reinforcement and reconnection to yesterday · Block sequencing across morning and afternoon · Placing the hardest material where attention allows · Protecting lab time from demonstration overrun · The post-lunch block and what belongs in it · Question handling: inline, parked, or end-of-block · End-of-day check and consolidation · Homework and overnight work: when it helps and when it backfires
How days connect. Dependency between days, deliberate spacing and revisiting so material consolidates, building the capstone in stages across the week instead of announcing it on the last afternoon, and designing the final day to finish rather than to introduce.
Topics: Dependency mapping across days · Spacing and deliberate revisiting of earlier material · Progressive capstone: building it in stages from day two · Reserving the final day for completion and consolidation · Where to place the hardest day within a week · Fatigue management across four and five day blocks · Handling absence: catching up a day that was missed · Closing: review, next steps and post-course support
The same content in different shapes. Converting a contiguous onsite block into half-days across two weeks, running across timezones, part-time evening delivery for teams that cannot go offline, and the specific adjustments each format requires rather than a straight copy of the schedule.
Topics: Contiguous onsite blocks: strengths and constraints · Split-day online: half-day structure and continuity · Timezone-spread delivery across multiple offices · Part-time and evening formats for teams that stay operational · Hybrid delivery with remote and in-person attendees together · Remote hands-on support and screen sharing discipline · Recording, catch-up and asynchronous work between sessions · Choosing a format with the sponsor rather than for them
Closing the loop. Where checks belong across the days rather than only at the end, how to recover a day that has overrun without damaging the outcomes, keeping a mixed-ability group together, and measuring afterwards whether the plan itself needs changing.
Topics: Formative checks distributed across days · Where the summative assessment belongs · Recovery: cutting, compressing and rescheduling in flight · Mixed ability: stretch tasks, catch-up windows and pairing · Reading the room and reallocating time honestly · Feedback collected per day rather than only at the end · Post-course measurement of transfer · Revising the daywise plan for the next delivery
We rebuild the agenda around the tools you actually run.
Request a custom agendaTake a module-level agenda and produce a full day-by-day plan with block timing, objectives, prerequisites, environment checkpoints and a named cut list.
Estimate a hands-on exercise, then run it with real attendees and measure the gap — including setup, the question that derails everyone and the two people who finish first.
Design a first day that gets every attendee to a working environment and a first real result, including a fallback for the machine that refuses to cooperate.
Restructure a course whose capstone starts on the final afternoon into a staged build across the week, and prove the earlier days supply what each stage needs.
Convert a contiguous onsite plan into split-day online delivery across two weeks and three timezones, adjusting continuity, recap and asynchronous work.
Present a full delivery plan for a real engagement — day objectives, block timing, checks, stretch and catch-up work, cut list and contingency — and defend every timing decision.
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
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.
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.
| 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.