The process took 3 days. I interviewed at Balihoo (Boise, ID) in Jan 2012
Interview
Met CTO briefly, formal 3ish hour interview following day. Actual interview was in-depth one-on-one with CTO, puzzles and problem solving.
Next, met dev team in conference room to be grilled on mundane development minutiae, like a silly pop quiz from CS-102 freshman year, despite my decade of relevant professional experience. If I failed to recall the precise term the ringleader expected as an answer he would subject me to underhanded and condescending insults such as recommending I find a copy of Design Patterns so I may better understand programming fundamentals. The guy clearly disliked me as soon as we met.
Finally a one-on-one with CEO, a wonderful change of pace from the gauntlet of snobby devs putting me down for an hour. CEO at the time was phenomenal and an absolute pleasure to speak with.
Needless to say I was not hired, which of course is good since the devs clearly did not want me on their team. This was 2011 or 2012.
Interview questions [1]
Question 1
Was asked to explain a specific, obscure design pattern
I applied in-person. The process took 3 days. I interviewed at Balihoo (Boise, ID)
Interview
Long and thorough interview process. One portion involved being questioned by potential peers, some of which were not especially gifted at hiding their dislike of me as a person/engineer. However, the CTO, CEO, and most of the engineers who interviewed me were very friendly. While I am a talented developer who went on to find work in the field at another organization, I felt like I was turned down based on a small clique of existing employees who kinda just didn't like me.
That said, the process itself was fine.
Interview questions [1]
Question 1
Random questions straight out of programming/CS text books to which I would never need to know the answer from memory on the job (Google would have it for me in 5 seconds). Experience and problem solving abilities should speak for themselves, not mundane computer science quizzes.
