Chicago Trading Company Senior Software Engineer interview questions

I recently had a six hour long interview at this place. The position was in infrastructure group. I would say what a waste of my six hours. I interviewed with people that themselves had no idea what they were talking about. They had incorrect concepts of how things work and are really poor judges of technical abilities. Started out with a 45 minute presentation in front of 7 or so people. There I found a rather obnoxious large man who kept telling me the piece of app that I presented can be done in a different way because that's the way he did it in his previous job. Afterwards, I had misfortune of going through with another 45 minutes with this rather large man and another guy. One of the question, they asked was what happens before a monitor is acquired in java. The answer they were looking for is "cache is flushed before monitor is acquired", which is completely incorrect. I gave them entire story of how the locking is done, including what the source of java object monitor looks like, how the monitor ownership is obtained using CASing, what kind of op codes you see (including the actual opcode names) when locking is done etc etc. The rather large man didn't know any of this, but he and the other guy kept arguing with me to get "cache flush" out of me, which is absolutely wrong. The other two hours I spent whiteboarding. Their actual expectations were not that I write syntactically correct code, or a working code, but write code like it's in an IDE (I learned this from the feedback I got). They thought I did sloppy variable declaration, whatever the hell that means. Whiteboarding is generally used to see the thought process and problem solving process, not to see how nicely the variables are declared. It's a whiteboard for god's sake. When I came back home, I was really underwhelmed by the people I encountered and their depth of knowledge.