Re: New Thread - Pre Screening Questions for a C# developer

One other point I haven't seen in this thread yet: Multiple-choice questions
are convenient for scoring, but horrible for evaluating. The answer is
always in the list of possible answers; therefore, an analysis of the list
of possible answers will often yield the correct answer, without having to
know it beforehand. I did this quite a few times in my lifetime. IMHO, when
testing, it is not wise to provide the answer to the subject of the test,
regardless of how one tries to hide it.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

"William Stacey [MVP]" <william.stacey@xxxxxxxxx> wrote in message
news:uN5lsuwTGHA.2656@xxxxxxxxxxxxxxxxxxxxxxx
| Also, it's useful to draw a denormalized table (e.g. customer orders
| which will contain all orders, customer info, prices, etc all in one
| table) and to ask them to denormalize that table.

Naturally, that is a trick question as the table is already
"denormalized".
I know that was just a typo. :)

| Another question is to ask them to design something like watch in terms
| of OOP - this way you might get a good idea of that person't OOP skills.

Good idea.

| So my advise - don't look too much into particular details as class
| names, function names, sql syntax but rather look at the person's
| analytical, algorythmical skills and ability to function under stress
| and pressure.

I agree. You could loose a lot of good talent as some of the best don't
think in terms of MSDN style answers, but in logic and debugging and
design.
The test style questions can be found in Help in a few moments and we
don't
need to pack our brains with that, we have Intellisense. The good stuff
is
the knowing the stuff you can't learn from MSDN/Help.

--
William




.