About
This is a training residency.
Tuotr, on this site, is the training. You come to the studio in Bangalore, you build one system, and you practise explaining it. Sunil reviews the work. That is the offer.
What you are paying for
Three months on one system.
You may already have paid for a course. This is the part a course does not do: one system, in the room, with someone reading it until you can explain it.
Module 1, Build, is three months, full-time, on weekdays, at 26 Magrath Road. The fee is ₹90,000 + GST. You build one system. You write the steps. The model does the step you gave it. You learn to say what it looked up, what a tool could change, how you knew it was wrong, and what you fixed.
You can stop after those three months. They are enough for “Tell me what you built.”
Module 2, Deploy, is another three months, and only after Build. The fee is ₹1,80,000 + GST. You take the same system and learn how to run it: a place to put it, what it costs, what happens if the model changes, what happens when more people use it, and how you find the step that failed. GST is added on top of each fee.
The studio has the computers, GPUs, coding tools, and API keys. For normal use of the training, there is no extra bill for those. Your rent, food, and travel in Bangalore are yours. You talk to Sunil before you pay. There is no start date on this website, and there is no payment button.
The review
Sunil reads the system with you.
Sunil Gupta teaches the residency and reviews the work. The group stays small enough that he can do that.
A week is work, review, fix, and write. You build. He asks the interview questions while the system is still in front of you. If the answer is vague, you change the step. You also write down what the system is allowed to do, and that note has to match the system.
You are in the room. This is not a recording, and it is not an evening class. If you cannot be in Bangalore on weekdays for three months, say that in the first note.
The words you will use — prompt engineering, RAG, tool calling, workflows, and, if you continue, deployment, cost, evals, and error analysis — are the words an interviewer uses. You will know them because you used them on your system, and because Sunil asked you to explain them.
What you leave with
Your resume names your system.
Name the system you built, and the job it does. Then be ready to walk through it.
Say what it looked up. Say what a tool was allowed to read, and what it was allowed to change. Say how you knew a turn was wrong, and what you changed. You have already answered those questions in the studio.
Write only what you can explain. If a step is still vague, leave it off the resume. The interviewer will ask the next question.
A certificate from a course you already finished does not replace this. People have seen certificates. They still ask what you built.
After the residency
A job may come later. We do not promise one.
You are paying for the training. You are paying so you can explain one real system.
A job may be discussed later. That talk might happen. It might not. It is not a job offer. It does not name a salary. It does not name a number of openings. Paying for Build, or for Build and Deploy, does not buy a job.
A promise of a job would be a false claim. That is against the law. We will not make that promise on this website, on a call, or in an email. If the reason you would pay is a guaranteed job, do not pay. Say that in the first note.
The residency
Build one system. Explain it in an interview.
Three months is enough for that interview. Three more, if you continue, to put that system where people can use it.