xsevensinzx (5/22/2015)
rsgardner2 (5/21/2015)
I really wish employers would get smart and try this instead of gathering lists of 'technical questions' from the internet.
Paraphrasing Google here: It's not about finding a master who can do something amazing, it's about finding good problem solvers because eventually, they will figure it out.
I really agree with that statement to some extent. While it's cool that someone can answer a lot of standard technical questions, it's really important to know if the candidate is willing to tackle as well solve complex problems.
Again, I have to disagree, for the most part. While finding a "master" is not my goal, it would be nice to find someone (anyone at this point) that isn't going to glaze over and start drooling on themselves when presented with a 3 table join or even how to get the current date and time.
As for "standard technical questions", they are a must. The difference is that you don't just sit there and listen to the applicant... you must interact with the applicant during the applicant's explanation and after. When I interview someone, every "standard" question is nothing more than a segue into a possible hierarchy of related questions and discussions on a give subject, the purpose being to find out if it's simple rote memorization on their part or if they've really done something, not to mention their ability to communicate and their general disposition.
--Jeff Moden
Change is inevitable... Change for the better is not.