How do i Know someone really knows .NET

Roddy66

Hi My company is hiring and I'm stuck with writing a meaninful set of questions so interviewers can ask the prospects about .NET and ASP.NET This are Senior level Developers positions that will be in charge if developing from specs or sometimes without specs web-based and smart client applications. On top of .NET they require amomg other things - N-tier architecture - component development - UML and RUP - Data modellling - ORACLE - PL/SQL Any how , can someone point me to standards question that can ask to determine the level of knowledge on ASP.NET and .net in general. Rodrigo

Anonymous

Hi, Well a good start would be with the garbage collection. Ask them what is garbage collection, and the mechanics of it. Make sure u read about 1'st and 2nd generation garbage collection. this will help you understand and also compose some questions. Also you can ask them about the .NET tools, such as ILASM-ILAssembler, ILDASM-ILDisassembler, and of course IL. IL is the bytecode of the framework. Any experienced developer would certainly know a bit about IL, Intermediate Language. And for asp.net I would ask about security. Such as Forms.Authentication namespace, simply for the reason that if any developer has worked with asp.net they would definatly work with Asp.NET security namespaces. Also I would definatly get into the DataGrid control since its advanced and very powerful. Maybe Class Libraries can fit in there too, and component development.

Colin Angus Mackay

Anonymous wrote: Well a good start would be with the garbage collection. Why? There really isn't much to know other than to use Dispose if an object uses IDisposable, and implement IDisposable yourself if your class has member variables that use the IDisposable interface themselves. Anonymous wrote: ILASM-ILAssembler, ILDASM-ILDisassembler, and of course IL Huh! What does that really get you? While the information could be useful there are a number of really great .NET developers I know that don't use IL or the ILAssembler/Disassembler. Anonymous wrote: And for asp.net I would ask about security. Why stop there? What about security in Win Forms Applications? What about security when dealing with the database? Security is a huge topic and covers many areas. Anonymous wrote: Also I would definatly get into the DataGrid control since its advanced and very powerful. Personally, I find that data grids are extremely poor. They are good for mocking up a quick prototype but they are cumbersome and difficult to change if you want to do anything more than simple grids. Anonymous wrote: Maybe Class Libraries can fit in there too Are you talking about the .NET BCL (Base Class Library)? And you say "Maybe"!

Do you want to know more? WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and Forums

Upcoming talk: SELECT UserName, Password FROM Users -- Getting unauthorised access to a SQL Server, and how to prevent it.

Colin Angus Mackay

rpineda wrote: My company is hiring and I'm stuck with writing a meaninful set of questions so interviewers can ask the prospects about .NET and ASP.NET I would suggest the best policy would be to put someone technical on the interview panel rather than have someone non-technical ask the questions. A non-technical person will either only accept the answer as written down for them (the person may know the answer, just not express it in the same way) or could be bambozzled into accepting a false explanation. I would say that the .NET Framework is so big that few people will know all of it in depth. Think about the projects you will need this programmer to work on and ask question in those area. If you find a test to ask prospective .NET developers make sure it asks questions that are relevant to the work you do. For example, you mention Oracle, so asking questions about classes in the System.Data.SqlClient namespace will be a bit pointless, but asking about System.Data.Oracle will be relevant. You might try looking in books designed for the MCAD and MSCD courses as they often have sample exam question at the end of each chapter or at the back of the book. I would say that the most important qualities of a good developer are willingness/eagerness to learn (information becomes old very quickly in IT), be a good logical thinker (this allows them to think through problems - especially ones they may not have encountered before). Anyway, I hope this helps.

Do you want to know more? WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and Forums

Upcoming talk: SELECT UserName, Password FROM Users -- Getting unauthorised access to a SQL Server, and how to prevent it.

Steven Campbell

Give them a notebook with VS.NET 2003 and access to the Internet, and ask them to write both a web application and a winforms application to query the pubs database for authors, and then show the books by the selected author. Give them an hour. They may not complete, but you should be able to evaluate their knowledge of how to do multi-tiered apps, and how well they know some aspects of .NET. A faker will not be able to do anything in an hour, and a guru will impress the hell out of you.

my blog