Forward-deployed AI engineering training in Bengaluru
Global capability centres in Bengaluru increasingly build AI systems for their parent organisations, and the engineers who do the work need a way to learn the whole path: discovery, architecture, integration and handover. The training is practical. Participants build against realistic cases, and each piece of work is assessed against a written standard.
I am Mayur Patil, based in Nashik, India. I run the public cohort and team programmes for centres, and I am in Bengaluru often for engagements.
Who takes the training in Bengaluru
The training suits engineers in capability centres who are asked to build agents for a parent's business unit, and engineering leaders who need a team that can take a system from discovery to a running product.
What the programme builds
Participants build one realistic system across the programme. Discovery sets the outcome, the owner and the evidence. Architecture records the decisions. Integration connects the system to real records and tests it. Handover gives a named owner a runbook and the decisions behind the system.
The four gates describe how each stage is assessed. The FDE operating model term describes where the engineers sit in the centre, which decides who owns the system after handover.
Example scenarios
These scenarios are examples, labelled as such. A team may build any of them, or its own:
- A procurement agent that checks supplier documents against a checklist and records each check.
- A finance-operations agent that prepares a reconciliation summary and needs approval before it posts an entry.
- A service-desk agent that drafts replies and routes exceptions to a named owner.
The public cohort or your team
| Public cohort | Team programme | |
|---|---|---|
| Who | Individual engineers | One team, on its own work |
| Format | Live online, weekday-evening and Saturday and Sunday tracks | Built for a centre's own engineers and its parent's business unit |
| Output | A working system and an assessment for each participant | A working system on the team's data, and a handover |
| Where to enrol | AIXL Academy | Send an enquiry |
Gates and artefacts
Every participant produces a discovery brief, an architecture decision record, a working build, an evaluation report and a handover note. In a capability centre, the handover note names the owner in the parent's business unit, not only the centre.
Time zones
Bengaluru is on India time. Team programmes run in the centre's working hours, with a short overlap for decisions with the parent's business unit where needed. I run back-to-back full-day corporate trainings, mostly in IST, and some programmes in US Pacific time for teams in the Bay Area.
Relevant work
Tredence, which I have worked with on building forward-deployed teams for its clients, and Novo Nordisk India are two of the organisations I have worked with. The full list is on the about page.
Where to go next
The FDE training hub describes the programmes. For consulting for a centre in Bengaluru, the Bengaluru consulting page covers the operating-model questions.
Common questions
Who takes the training in Bengaluru?
Engineers and engineering leaders in global capability centres and services firms who will build and run AI systems for a parent organisation.
Can a centre train its own engineers on its own tools and data?
Yes. A team programme is built on the centre's tools, use cases and data. It ends with a working system the team owns and an assessment of each person's demonstrated skills.
What is the public cohort format?
Live online, with a weekday-evening track and a Saturday and Sunday track. Dates and timings are on the AIXL Academy page.
Can the training run across several business units?
Yes. Programmes run for one team at a time. A centre can run several in sequence, so that each business unit builds a system to its own standard.