3 ms·
I've found it helpful when interviewing and it's becoming obvious the interviewee "really needs to hit Google" that you just say, "Just write the function down
by jerf 16y ago
I've found it helpful when interviewing and it's becoming obvious the interviewee "really needs to hit Google" that you just say, "Just write the function down with some appropriate parameters and keep going". For instance, it's easy to have year and years of very detailed experience in a language, yet still not quite remember off the top of your head how to open a file and read some lines out of it, which turns out to be something that you do far less often than you might think, because it's often totally abstracted away. If you haven't got any clue what to do with a string, on the other hand, that's probably a problem.
You still get what you need as an interviewer; even if you don't know the parameters, you should still see basic error checking, you can learn a lot if they don't provide the correct parameters, etc. This approach also allows you to implement the "don't know the language" interview; I don't really know PHP but I've interviewed people in it, because I know it well enough to see the things I am looking for. In that case I don't even know the precise parameters to open to "nail you" on them in the first place! But that's not what I'm looking for.
- __mharrison__ 16y agoThe interesting thing is there are some people who on paper come across as strong, but throw a simple programming problem at them and they give you a blank stare. I'm usually not playing the compiler type during the interview. Pseudo code would probably work since I want to see problem solving. (But those who could write pseudo code could just as easily substitute in their language de jour).