4 ms·
When I interview, I use this question is a reverse fashion. I asks how would you implement a b-tree index (for example). The right answer is -- "I wouldn't.
by joshuaellinger 13y ago
When I interview, I use this question is a reverse fashion.
I asks how would you implement a b-tree index (for example). The right answer is -- "I wouldn't. DB vendors put years into getting this right.".
If you want this sort of gimmick to stop, when you are in an interview, you should just have the balls to ask how it is relevant to your potential job. Their response will give you a good idea if you really want to work there.
As an interviewer, you litmus-tests on questions like this is that they should be (a) answerable by all your existing employees and (b) reveal the thought process of the applicant. If they don't do that, find some better questions.
- drewcoo 13y agoThat may work for you and I don't mean this as personal criticism, but hostile interview techniques like that are enough for me to not accept a position if it's offered. Likewise, if I were interviewing someone and the candidate asked hostile questions to see if I "had balls" that would be a no hire. Just my opinion, of course. YMMV.
- joshuaellinger 13y agoI think you misread my post slightly. I consider the trick questions from Google interviewers to be hostile. The only reason not to call them on it in the interview is that you want the job and think that you can get it by being nice rather than honest. "having balls" != "hostile". "having balls" == "telling the truth" The point I was trying to make in an interviewer is that you really want to find out what someone is going to do when you ask them to do something that they think is stupid. Because you will eventually. As an interviewee, you really want to find out what happens if you have to challenge the management. You can be both honest and nice. It is just harder than trying to answer the question directly.