Private corporate batches, live online cohorts and 1-on-1 mentoring in spaces, pages, templates, macros and permissions for documentation people actually maintain — 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 teaches Confluence as an information architecture problem rather than an editor tutorial — space design and the permission model from global down to page restrictions, templates and blueprints so content arrives in a consistent shape, and labels, the page tree and search so it is findable a year later. Sessions cover the macro layer in depth, from text formatting, panel and code macros to space, gallery, task list and user macros that turn a static page into a live view, then move into administration: users and groups, directory integration, apps and add-ons, site customisation, notifications and task management, attachment handling and versioning, and backing up and restoring a site.
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 Confluence that means a trainer who has run it in production — spaces, pages, templates, macros and permissions for documentation people actually maintain — 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 Confluence batchConfluence is Atlassian's collaborative documentation and knowledge platform. Content lives as pages, pages live in spaces, and spaces are the unit that carries permissions, navigation and ownership. A page has a full version history, restrictions, labels, attachments, comments and watchers, which is what distinguishes it from a shared document: content in Confluence has an owner, an audit trail and an audience.
The editor is only half the product. The other half is macros — the components that pull dynamic content into a static page. A page can include a table of child pages, a filtered list of pages by label, a task list, an excerpt from another page, an issue list from a linked tracker, code blocks, panels, galleries and expandable sections. User macros let an organisation define its own. This is what makes a Confluence page a living view rather than a snapshot that goes stale the day it is written.
Structure and permissions are what make Confluence work at scale or fail at it. Global permissions decide who can do anything; space permissions decide who can view, edit, comment, administer or delete within a space; page restrictions narrow further. Templates and blueprints standardise how a new page begins so a knowledge base does not become a thousand different formats. Labels, the page tree, the search and the browse menus are the navigation layer that decides whether anyone finds what has been written — which is, in the end, the only test a documentation system has to pass.
Documentation stopped being optional the moment teams stopped sitting together. Distributed and asynchronous working converts undocumented knowledge into a delivery risk, because the person who knew is now in a different timezone, on a different team, or gone. Confluence is where a large share of organisations put that knowledge, and how well it is structured decides whether it is an asset or a landfill.
The skill that matters is not writing pages. It is designing a space and permission structure that reflects how the organisation is actually organised, choosing templates so content arrives in a consistent shape, using macros and labels so pages surface themselves rather than needing to be found, and setting a review rhythm so content that has gone stale is visibly stale. Nearly every failed Confluence instance failed on those points rather than on the editor.
There is a distinct administration demand too. Space and global permission design, connecting to a corporate directory, managing apps, backup and restore, site customisation and migration between deployments are all specialist work, and the people who can do it credibly are far fewer than the people who can write a page. For engineering organisations there is a further dimension: linking documentation to the tracker and to the delivery process, so runbooks, decision records and release notes live next to the work they describe.
The structure before the content. What a space is, why it is the unit of permission and navigation, how the page tree works, and the difference between a wiki that gets used and one that gets abandoned — which is almost always a structure decision made in the first week.
Topics: Exploring Confluence benefits and where it fits · Confluence structure: sites, spaces, pages and the page tree · The Confluence interface and layout · The dashboard and what it is for · Login, sign-up and the personal space · Permissions overview: global, space and page · Configuring Confluence for a new team
Getting a site running and configured. Supported platforms, evaluation options, installation, licence activation and the finishing steps — then the site-level customisation that makes an instance feel like it belongs to the organisation rather than to a vendor.
Topics: Evaluation options for Confluence · Supported platforms and system requirements · Installing Confluence on Windows · Activating a Confluence trial licence · Finalising the Confluence installation · Customising the Confluence interface · Customising the Confluence site: look, feel and layouts · Base URL, mail server and initial global configuration
The model that decides who sees what. Global permissions gate capabilities; space permissions gate a space; page restrictions narrow to individual pages. Getting all three straight — and knowing which one is causing the problem when someone cannot see a page — is core administrator work.
Topics: Creating users and groups · Adding groups and setting permissions · Managing user permissions · Global permissions and what they gate · Space permissions in detail · Page locations and page restrictions · Anonymous access and public spaces · Diagnosing why a user cannot see a page
How people find things. The menus, the people directory, the user menu and the search — plus the navigation helpers that authors control: labels, page ordering and the browse views. Findability is a design responsibility, not a user problem.
Topics: Menus and the browse menu · Browse menu basics: pages, blogs, labels, attachments · The people directory · The user menu · The search menu and search syntax · Using labels and other navigation helpers · Search filters, scoping and why results disappoint · Ordering the page tree meaningfully
Producing content. Creating a space and giving it a landing page that does work, creating pages and blog posts, adding headings and text, and the supporting content patterns — child pages, related pages, and blogs for things that are dated rather than maintained.
Topics: Creating spaces and space types · Creating content in a space · Creating pages and blog posts · Adding headings and text in pages · Public sign-up and login for an open space · Supporting pages and child page structure · Blogging your experiences and when a blog beats a page · Searching and browsing for related items before writing
Everything the editor does that people never discover. Layouts and columns, tables, images and attachments, links, video and embedded media — and how to edit an existing page without destroying someone else's structure.
Topics: Editing pages using the text editor · Changing page layouts and column sections · Creating and formatting tables · Adding images and attachments in Confluence · Adding links: internal, anchor and external · How to add video and embedded media · Editing page content: structural and inline changes · Customising page layout for readability
Consistency at scale. Templates and blueprints so pages begin in the right shape, importing and updating existing content, and the lifecycle after publication: page information, version history, comparing versions, and removing content deliberately rather than leaving it to rot.
Topics: Creating pages from templates and blueprints · Creating a template and scoping it to a space or globally · Using a template to create a repeatable page type · Importing, updating and removing content · Page information and page history · Comparing versions and reverting · Viewing page information for audit and ownership · Archiving and deprecating stale content
The features that turn documentation from publishing into conversation. Comments and inline feedback, watching pages and spaces, sharing and mentions, following, likes, favourites, drafts, and the network and popular content views on the dashboard.
Topics: Giving content feedback and making comments · Adding inline and page comments · Watching pages, spaces and blogs · Favourites and drafts · Following users and using your network · Sharing a page and using @mentions · Likes and popular content on the dashboard · Enabling restrictions on a page during drafting · Sharing page content outside the team
The single highest-leverage topic in Confluence. Simple formatting macros first, then the ones that pull dynamic content into a page — space, page tree, blog posts, gallery and task list — then widgets, external content, advanced visuals and user macros, plus how to read a macro error rather than deleting the macro.
Topics: Introduction to macros and the macro browser · Text formatting macros · Colour, quote, code and panel macros · The HTML macro and its risks · Space macros and page tree macros · The blog-posts, gallery and tasklist macros · Widgets and external content macros · Advanced images and visuals · User macros: writing your own · Creating a page with embedded macros · Macro errors and how to diagnose them
Working faster and more precisely than the editor allows. Keyboard shortcuts, wiki markup and autoformatting, text styles, headings, lists, tables and links at markup level — which is also how you fix a page the editor has mangled.
Topics: Keyboard shortcuts worth learning · Wiki markup and autoformatting · Text styles and emphasis · Headings and document outline structure · Lists, nesting and task lists · Tables in markup · Links, anchors and shorthand link syntax · Repairing a page whose structure has broken
Turning documentation into follow-through. How Confluence notifies, how to tune email so people stay subscribed, and the task system — creating tasks in a page, gathering them with the tasklist macro, assigning them to people, and completing them from a notification.
Topics: Managing tasks and notifications · Email options and notification settings · Advanced Confluence notification configuration · Turning off recommended-content email · Notifying a specific user · Creating tasks in a page · The tasklist macro and aggregating tasks · Using and completing tasks from a page or a notification · The task list view per user
The operational layer. Attachment handling and versioning, the attachments macro and settings, then administration proper: managing add-ons including diagramming apps, admin tasks, and backing up and restoring a site — the one procedure nobody has practised until they need it.
Topics: Attaching files and file management · The attachments macro and viewing attachments · Editing attachments and file versioning · Versioning attachments and changing attachment settings · Admin tasks and the administration console · Managing add-ons and plugins · Installing and using a diagramming app such as Gliffy · Backing up and restoring a site · Site health, storage and upgrade considerations
We rebuild the agenda around the tools you actually run.
Request a custom agendaTake a team's scattered documents and build a space with a page tree, naming convention, ownership and a landing page that routes newcomers correctly.
Build a permission model across global, space and page level, then debug three access problems, each caused at a different level.
Create templates for the page types a team writes repeatedly, apply them, and measure the difference in structure against the pages written freehand.
Build a space home page from page tree, label, excerpt, tasklist and gallery macros so it stays current with no manual editing.
Run a meeting-notes flow where decisions become documented and actions become assigned tasks that appear on each person's task list.
Back up a fully configured site with attachments and apps, destroy it, restore it, and verify every space, permission and attachment version survived.
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 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.
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
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.
| 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.