Re:Why "I'd Google it" is not an acceptable Interview Answer
by wildwood on Thursday June 11, 2009 @02:58AM
(#652381)
I absolutely agree - if I'm trying to gauge whether an applicant really knows as much as they think they know, I would ask questions where the interviewee might think "google it" is acceptable, but that would make me trash the application.
For example, if someone rates themselves as 7 out of 10 on java, they better be able to come up with a handful of functions on Object that are useful to override, or walk through the rough call sequence to query a database using jdbc. And that should all be from memory.
Maybe that's unfair on my part, but I feel like it does a lot to filter for people who can actually walk the walk.
Re:Why "I'd Google it" is not an acceptable Interview Answer
by sjf on Thursday June 11, 2009 @05:26AM
(#652505)
Because everyone who writes in Java uses JDBC? Why not ask them about core features of the language?
In contrast, if I see a resume with a few years of experience writing Java code (working full-time on 90%+ Java systems), then I think it's reasonable to discuss the specifics of the language/platform. If you've supposedly been writing Java code for a few years and you can't tell me how exceptions work, then you're a moron or a liar.