i have had my share of interviewing would-be programmers for my team and i did have a layout of qualifications/questions that i/team needs hoping i would find them in the candidates..
of course, hr’s questions would be different from mine unless they themselves are technical people, so i’m not going to demean their way of processing people. my only concern is that some times i also look @ how these candidates communicate what they know (this is oftentimes the problem i see with tech people – unable to clearly tell others the technical details of what they know)
check this it and tell me what you think? thought most of it were true.
image c/o [hanovsolutions.com]
set it good 
I'm a computer science student, and this is very useful for me. I've shared this to my friends. Thank you. I hope someday I will qualify as a good programmer. =)
LikeLike
thanks macobex.. having a good resume however doesn't equate a good programmer.. there are some who have good credentials but still fails due to other reasons like – salary, communication, not fit with the team etc… just the same, feel free to spread IT PINOY! good luck!!
LikeLike
I’m a computer science student, and this is very useful for me. I’ve shared this to my friends. Thank you. I hope someday I will qualify as a good programmer. =)
LikeLike
thanks macobex.. having a good resume however doesn’t equate a good programmer.. there are some who have good credentials but still fails due to other reasons like – salary, communication, not fit with the team etc… just the same, feel free to spread IT PINOY! good luck!!
LikeLike