The interview process started out with a phone call screen. Nothing to bad at all. The next interview was a in-person interview. I do not know why they cannot just do a video interview since I am in mainland Europe. At the in-person interview (mind you my flight was cancelled and I barely made in time around their schedule) I was whisked away with their presentation. It was a brief but to the point presentation. They then go into a pair-programming exercise with their architect. Now this is where it went down hill. His exercise he choses to go with unit testing NUnit and password validation. Simple enough, so I start to write the tests to fail. The hardest part was the way he set up the class. I mentioned this was not a good design and that I've written tests before. I also showed him some concepts I've learned in my experience (e.g. catching exceptions in NUnit). His response was, wow I didn't even know you could do that! My assumption was the architect did not like me showing him new concepts. Of course some architects are open minded and will learn new concepts. This architect was not like that. I got the impression he saw me as a threat. When someone asks me what I see myself doing in 5 years, I always answer "I see myself as the architect of this development department". So year be mindful of these people that are easily threatened by more knowledgeable developers. My advice, if you want a job here but sure to be a "yes man" or "yes woman" and try not to make them look bad, meaning you should appear mediocre. And yes, they do not look at anything else, no past work, no past accomplishments, just a review based on that one sole person (architect) who may or may not like you running their pair programming exercise.