I got a call from Deloitte India for a .Net full stack developer role. There were a total of 3 rounds.

1. Online assessment (moderate level). I was able to clear it.
2. Technical round. I was able to clear the technical round as well.
3. Partner round. I had the worst experience ever. He told me, "We are looking for an Azure-centric resource only, not a full stack. So we have to reject you, as you do not meet expectations." (I got rejected.)

1. Interface vs. abstract class

2. Design patterns

3. Azure API Gateway

4. Key Vault

5. Function App

6. Application Insights

7. Redis Cache

8. ELK Stack

9. Find 4th highest salary using SQL and LINQ

10. Can we add a record using HTTP GET?

11. Why POST if we can PUT?

12. Explain how you would implement registration (from UI till DB).

13. TempData vs. ViewBag

14. ViewData

15. Authorization of requests

16. Team structure and size

17. Sprint planning

18. Exception handling

19. Logging implementation

20. ConfigureService vs. Configure

21. Dependency Injection

22. Types of DI

23. Can two actions have the same name and same parameters?

24. SOLID principles

25. If you are using JWT authentication and it is stored at the client end, and the current user has logged out but the token is not removed from the UI side, and some other user can use that to bypass your application, how would you handle it?

26. Code coverage in Sonar

27. .NET vs. .NET Core

28. Guess the output:

csharp Class A { public virtual void Display() { Console.WriteLine("A.Display()") } }

Class B : A { public override void Display() { Console.WriteLine("B.Display()") } }

Class C : B { public new void Display() { Console.WriteLine("C.Display()") } }

static void Main() { A a = new A(); C c = new C(); a = c; c.Display(); a.Display(); }

1. Middleware

2. How routing works

3. Triggers

4. SP vs. Function: when to use what

5. Azure Active Directory