4 ms·
I don't think I would have been so patient as an interviewer. He tried very hard to evade the questions several times. I would expect "fun" meetings in the futu
by Tichy 18y ago
I don't think I would have been so patient as an interviewer. He tried very hard to evade the questions several times. I would expect "fun" meetings in the future, dragging on for hours.
- derefr 18y agoHe didn't evade the question; he asked the question that actually needed to be asked. If I ask you how to code a performant 3D shooter in PHP, you don't explain it, you stop me, possibly bitchslap me, and tell me that that's not what I should be doing, or, more kindly, ask "why do you think you should be coding it in PHP?" I think I might inject this kind of thing into an interview just to weed out the people unwilling to stand up to insanity. If you can't tell me when I'm going too far down the wrong path, how can I be sure you'll know if you're doing the same thing?
- ErrantX 18y agoThat's not a relative example though: looking at the original question the interviewer wanted to see how he would approach the problem of analysing and sorting the words. At the end of the day he petulantly (his words) stuck to a point that could have been made in a simple sentence (well, assuming we agree there is no way this could work in the real world because of the fluidity of language and the poor behaviour of web crwlers then I would.....). If the interviewer is looking for a discussion on that he will pick up and ask for more. If not he will let it pass (and probably note that your recognised the issue). In an interview you must dangle relevant information in front of the interviewer and wait for him to pounce on things he wants more information on :) Also: NEVER assume a concept the interviewer has "never heard" of IS something he/she has never heard of. That is a simple mistake to fall into.
- derefr 18y ago> Also: NEVER assume a concept the interviewer has "never heard" of IS something he/she has never heard of. That is a simple mistake to fall into. Of course, they just want you to explain the concept as if they've never heard of it. However, he was writing this after-the-fact, so I'm assuming it still seemed that he hadn't heard of the concept in retrospect, which is a much different beast.
- Tichy 18y agoI see your point, but I don't think the questions were particularly insane.
- ilitirit 18y agoI agree, but it was partly the interviewer's fault. He should have just said "assume static pages" and/or "assume everyone speaks the same dialect of english and uses the same vocabulary". In cases like these interviewer should always try to eliminate fluffy answers as far as possible. How else would an interviewee know what his intent is? Perhaps the interviewer wants him to critically assess the question? On the other hand, I always make a habit of asking things like "is it safe to assume such and such?". Then I don't have to go into detail unless they ask "Why?". That said, it was quite obvious that guy was trying to avoid the question. That wouldn't have sat well with me.
- Tichy 18y agoI would have expected the candidate to bring up something like "OK, let's assume the work of Shakespeare or another fixed body of text" if he was worried about that issue. Instead he said "that question does not make sense", which would have annoyed me.