Took a whole day at the office that too without technical interview ,
First was a technical test (laptop based), then if selected the English and hearing test, then HR round and then 2 technical rounds ,
Frustrating and probably biased. He went into depth for questions for those topics I mentioned I didn't know. I don't want to say there was a bias, but interview was skewed towards non-selection.
Interview questions [1]
Question 1
1.There is a requirement/enhancement coming within an existing application. What is the approach you take? What are the artifacts you come up with? How do you start with coming up with the design?
2. Give me a problem statement and the solution you have done — a use case where you are really proud of the design you delivered.
3. After multiple retries, a message goes into the dead letter queue. What are you doing with those messages?
4. Say there is some scenario where a message is going to a dead letter queue — it need not be payment, it could be inventory, orders, whatever. How are you going to solve that, and what are you going to do with those messages?
9. Is your application monolithic or microservices-based?
10. How are you handling data integrity within the microservices?
11. Say order processing: I create an order, check inventory, do the payment, then create the order. If the payment fails and inventory is already deducted — how do you maintain data integrity in this case?
12. You talked about CQRS — why do you need to use the CQRS pattern?
13. (Follow-up) You could reuse the same models for read and write, right? It's just an object with data. Why should you not use the model itself?
14. (Follow-up) Those locks can still be controlled using NO_LOCK or similar mechanisms, right?
15. How do you communicate between one microservice and another?
16. How is your microservice deployed in Azure — are you using App Services or Kubernetes?
17. When do you choose between App Services and Kubernetes?
18. What are extension methods?
19. How do you differentiate between a regular method and an extension method?
20. In an ASP.NET web application, how are you going to handle exceptions across your controller methods?
21. Say I don't want to use try-catch in each controller/action method — how do you handle it in a generic way?
22. (Follow-up) You talked about middleware — how are you going to do that with middleware?
23. How many years of experience do you have developing ASP.NET web applications?
24. How do you improve performance in your ASP.NET application?
25. Do you know what clean architecture is?
26. Do you know what is (unclear) design?
The interview process covered React and Angular fundamentals, component architecture, lifecycle methods, hooks, state management, routing, forms, API integration, performance optimization, and real-time scenario-based questions. It also included discussions on project experience, debugging approaches, best practices, and handling production-level challenges in frontend development.