I suppose I did not clarify, but it was not one question. It was like a checklist of define this & define that. Not all OOP either. Define a namespace, tell me what a relationship is in a database. It just seemed very tedious, and not necessarily really getting to the meat of whether or not this guy can code on your team or not. I have just never felt that memorizing a definition has anything to do with being able to apply that knowledge. (Although, indeed, it is a manditory first step in the process.) In the most extreme example, it's like all of the data you have on a computer, but what can the computer itself do with it... nothing. Of course, that's VERY extreme, and no human being would truly be like a worthless gob of silicon & wiring with no ability to use the knowledge contained within. And, to further clarify, these interviews (or really 1 particular interview is standing out in my mind) was while I was already employed & simply looking to better my situation, so I could afford to consider such things.

Basically, you summarize my concerns well though. I could potentially work with a lot of people with a great capacity for memorization of facts, and quite likely scored very well on college because of that, but applied knowledge is just not their thing. I would say even primary to that thought is if that is the type of co-worker I would have, would I then be overlooked for promotion or raises based on some fundamental difference in opinion on HOW you should rate the quality of a programmer? Again, if I were unemployed & sitting in that interview, I definately could grin & bear it & play the game, but that was not my situation at the time.


><snip>
>I have left the interviews thinking I was HOPING I wouldn't hear back from the company. I felt their demonstration of how they discerned good programmers from bad ones was different than my own ideas & just didn't feel comfortable with that mindset.
><snip>
>
>I find it interesting that one question to try to see how much OOP knowledge would be a knock out question for you. Are you thinking you would be working with other developers that were not qualified because you didn't like the hiring process?