|
|
Posted by larry on 05/06/07 21:39
On Apr 16, 7:29 am, tasteless <tastel...@gazeta.pl> wrote:
> this questions needs to be very hard, but the experienced senior PHP
> developer should answered on it.
>
I think you should concentrate on seeing if you Senior Developer knows
enough to be a senior developer.
If he is writing code see some examples of his code (to see how he
writes) from projects he's done in the past.
See how he codes (thinks) an example I read on Slashdot (my
interpretation) was to have the interviewee write code to display a
list of numbers 1 to 300, anytime the number is divisible by five
display the number with "bin" after the number. If the number is
divisible by three display "fiss" after the number. If it is both
three and five display the number with "fissbin"
It may be simple to code but it can be done in 10 minutes, and you
will get some idea of how they problem solve use loops decision trees,
etc.
Discuss something related to the type of applications you are
developing to see if they grasp the concept of developing software in
the field that you are in (i.e. developing stuff that involves
tracking family data can be very complex with incomes and family
member relationships)
Lastly get his programming philosophy, besides seeing the problem and
knowing the language does he grasp out to the users, as in if you want
to support Linux, is he/she aware of the problems developing for non-
IE browsers. Are you wanting to implement some sort of technology (DB
replication, encryption, GIS, Access integration, whatever) see if
they are familiar/comfortable with it and if not why (they may have a
valid reason or alternative).
Navigation:
[Reply to this message]
|