Makes a person write a fully tested application to solve a difficult triangle puzzle and a technical phone interview before a face-to-face interview. During the face to face interview, the art of asking more numerous arcane, forgettable and theoretical questions continued. Various members of the team asked numerous technical questions; many of which are irrelevant to an optimally engineered software application; and if ever needed, could easily be answered on some closed out Stack Overflow thread or gleaned from some college level computer science textbook. I doubt that those people even knew the practical implications of the answers to the questions they ask beyond the scripted pedagogical responses which they have jotted in their respective notepads. One of the team interviewers was outright hostile and rude for no reason at all. He even proceeded to disrupt the process with bursts of derision that he masked as unexcused sneezes. He also showed during the interview that he: 1. Does not know the difference between the Dependency Injection mechanism and Inversion of Control architecture - making numerous statements that confused Inversion of Control for Dependency Injection. 2. Does not know when to and when not to use Inversion of Control architecture. Thinks that the main advantage of Dependency Injection is for creating an easily testable application - because, according to him, objects have already been magically created by the application and awaiting injection. He had no clue that any class that adheres to the most basic principles of the object oriented design is easily testable simply by the virtue of such basic adherence. 3. Does not understand the idea of immutable classes 4. Does not understand when to use lazy loading vs eager loading, 5. Does not know how to instantiate a singleton JIT in a thread safe manner 6. Does not know why eager loading should be used to instantiate must-use classes such as configurations and application level services. The hiring manager was disengaged and mentally absent - which I supposed is attributable to either the stresses of managerial responsibilities or his unwillingness to diversify his corp of engineers. He slumped over his chair with his eyes half awake and his arms folded across his chest. He did not even look at my resume which he duly placed in front of him. He told my recruiter that I was not a technical fit. Another personnel was marching around the office in what appears to be his underwear. The blatant lack of professionalism I encountered in that place was simply spellbinding. At the end, it is very difficult not to think that they use employment-seeking experienced software developers to solve their bottle-neck technical problems, and then shut them out with a trumped up "lack of technical fit" nonsense.