Private corporate batches delivered onsite across Chennai, or live online in IST (UTC+5:30) — 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 for build-heavy estates: repository strategy for large, long-lived codebases, build caching and agent capacity that cut a ninety-minute cycle, test selection and flake triage for large suites, containerising an established Java estate without rewriting it, and release traceability from requirement through commit and build to the artefact that shipped. Sessions run live against a working pipeline, and Chennai batches are scheduled in IST around release and shift calendars rather than in spite of them.
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 — delivery engineering for build-heavy product and manufacturing estates — long builds, test farms, shift operations and traceable releases — 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 Chennai runs at your own office, with the OMR corridor from Perungudi through Sholinganallur, Siruseri, Guindy, Taramani, Ambattur and Porur covering most engagements; travel within the city is included in the quote and only outstation travel to a plant or a second location is itemised. You provide the room, network access and a screen, and the trainer brings the lab, materials, assessment and certificates. Live online delivery runs in IST (UTC+5:30) and is often preferred where a team splits across two sites. Batches run 8 to 30 engineers and are commonly scheduled as two blocks rather than a continuous week so a release window is not disturbed, with a repeat sitting where operations staff work rotating shifts. Quotes are issued in INR with GST applied and purchase orders supported.
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 practice of making software delivery one continuous, owned flow rather than a sequence of departmental hand-offs. The Chennai version of that problem has a distinctive character, because a large share of the engineering here is not a web service that deploys forty times a day. It is telecom and networking software, embedded and automotive systems, enterprise product suites, and the platforms that sit alongside factories and supply chains — codebases where a full build takes hours and a release is coupled to hardware, a plant calendar or a customer's own upgrade window.
In that setting the DevOps questions change. Feedback speed is dominated by build and test time rather than deployment time, so caching, incremental builds, agent capacity and test selection matter more than another deployment strategy. Traceability matters more than throughput, because a release may have to be tied back to a requirement, a test result and an approval for a customer or a quality process.
The practices are still the standard set — version control at scale, continuous integration, artefact management, configuration as code, containerisation and observability. What earns its place in a Chennai engagement is the ability to apply them to a large, long-lived codebase with real hardware dependencies, and to leave behind a pipeline that stays fast as the codebase and the team keep growing.
Chennai's engineering employment is anchored in organisations that build products rather than only operate them: network equipment and telecom software, automotive and component engineering, enterprise product suites, healthcare and insurance platforms, and captive centres doing genuine research and development rather than support. Those organisations are all under pressure to release more often without loosening the quality obligations that come with shipping to enterprises, regulators or physical products.
That produces a very specific hiring pattern. Teams are not looking for someone who can install a CI server; they already have one, usually several, and often a build that has quietly grown to ninety minutes. They are looking for engineers who can cut feedback time on a large codebase, keep a test farm honest, containerise services that were written long before containers, and prove what went into a release.
Demand is also being pulled by the shift to product-line delivery across manufacturing and mobility employers in Tamil Nadu, where software increasingly ships with the physical product. Getting a release wrong there is expensive in a way it is not for a consumer application, so the premium sits on discipline and evidence rather than raw speed.
Measuring before changing. Instrumenting the delivery path on a real codebase, separating build time from queue time from test time from approval waiting, and choosing the change that returns the most feedback speed per unit of effort.
Topics: Instrumenting the delivery path end to end · Queue time versus execution time · Where approvals and hand-offs add latency · Baseline metrics for a large codebase · Prioritising by return rather than novelty · Setting a realistic target for cycle time
Repository strategy when the code is older than the team. Monorepo against multi-repo trade-offs, submodules and vendored dependencies, large binary handling, keeping history usable, and a branching model that supports both mainline work and supported customer releases.
Topics: Monorepo and multi-repo trade-offs at scale · Submodules, subtrees and vendored dependencies · Large file handling and repository size · Long-lived support branches and backporting · Review load and ownership on a large codebase · Migrating history without losing traceability
The module that usually pays for the course. Dependency and build caching, incremental and remote builds, agent pools and ephemeral workers, reproducible toolchains, and artefact retention that does not fill the disk every quarter.
Topics: Dependency and build caching strategies · Incremental and parallel builds · Agent pools, labels and ephemeral workers · Reproducible toolchains and pinned versions · Artefact repositories and retention policy · Diagnosing a build that is slow for the wrong reason
Large suites and shared hardware. Which tests run on which trigger, parallel execution and sharding, quarantine and flake triage, managing shared rigs and licensed tools, and separating gated tests from nightly ones.
Topics: Test selection by change impact · Parallel execution and sharding · Flake detection, quarantine and triage · Shared hardware and licensed tool scheduling · Gated versus nightly suites · Reporting test health as a first-class metric
Moving long-lived services into containers without a rewrite. Image design for legacy applications, externalising configuration, memory and thread settings that behave under container limits, service dependencies, and an honest assessment of what should not be containerised.
Topics: Image design for established applications · Externalising configuration and secrets · Runtime settings under container limits · Handling stateful and licence-bound components · Service dependencies and start-up ordering · What to leave on virtual machines and why
Recreating environments instead of repairing them. Infrastructure as code for test and staging, configuration management for the virtual machine estate, seeded test data, and environment lifecycle so integration environments stop being scarce shared resources.
Topics: Infrastructure as code for test environments · Configuration management for the existing estate · Test data seeding and refresh · Environment lifecycle and reclamation · Environment parity with production · Removing the shared-environment bottleneck
Releasing alongside plants, customers and support commitments. Release calendars against plant and customer windows, staged rollout, rollback rehearsal, and observability designed for operators working rotating shifts rather than for engineers reading dashboards.
Topics: Release calendars against plant and customer windows · Staged rollout and canary in a constrained estate · Rollback rehearsal and decision criteria · Alerting tuned for rotating shifts · Runbooks and shift handover · Incident review that produces corrective actions
Proving what shipped. Linking requirement to commit to build to test result to approval, generating release notes and bills of materials automatically, retaining evidence for the life of a product, and preparing for a customer or quality audit.
Topics: Requirement and issue linkage in commits · Automated release notes and change logs · Bill of materials per release · Retaining evidence across a product lifetime · Access and approval records · Preparing for a customer or quality audit
We rebuild the agenda around the tools you actually run.
Request a custom agendaProfile a slow build on a real project, then attack it with dependency caching, incremental compilation, parallelism and agent changes — and prove the improvement is repeatable.
Introduce impact-based selection and sharding on a big test suite, detect and quarantine genuine flakes, and publish a test-health report the team will trust.
Containerise an established application, externalise its configuration, tune runtime settings under memory limits, and prove parity against the original deployment.
Create a full test environment from code with seeded and masked data, run a suite against it, then destroy it and recreate it identically.
Automate release notes and a bill of materials, then reconstruct the complete provenance of one release from stored artefacts alone.
Take one product from measured baseline to an improved cycle time with test gating, on-demand environments, rehearsed rollback and full release traceability.
Chennai's engineering demand is dominated by organisations that build and ship products rather than only operate services. Telecom and networking software, automotive and component engineering tied to the manufacturing belt along the Oragadam and Sriperumbudur corridors, enterprise product suites built by long-established local software companies, healthcare and pharmaceutical technology, insurance and banking back-office platforms, and captive research and development centres for global equipment makers. Software here frequently ships alongside hardware or into a customer's own upgrade cycle, which sets the tone for every delivery conversation.
The consequences show up consistently in engagements. Codebases are large and long-lived, with supported releases going back years, so branching strategy and backporting are live concerns rather than theory. Builds are measured in tens of minutes, and the fastest available win is usually caching and agent strategy rather than a new tool. Test estates include shared hardware and licensed instruments that cannot simply be parallelised. Java and C++ dominate, containerisation is a migration rather than a default, and release calendars are negotiated against plant schedules and customer windows. Chennai teams also tend to ask for traceability early — linking requirement to commit to build to approval — because their customers or quality processes ask for it first.
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.
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.
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.
| 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.