Skip to content

Four courses · One practitioner

Choose by the decision, not the job title.

Four courses for the moments when your work changes shape: a first architecture review, a platform that has to scale, a team that needs a shared plan, a company that needs a delivery system.

“The course should meet the decision you are already carrying.”

Praveen VR · Principal instructor

15

Seats, most cohorts

4

Focused courses

Engineering standards grounded in 15+ years at

Principal Software Engineer
Telecom Network Systems R&D
Network Management R&D
100+ Production Systems Shipped
20+ Connected Enterprise Modules

The courses

Four ways in. One standard.

Every course is built around an artifact you can use, not a certificate you file away. Choose the one that matches the work in front of you.

1

For senior engineers moving into Team Lead or Architect roles

Technical Leadership & Architecture

For the senior engineer ready to make, defend, and land architecture decisions — without waiting for a title change.

Turn a business goal into module boundaries, data ownership, and a sequenced architecture roadmap.

Choose between monolith, services, and micro-frontends with explicit trade-offs — and know when not to split.

Design multi-tenant data isolation, permissions, and audit that survive a real architecture review.

6 weeks · Live cohort18 hours · Live contact15 max · Cohort capCohort pricing
2

For senior engineers and tech leads who build platforms

AI-Native Platform Engineering

For the platform lead who wants to build the system an AI-native business runs on, not just consume it.

Stand up a shell host and two independently deployable remote modules.

Implement three-tier tenancy, row-level security, and request-context propagation.

Design API and event contracts that survive independent module teams.

8 weeks · Build-along24 hours · Live contact15 max · Cohort capCohort pricing
3

For engineering teams modernizing a real platform

Corporate Platform Engineering & AI Delivery

For the engineering team modernising a real platform, installing safe AI delivery, and leaving with a plan they own.

Create a shared map of current business flows, pain points, and constraints.

Define target module boundaries, tenancy, integration, and data ownership.

Prototype a shell, module contract, and event flow in a guided lab.

3–5 days · Onsite option2 weeks · Online option10–20 · Team sizeCustom team quote
4

For founders and core teams installing an AI-native delivery system

Build Your Software Factory

For the founder and core team installing a delivery system that lets a small team ship like a much larger one.

Map what to automate, what to keep human, and what the factory should cost.

Write a context layer that lets agents work in your repo without constant re-explaining.

Run parallel agent work with worktrees, subagents, model tiering, and MCP.

6 weeks · Team program3 seats · Per company5 max · CompaniesPer-company cohort pricing

How to choose

Start with the outcome.

If two courses look close, choose the one whose artifact you need next. The course should change the work you are doing now, not the work you might do someday.

If you need to…Start withFormat
Make and defend architecture decisions, or move into a lead or architect role.Technical Leadership & Architecture6 weeks · live cohort
Build a multi-tenant platform with micro-frontends and AI agents.AI-Native Platform Engineering8 weeks · build-along
Modernise your team’s platform and install AI delivery safely.Corporate Platform Engineering & AI Delivery3–5 days onsite / 2 weeks online
Install a software factory across your founder and core team.Build Your Software Factory6 weeks · 3 seats per company

Still deciding?

Send a one-paragraph note about what you are working on. We will tell you which course fits — or if none do.

Ask for a recommendation

The common standard

What every course has in common.

1

Taught personally

Every session is led by Praveen VR. No teaching assistants, no junior subcontractors, no recorded substitute.

2

Capped small

Most cohorts are capped at 15 people. The work is reviewed, not just delivered, so the feedback stays specific.

3

Training only

No code audits, repository access, NDAs, or done-for-you implementation. You learn the pattern; your team keeps ownership.

Next step

Bring the work you are carrying.

Tell us what you are trying to move forward. If a course fits, we will say so. If it does not, we will tell you that too.