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

Yes, in Hinglish: technical terms in English, explanations in Hindi the way Indian engineering teams actually talk. It is a live system design course for backend engineers in India, not dubbed English slides. If you searched for a system design course in Hindi or Hinglish, this is built for that.

Yes. The whole arc is developer to architect: you start with a monolith, earn every split with a reproducible failure, write ADRs for each decision, and finish with a portfolio hiring managers read. It is not syntax training. It is how senior and staff engineers think about boundaries, scale, cost, and failure before they pick a library.

Backend developers with 4-18 years who have shipped to production and felt a bad architecture decision hurt them. If you can build a REST API and argue about why a past system broke, you fit. Sweet spot is 5-10 years, seniors moving toward staff. The monolith-to-services arc lands hardest there. At 10+ years you will skim some code weeks; use the time to write retroactive ADRs on your own systems. At 4 years you are welcome but expect a steep ramp.

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.

Yes. We will not fail you because a C# file does not compile. Each week you submit ADRs, sequence diagrams, failure analysis, and k6 notes. Tadka runs on .NET 10, but service boundaries, API contracts, Kafka, caching, and observability are the same in Java, Node, or Go. Every day ships an option-space.md that maps the pattern to your stack.

Most system design and architecture courses give you twenty shallow interview diagrams. We take one production system and run it all the way: monolith, scale until something hurts, split when the data says so, load test it, break it on purpose. You write an ADR for every major call. That helps in interviews because you have seen consumer lag and cache stampedes, not just drawn a Kafka box.

We do not fail you because a C# file does not compile. You submit ADRs, sequence diagrams, failure analysis, and demo evidence each week. The rubric cares more about your reasoning and failure modes than whether you typed the handlers yourself. Tadka is code you run and break. Your job is the decisions and the diagrams.

Everyone does pair mocks in Week 8, plus the Design-Swiggy masterclass. I cannot do forty-five minute 1:1s with fifty people and still teach the cohort. The top five peer-voted ADRs each batch get an instructor review slot.

No. We build with Postgres, Redis, Kafka, Docker, observability, k6, and ADRs. MongoDB, Elasticsearch, event sourcing, and fancier deploy patterns come up as decision discussions: when they are worth the extra complexity, when they are not.

Very little. Postgres, Redis, Kafka, and Docker all run free on your laptop. Cloud deploy is one black-box day: we use a pre-built stack and talk about blast radius, release cadence, and the monthly bill. You do not iterate on AWS infra yourself, so no surprise cloud charges. Copilot (~$10/month) or Claude Code is optional; we cover the workflow either way.

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.

You walk out with an architecture portfolio: ADRs, diagrams, a cost model, load test notes. That is what hiring managers actually read, not a PDF that says you completed a 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.