.NET interview questions :- Can you explain architecture of your project ?

 Posted by articlesmaint on 3/7/2011 | Category: .NET Framework Interview questions | Views: 53004

This is normally the first .NET interview question which pops up in .NET and C# interviews. Personally i think your full  .NET interview ahead depends on how you will answer this question.

Common mistakes :- Many developers make a common mistake of answering this question by saying that we have used C# , SQL server , ASP.NET etc. But please do note that the question is, what is the architecture of your project and not technology.

So a typical answer will be something as below. Please note your answer will vary as per your architecture and structure.

"My current architecture is a simple 3 tier architecture with UI in ASP.NET , middle layer are simple .NET classes and DAL is using enterprise application blocks.

The UI  is responsible to take user inputs , all my business validations are centrally located in middle layer and the data access layer is responsible to execute stored procedured and SQL queries to SQL Server.

Strongly typed business objects are used to pass data from one layer to other layer. The database of the project is in a 3rd normal form."

So first start with the overall architecture , talk about each layer , how data is passed between each layer and the database design structure.

One very important tip if you can draw a diagram and explain....I think you have the job.



Asked In: Many Interviews | Alert Moderator 

Comments or Responses

Posted by: Kishork80 on: 3/7/2011
Just to add on this Try to get command over Design Pattern and UML diagrams .Must know use case, sequence diagram, class diagrams,State Diagram,Activity Diagram,Interaction... . This is mandatory to explain Your application flow.Try to talk clear and to the point if you are going for Senior level positions like Tech Lead or Senior developes. They will get confident and .. you get the job instantly. Good Luck
Posted by: Laghaterohan on: 3/8/2011
I agree, however i feel design patterns are quite tough to understand at once and needs quite a lot of reading and understanding...any one has better ways to remember design patterns?

Login to post response