The interview seemed easy enough. They provided me with a hard copy of some legacy Java code with very little standards within the code. I was asked to identify it, and right away, even before the hard copy left the interviewers hand, I had an idea of what it was doing by merely glancing at it. The idea was for the interviewer to let me look at code for 10 minutes to see what it was doing. Now, this was code with identifiers such as int a int b (every identifier was one letter long). I was able to identify the code as an implementation of a hash table with separate chaining, ie a chain list with worst running time O(n) on retrieval and insert. The interviewer came back later and basically said, "You are the first candidate who has ever instantly identified code in this manner". Although he said this, apparently I had failed this "code review" " test" (more on this later). The second part after talking to the person administering the "code review" test was talking to the senior developer at Evite. He asked what my favorite language was. Being an IT worker of some experience, I knew that being tied to any particular language framework or tool is hubris. So I replied that I didn't have one and used whatever tool was necessary to complete the task, whether it is Java on Spring, Python on Django or even some custom big data tool if it is necessary. He took this as a sign of belligerence and said: "So you refuse to answer my question." This is when I knew ageism was a factor. A younger programmer who picks up a new tool and runs with it is definitely a threat to an older, more institutionalized programmer. After this interview with the senior programmer, they sent me back home and emailed me a "test". It was easy enough except for a problem with the requirement. They wanted some scheduling algorithm and some restful service to be implemented, except the scheduling rules defined by their "test" had a conflict. The code review interviewer I had spoken to earlier did not really resolve the problems with the requirements and told me to just submit the code when I'm done so he can get back to me later. I submit the code and wait for a week. I follow up the following week and he does not answer for another week. After two weeks he states that I failed both the code review AND the coding "test" even though he had stated in the on site that he never saw anyone who had ever gone through a code review that quickly and accurately. His response to my questioning about why he never got my follow up email was that it went to his spam box even though he received my first email. I knew at this point Evite was a Mickey Mouse shop. Moral of the story: don't entertain an Evite "interview".