eah hya 2s2lt el interviews eli 3gbtk awi + its answer :D

For me to interview a developer is to ask him\her to write Code.
The problem you ask him\her to solve should be within these guidelines

1. Not an "Aha" kind of problem, that you don't know it unless somebody tells you the trick, because if the candidate just solved it you can't tell if he was good that's why s\he figured it out, or he knew that trick already so s\he solved it.
2. Avoid technology specific coding, for example how to access database using ADO.net? it is not challenging and it doesn't test the candidate's ability to think, just the ability to memorize API's
3. Make sure you have a little bit of room for the candidate to show off him\her design skills
4. Algorithms and Data structures are usually the way to go for most cases, but you shouldn't be asking a very direct algorithm question like "Write mergesort" now you are not testing thinking you are testing memorizing, you need to provide a general problem that the candidate by analyzing the problem figures out that merge sort (or any other algorithm for that matter) can solve this problem. This means that the candidate understands the underlying value of algorithms
5. Interview questions should be scalable, so you ask an easier constrained version of the problem, then you expand on the idea a little bit more and so on, then you ask for optimizations in cases when for example data set is significantly bigger and so on.
6. Open ended questions are good if you want to test design abilities and how the candidate behaves when taking decisions with other people, is s\he good in negotiation? can he present his case? is he willing to accept other opinions if it is still correct? will he agree on something that it is obviously wrong just because it came from an authoritative source without even raising concerns?