It's interview time!

Tomorrow we interview the first candidate to fill the vacant developer position. Already one of my coworkers has begun a careful inspection of the candidate's resume, and has identified a problem. The candidate says he has experience with SQL Server 2003, a product that doesn't exist. He's also listed various Operating Systems he's worked with in the past, one of which is listed simply as, "2003". "2003" is not an Operating System. Whoopsie Daisy!

Recruiters often "mess around" with resumes before sending them off to employers, so there may be a valid explanation. But it still looks suspicious.

Here's a sample list of questions we commonly ask that most Microsoft .Net developers should find relatively straightforward:

1) Describe some of the differences between a DataReader and a DataSet.

2) Describe some of the differences between C# and VB.Net

3) Why would you want to use a StringBuilder object?

4) What is Reflection?

5) What namespace must be referenced to execute queries against SQL Server 7.0 or greater?

6) Why do ASP.Net web pages load slowly the first time they are accessed?

7) If you reference COM objects from within a DotNet page, what page directive must be present?

8) Is it possible to use a .Net object from within a classic ASP page?

9) What is a WebService, and what benefits does this technology offer?

10) How are WebServices different from .NET remoting?