To refine that a bit, you may want to give them some code that has
been intentionally broken (simple things for the entry level
position, such as missing semicolons or curly braces etc) and watch
to see how they go about discovering the parse errors. To me, it
would be better to hire someone that can solve problems quickly, not
someone who can simply tell you what a piece of code is doing. Just a
thought though - good luck!
-Joe
On Jul 20, 2006, at 7:20 AM, Finner, Doug wrote:
My advice, give the candidates problems and see how they solve them.
Even if they don't finish, you get an idea of how they think.
tedd
I like this idea!
Do you expect them to be able to work with code written by others? If
so, hand them some of your existing code (good examples and not so
good)
and ask them to figure out what it does and recommend changes.
I really really like the 'give them a problem and have them solve it'
idea...
Doug
______________________________________________________________________
_
This e-mail message has been sent by Kollsman, Inc. and is for the use
of the intended recipients only. The message may contain privileged
or confidential information. If you are not the intended recipient
you are hereby notified that any use, distribution or copying of
this communication is strictly prohibited, and you are requested to
delete the e-mail and any attachments and notify the sender
immediately.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
