Being a Candidate...
What I saw in the last few months is that we can foreseen the next interview questions (the wheel already invented, so does the question we need to face with in an interview/examination) :
What the different between “has a” relationship then “is a” state of a class and how u can achieve it using C#?
What are delegates, interfaces and attributes? Why we need it?
Raise few options to improve performance to your web application?
Please write a short sample that uses a DataGrid which display the employee details..
Write a store procedure that get a leaf ID and return the leaf direct path...
In general, easy question.
I don't understand how and why candidate come to interview without a basic preparations to questions that are more likely to be raise there. A candidate been invited to an interview after his resume convinced that its worth to check what the candidate knowledge is. Still, many time the candidate was disappointed and I find a real gap between what I saw in the resume and what I got in the candidate short examination.
Especially developers who wrote amazing code a year ago but not in the last 3 month - should do their homework before any examination. We tend to forget things if we don't actually use it.
Few tips -
Write DataGrid, Repeaters, Drop Down List (etc) events handlers..
Check out few samples code and write by yourself few store procedure if u think this going to be part of the examination (pl/sq or tsql)
ADO.NET - learn how to use its objects directly. Don't start to use the VS.NET designer wizards during the exam...
Write a complete user interaction flow: user send input data, accordingly data been retrieve from DB and eventually the data being display in a web form (or window form)
And a golden rule: write inline documentation and use naming conventions. Write clear and modular code.
Candidates (me too, sometimes) - do your homework before interviews - or at least contact me so I will assist u to pass your next interview...