A pal of mine had to rent a developer to implement an internet based system in ASP.NET MVC. Since my friend know that I use both ASP.NET MVC, ASP.NET Web API and ASP.NET Core, he requested me about which questions to ask in the course of the interview.
Let me start out with this: I don’t believe in check-lists. You can't find a listing of 50 ASP.NET MVC interview questions, if you want to reveal if you have the right man or not. To absolutely show that the interviewee knows some thing approximately ASP.NET MVC, you will need to either see code that he/she wrote or maybe better: permit him/her display it to you. Ask the individual you're interviewing to reveal you some code and give an explanation for what goes on.
I frequently read remarks from humans saying some thing like “with this approach, you don’t recognise if the man or woman under interview wrote the code or not”. Don’t worry! If he/she didn’t, you may recognize within the first couple of minutes. When inquiring for the rationale in the back of the design choices, people writing the code will be able to answer and the ones showing other peoples code won’t.
Depending at the architecture you chose in your MVC app, speakme approximately one or greater of the following subjects is a super manner to recognize how the interviewee reflect onconsideration on code.
Model View ControllerTalk about separation of concern. What does the man or woman reflect onconsideration on MVC versus similar patterns? Do he/she even understand about alternatives?
Dependency InjectionDI is a vital a part of MVC (or at the least need to be). Talk about the blessings and drawbacks of using IoC. Which containers have the person used. Any favorites and why? Remember to ask approximately item lifecycles and when to apply what.
Rendering viewsWhich view engines have the interviewee used and prefer? Ask approximately the differences among Razor and single page applications. You would possibly have a good know-how approximately the differences, but you will be surprised approximately the weird answers human beings come up with.
SecurityLet’s face it. Security is important. Does the individual realize approximately authentication and authorization and how to enforce it in ASP.NET MVC? Digging into strategies for solving cross website online request forgery might be a way to find out how much the interviewee clearly is aware of outside the standard AccountController generated through Visual Studio.
ASP.NET Web API and ASP.NET CoreDo the person you're interviewing realize the distinction among ASP.NET MVC, ASP.NET Web API and ASP.NET Core? While know-how approximately Core isn’t a must, it suggests you if the man or woman is into new technologies or not.
There you go. A quite easy list and I’m certain there are plenty of different things to talk approximately as well. In my opinion, digging into details about the information of the API or having humans write Razor on a whiteboard, isn’t the manner to head here. Take 15 minutes to glance through the code that the interviewee wrote after the interview instead. Identifying mess inside the code, usually display up inside the first file you open anyway.
Would your users admire fewer mistakes?Elmah.Io is the clean blunders logging and uptime monitoring service for .NET. Take back control of your mistakes with aid for all .NET net and logging frameworks.
Let me start out with this: I don’t believe in check-lists. You can't find a listing of 50 ASP.NET MVC interview questions, if you want to reveal if you have the right man or not. To absolutely show that the interviewee knows some thing approximately ASP.NET MVC, you will need to either see code that he/she wrote or maybe better: permit him/her display it to you. Ask the individual you're interviewing to reveal you some code and give an explanation for what goes on.
I frequently read remarks from humans saying some thing like “with this approach, you don’t recognise if the man or woman under interview wrote the code or not”. Don’t worry! If he/she didn’t, you may recognize within the first couple of minutes. When inquiring for the rationale in the back of the design choices, people writing the code will be able to answer and the ones showing other peoples code won’t.
Depending at the architecture you chose in your MVC app, speakme approximately one or greater of the following subjects is a super manner to recognize how the interviewee reflect onconsideration on code.
Model View ControllerTalk about separation of concern. What does the man or woman reflect onconsideration on MVC versus similar patterns? Do he/she even understand about alternatives?
Dependency InjectionDI is a vital a part of MVC (or at the least need to be). Talk about the blessings and drawbacks of using IoC. Which containers have the person used. Any favorites and why? Remember to ask approximately item lifecycles and when to apply what.
Rendering viewsWhich view engines have the interviewee used and prefer? Ask approximately the differences among Razor and single page applications. You would possibly have a good know-how approximately the differences, but you will be surprised approximately the weird answers human beings come up with.
SecurityLet’s face it. Security is important. Does the individual realize approximately authentication and authorization and how to enforce it in ASP.NET MVC? Digging into strategies for solving cross website online request forgery might be a way to find out how much the interviewee clearly is aware of outside the standard AccountController generated through Visual Studio.
ASP.NET Web API and ASP.NET CoreDo the person you're interviewing realize the distinction among ASP.NET MVC, ASP.NET Web API and ASP.NET Core? While know-how approximately Core isn’t a must, it suggests you if the man or woman is into new technologies or not.
There you go. A quite easy list and I’m certain there are plenty of different things to talk approximately as well. In my opinion, digging into details about the information of the API or having humans write Razor on a whiteboard, isn’t the manner to head here. Take 15 minutes to glance through the code that the interviewee wrote after the interview instead. Identifying mess inside the code, usually display up inside the first file you open anyway.
Would your users admire fewer mistakes?Elmah.Io is the clean blunders logging and uptime monitoring service for .NET. Take back control of your mistakes with aid for all .NET net and logging frameworks.
0 Comments