From: Bjørn Remseth (email@example.com)
Date: Mon Jun 12 2000 - 04:10:00 PDT
On Thu, Jun 08, 2000 at 05:14:34AM -0500, Adam L. Beberg wrote:
> some hiring rules for writing non-crap software:
> [or, why I'll never win]
I have a standard set of questions I usually ask:
If candidate says he/she knows something about databases
then ask candidate "Can you explain 1NF for me?".
If candidate answers correctly, ask candidate which NF is usually
his/her target when making a first attempt at a DB design.
If candidate says he/she knows something about program design
then ask candidate "What is a quadratic algorithm?"
(the question is intentionally ambigous, and one might tell
the candidate this, it makes no difference for the ones who
knows the answers ;)
If candidate says he/she knows something about networks
then ask candidate "Can you explain 'Slow start' in TCP for me?"
Even if these questions appear to have a textbook answer, and they do, they
really are open ended questions.
I make no secret about the fact that I regularly ask these questions, still
I have yet to interview a -single-person- who couldn't give a reasonable
answer to all of them that I wouldn't hire on the spot ;-)
This archive was generated by hypermail 2b29 : Mon Jun 12 2000 - 04:15:26 PDT