About Rohit Bhardwaj
I help developers and architects think clearly about systems.
Enterprise AI architect. O’Reilly instructor. Author of System Design with AI Interview Guide. Host of AI Architect Circle.
Bring a difficult question. We’ll make the assumptions visible and work toward a decision you can explain.
I created AI Architect Circle as a place to work through the decisions behind software and AI systems. The questions might come from an interview, a project, or a design review. The aim is the same: reach a recommendation you can explain and examine.
My work as Director of AI & Data Architecture at Salesforce brings together enterprise AI, agentic systems, distributed systems, and data platforms. You can explore my background and talks in the ArchConf speaker profile ↗.
Architecture becomes more useful when we make our assumptions visible. What does the system need to achieve? What constraints matter? Where can it fail? What evidence would change the decision?
My educational work connects those questions to practical exercises. AI can help us explore possibilities and challenge an answer. Our responsibility is to check the reasoning and decide what fits the situation.
What you can expect here
- A concrete starting pointA scenario, a constraint, and a question you can work on.
- Reasoning you can challengeAlternatives, trade-offs, and the conditions that could change a recommendation.
- Respect for your contextUseful principles with room for the requirements and uncertainty in your own work.
- A practical next stepA worksheet, a source, or a question to take into your next conversation.
Teaching, speaking, and publishing
The book and the circle
Build understanding through practice.
System Design with AI Interview Guide is a companion for readers developing an approach to system design. The circle extends that study through free resources and conversations.
You do not need to arrive with the perfect answer. Bring an unfinished idea and a willingness to examine it.
Explore the bookEditorial approach
Make the evidence and the reasoning visible.
Architecture advice is more useful when you can examine how it was reached. Articles distinguish reported facts from interpretation, connect claims to relevant sources, and describe the assumptions behind examples.
Teaching scenarios are labelled as hypothetical. They illustrate a decision and do not imply a real incident or a private customer engagement.
When a correction changes the advice, the article should be updated with an explanation of the change. A new review date should reflect a substantive review, not merely a cosmetic edit.
If you notice an unsupported claim, a missing constraint, or a broken reference, please raise it through the contact page.
Share a question or correction