Stop Building Like a Developer.
Start Thinking Like an Architect.

Backend developers with 4-18 years of experience who have shipped to production and felt the cost of architectural decisions. If you can build a REST API, understand basic SQL, and have opinions about why past systems broke, you belong here. Being honest about the range: the sweet spot is 5-10 years, engineers moving from senior to staff/architect, where the monolith-to-microservices arc lands hardest. If you have 10+ years, you will likely skim the implementation, but the cohort has a senior layer built for you: write retroactive ADRs on your own production systems, answer the "what does the simplified version miss?" pushback prompts, and use the ADR and trade-off templates as RFCs for your real design reviews. At 4 years, you are welcome but expect a real ramp, lean on the decision frameworks and architecture diagrams over the code, and you will keep up.

Hinglish. The way real engineering discussions happen in Indian teams. Technical terms stay in English, explanations flow naturally in Hindi. Think of it as a senior engineer explaining architecture over chai, not a university lecture.

All sessions are recorded and available to every enrolled student for the cohort duration plus 6 months (watermarked, no public distribution). But honestly, the live Q&A and code-along is where the real learning happens. Try not to miss them.

Absolutely. The capstone uses .NET 10, but the architecture work is language-agnostic. Service boundaries, API contracts, Kafka event flows, caching strategy, observability, deployment trade-offs, and FinOps modeling apply regardless of your stack.

Interview courses teach you to talk about many systems. We take ONE system deep: start with a monolith, scale it, hit real pain points, extract services when justified, and deploy the result. Requirements, data decisions, async flows, deployment, observability, cost, load testing, and ADRs. You earn every architectural decision instead of assuming microservices on day one.

No. The hands-on core is PostgreSQL, Redis, Kafka, Docker, ECS, CI/CD, observability, k6, and ADRs. Tools like MongoDB, Elasticsearch, Event Sourcing, and advanced deployment patterns are covered as decision points so you know when they are worth the extra complexity.

Very little. The whole stack — PostgreSQL, Redis, Kafka, Docker — runs free on your laptop. Cloud deployment is taught black-box: we run all 4 services on a pre-built stack in one "deploy day" and reason about blast radius, release cadence, and the monthly bill, so there is no surprise AWS charge from iterating on infrastructure yourself. An AI pair-programmer is optional but recommended (GitHub Copilot is about $10/month, or use Claude Code) — and we cover the workflow either way. No other paid tools.

Around 8-10 hours per week. 5 hours of live sessions on weekends, plus 3-5 hours for hands-on assignments and building your section of the capstone project. It's intense, but it's only 8 weeks.

Better than a certificate. You get a production-grade architecture portfolio document with an ADR for every major decision, infrastructure diagrams, FinOps analysis, and load testing results. This is what actually impresses hiring managers, not a PDF that says "completed course".

Full refund within 7 days of the cohort start date. No questions asked, no hoops to jump through. If the first week doesn't convince you, you get 100% back.