First, the state of the art of "taking technical interviews" hasn't changed in the last 10yrs at least. This is, when we as an industry are harbingers of "chang

First, the state of the art of "taking technical interviews" hasn't changed in the last 10yrs at least. This is, when we as an industry are harbingers of "change". The bottom line is that the interview process is time consuming, expensive and often not the aspect of your job for which you will be held accountable for (i.e. you get fired if you are unable to recruit). An interviewer in such a case, has no incentive to carefully think about the process. Usually the interview time during his/her day is not the prime task at hand and he/she has to run to "other meetings". In such an environment and time constraints, We come down to our rote notions of what "intelligence" means. If you are interested, I would recommend these two very well written articles: 1)http://code.dblock.org/five-ways-to-torture-candidates-in-a-technical-interview http://code.dblock.org/five-ways-to-torture-candidates-in-a-... 2)http://code.dblock.org/how-to-reject-engineering-candidates http://code.dblock.org/how-to-reject-engineering-candidates Lastly, I wish you luck if you are a so called Front End engineer or worse, a female engineer in this industry. Its really rough out there for them in special. Now, if you'll excuse me, I have to go and practice my bit manipulations.