Commentüs on: interview questions http://blog.lucene.com/2004/07/13/interview-questions/ Ramblings about Lucene, Nutch, Hadoop & other stuff Fri, 05 Dec 2008 08:02:59 +0000 http://wordpress.org/?v=MU hourly 1 By: Better Tom http://blog.lucene.com/2004/07/13/interview-questions/#comment-15252 Better Tom Fri, 11 Apr 2008 06:19:31 +0000 http://cutting.wordpress.com/2004/07/13/interview-questions/#comment-15252 well it's not the kind of news that is worth discussing. i wonder why are you all here so excited? well it’s not the kind of news that is worth discussing. i wonder why are you all here so excited?

]]> By: Me http://blog.lucene.com/2004/07/13/interview-questions/#comment-846 Me Thu, 01 Mar 2007 01:02:49 +0000 http://cutting.wordpress.com/2004/07/13/interview-questions/#comment-846 I run across a Technical Interview questions and answers website, which may be useful http://www.technical-interview.com I run across a Technical Interview questions and answers website, which may be useful http://www.technical-interview.com

]]> By: George Withers http://blog.lucene.com/2004/07/13/interview-questions/#comment-294 George Withers Sun, 19 Sep 2004 11:43:00 +0000 http://cutting.wordpress.com/2004/07/13/interview-questions/#comment-294 What I've been doing (and it does seem hard to know what is really "working") is to give a simple, standalone application description and give the candidate some time (30 minutes) to draw up an approach and then present it. This is certainly a test but gives the interviewee time to review the problem/question and present the answer interactively. In the presentation it's both easier for the interviewee in that the answer isn't simply 42, and for the interviewer in you have something to pick into to see how the person is thinking. What I’ve been doing (and it does seem hard to know what is really “working”) is to give a simple, standalone application description and give the candidate some time (30 minutes) to draw up an approach and then present it. This is certainly a test but gives the interviewee time to review the problem/question and present the answer interactively. In the presentation it’s both easier for the interviewee in that the answer isn’t simply 42, and for the interviewer in you have something to pick into to see how the person is thinking.

]]> By: Anonymous http://blog.lucene.com/2004/07/13/interview-questions/#comment-293 Anonymous Sat, 07 Aug 2004 00:28:00 +0000 http://cutting.wordpress.com/2004/07/13/interview-questions/#comment-293 What I'm worried about is that Google is only hiring smart people and not any creative people. Certainly you need smart people but without creative types Google may just be top heavy with smart people who won't be able to come up with the next great search engine. Right now, I don't see Google's search getting any better, in fact, it seems like it's getting worse. What I’m worried about is that Google is only hiring smart people and not any creative people. Certainly you need smart people but without creative types Google may just be top heavy with smart people who won’t be able to come up with the next great search engine. Right now, I don’t see Google’s search getting any better, in fact, it seems like it’s getting worse.

]]> By: Anonymous http://blog.lucene.com/2004/07/13/interview-questions/#comment-292 Anonymous Wed, 14 Jul 2004 08:10:00 +0000 http://cutting.wordpress.com/2004/07/13/interview-questions/#comment-292 I'm not looking forward to being stumped on my next interview but it does seem like "quizzing" is en vogue. Joel (http://www.joelonsoftware.com/articles/fog0000000073.html) seems infatuated with pushing interview candidates mental prowess to really get into how they think. In many ways I think this is good; but I see lots of potential holes in his approach. For one, it focuses on a lot of academic mental agility whereas a lot of the good programmers I've known aren't quick witted, sharp tongued or argumentative, they plod through issues and come up with good ideas. I’m not looking forward to being stumped on my next interview but it does seem like “quizzing” is en vogue.

Joel (http://www.joelonsoftware.com/articles/fog0000000073.html) seems infatuated with pushing interview candidates mental prowess to really get into how they think. In many ways I think this is good; but I see lots of potential holes in his approach. For one, it focuses on a lot of academic mental agility whereas a lot of the good programmers I’ve known aren’t quick witted, sharp tongued or argumentative, they plod through issues and come up with good ideas.

]]>