Private corporate batches, live online cohorts and 1-on-1 mentoring in immersive application engineering — XR runtimes, 3D content pipelines, WebXR, networked multi-user worlds and digital twins — 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 as engineering under a hard frame budget rather than as a tour of virtual worlds. It covers the OpenXR and WebXR runtime layers, the asset pipeline that gets a CAD or Blender model down to a draw-call budget a standalone headset can hold, interaction and comfort design, and the authoritative-state networking that makes a shared session usable over real latency. Every performance claim is demonstrated with a profiler open — draw calls, batching, level of detail, texture compression and frame timing — because in immersive work the difference between a demo and a product is almost always a measurement nobody took.
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 Metaverse that means a trainer who has run it in production — immersive application engineering — XR runtimes, 3D content pipelines, WebXR, networked multi-user worlds and digital twins — 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 Metaverse batchThe Metaverse, stripped of marketing, is a stack of engineering problems that already have concrete solutions. At the bottom sits real-time 3D rendering — Unity, Unreal Engine, or a browser engine such as three.js or Babylon.js — running against a frame budget set by the device rather than by the designer. Above that sits the XR runtime layer, standardised by OpenXR on headsets and by the WebXR Device API in browsers, which is what lets one application address a Meta Quest, a SteamVR headset, an Apple Vision Pro or a phone-based AR session without a separate codebase per vendor.
On top of the runtime are the parts that make a scene an experience. A content pipeline that gets assets from Blender, CAD or a photogrammetry scan into a format a headset can actually render — glTF or OpenUSD, with Draco and KTX2 compression, level-of-detail meshes, baked lighting and a draw-call budget. An interaction layer: hand and controller input, ray and grab interaction, teleport and smooth locomotion, and the comfort constraints that decide whether users can stay in the experience for twenty minutes. And a networking layer for shared presence — authoritative state, interpolation, avatar representation, spatial voice and the reconciliation logic that hides latency.
What sits above that is where organisations differ. Consumer platforms add identity, user-generated content and an economy. Industrial use is dominated by digital twins — a live 3D model of a factory, building or network fed by real telemetry — and by training simulation, where the value is measurable competence rather than engagement. Interoperability, the promise that made the term Metaverse popular, is still partial, and the honest answer is that OpenUSD, glTF and OpenXR are the standards that actually move assets and sessions between systems today.
The hype cycle has finished, and the useful part survived it. Headsets shipped in volume, OpenXR became the runtime almost everyone targets, WebXR reached the browsers that matter, and OpenUSD picked up serious industrial backing — which means immersive work is now a normal engineering discipline with stable interfaces rather than a research project against proprietary SDKs.
Demand has shifted with it. The funded projects today are industrial and enterprise: digital twins of plants and buildings, safety and procedure training that is cheaper and safer than the real thing, remote assistance with an expert seeing what a technician sees, design review in 3D, and product configuration and visualisation. These have measurable returns, which is exactly why they survived when consumer virtual worlds did not.
The skills gap is specific. Most teams starting this work come from web or backend engineering and hit the same wall — the application runs at thirty frames per second on a standalone headset, the assets are a hundred times too heavy, the multi-user session desynchronises, and users feel unwell after ten minutes. None of those are conceptual problems; they are performance budgets, content pipelines, network authority models and comfort constraints, all of which can be taught directly.
A working map of the technology so later decisions are evidence-based. Devices and their real constraints, the runtime standards that removed vendor lock-in, where AR, VR and mixed reality genuinely differ, and a candid separation of what is production-ready from what is still a demo.
Topics: Device classes: standalone headsets, tethered PC VR, phone AR, passthrough mixed reality · OpenXR and what it standardised · Rendering engines: Unity, Unreal, three.js, Babylon.js · Frame budgets, refresh rates and motion-to-photon latency · Tracking: inside-out, hand tracking, eye tracking, controllers · AR, VR, MR and spatial computing as engineering categories · What is production-ready today and what is not · Choosing device targets before writing any code
Where most immersive projects die. Getting assets from CAD, Blender or a scan into a form a headset can render — retopology and decimation, level of detail, texture atlasing and compression, material conversion, baked lighting — and the formats that let assets move between tools at all.
Topics: Asset sources: CAD, DCC tools, photogrammetry, procedural · glTF 2.0 as the delivery format, and OpenUSD for scene interchange · Polygon budgets, decimation and retopology · Level of detail and impostors · UV layout, texture atlasing and material consolidation · Texture compression: KTX2, Basis, ASTC · Draco and mesh compression for the web · Baked lighting, lightmaps and light probes · Draw calls, batching and GPU instancing · Automating the pipeline so artists do not do it by hand
The application layer on a headset. Project setup against OpenXR, the camera rig and tracking spaces, input from controllers and hands, interaction patterns that users already understand, and the locomotion and comfort decisions that determine whether an experience is usable.
Topics: Project setup and the OpenXR plugin path · Tracking spaces: local, stage and world-locked content · Controller input, hand tracking and gesture · Interaction: raycast, direct grab, poke, physics hands · Locomotion: teleport, smooth movement, vignetting and comfort · Spatial UI and text legibility in 3D · Passthrough, anchors and scene understanding for mixed reality · Spatial audio · Accessibility: seated play, handedness, subtitles, motion sensitivity · Profiling on device rather than in the editor
The distribution route with no install and no store review. Building with three.js or Babylon.js, entering an immersive session from a normal page, progressive enhancement so non-XR users still get something, and the loading and performance constraints that a browser adds on top of the device's.
Topics: The WebXR Device API and session types · three.js and Babylon.js: choosing and structuring a project · Entering and exiting immersive sessions safely · Progressive enhancement for desktop and mobile visitors · Asset loading, streaming and perceived load time · AR on the web: hit testing, anchors and lighting estimation · 8th Wall and other hosted AR pipelines · Performance limits of the browser renderer · Hosting, HTTPS, CDN and cache strategy for 3D assets
Shared presence, which is where the term Metaverse actually earns its meaning. Authoritative state and client prediction, what to replicate and what to interpolate, avatar representation and inverse kinematics, spatial voice, and how many concurrent users a given architecture can actually hold.
Topics: Authoritative server vs peer-to-peer state · Replication, interpolation, extrapolation and reconciliation · What to send and what to derive — bandwidth budgets · Networking stacks: Photon, Netcode for GameObjects, Mirror, Colyseus · Avatars, rigging and inverse kinematics from three tracked points · Spatial and proximity voice chat · Presence, ownership and object authority · Room and instance sharding, and realistic concurrency limits · Persistence: what survives a session and where it lives · Moderation, reporting and personal space controls
The layer that gets promised most and delivered least. What portability actually works today, avatar and asset standards, account and entitlement models, and a deliberately sober treatment of blockchain-based ownership — what it does and does not solve for an enterprise deployment.
Topics: Identity, accounts and entitlement across platforms · Avatar standards and cross-platform avatar services · Asset portability: what glTF and OpenUSD actually carry between tools · The Metaverse Standards Forum and where standards work is happening · Digital ownership claims, tokens and their real limitations · Content licensing, rights and provenance · Privacy in immersive systems: biometric-adjacent tracking data · Safety, harassment and moderation design · Data residency and regulatory exposure for spatial data
Where immersive work is actually funded. Digital twins fed by live telemetry, training simulation with measurable assessment, remote assistance and design review — plus the delivery side nobody plans for: build pipelines for large binaries, device fleet management, distribution and in-application analytics.
Topics: Digital twins: connecting a 3D scene to live telemetry · Streaming and simulation platforms for large industrial scenes · Training simulation and measurable competence assessment · Remote assistance and see-what-I-see workflows · Design review and product configuration use cases · CI for large 3D projects: build times, artifacts and asset storage · Distribution: stores, enterprise sideloading and managed device fleets · Device management, kiosk mode and hygiene for shared headsets · Analytics and telemetry inside an immersive session · Costing a pilot and defining what would make it succeed or fail
We rebuild the agenda around the tools you actually run.
Request a custom agendaTake a heavy source model and drive it down to a stated triangle, texture and draw-call budget using decimation, atlasing, compression and level of detail — with measurements before and after.
Build an OpenXR application with direct and ray interaction, comfortable locomotion and spatial UI, then hand the headset to someone who has never used one.
Publish a WebXR scene that degrades gracefully to phone and desktop, then halve its first render time through asset and loading work.
Build a shared room with avatars and spatial voice, then inject latency and packet loss until it breaks and fix it with interpolation and authority changes.
Connect a live telemetry feed to a 3D scene so state changes appear in the model, including handling stale and missing data honestly.
Deliver a working application plus the pilot case around it: architecture, asset pipeline, build and distribution, measurement and defined success and failure conditions.
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
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.
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.
| 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.