MeteorComm LLC Software Developer interview questions

At the beginning of the hour, the interviewer pointed out something from my resume's development philosophy paragraph and made it clear that things weren't done at Meteorcomm this way. This made the rest of the hour very uncomfortable. By the end, I had a very unfavorable impression of the company on both the managerial and technical fronts. I was asked if I knew about TDD. So I answered: "It's where you write a test case first, confirm it doesn't pass, then write code to make it pass." "Can you describe how you go about it?" "Well, usually I'll take a good guess on what smallest testable piece of functionality is that I can code, then I write the test case for it. Then write code until the test runs properly." "That sounds like bottom up development." "Um, well, maybe, depending on the design...." "Not like top down, which is the proper way to do it." "Um, ok." "So have you actually done TDD?" "Sure." "And that's how you do it?" "More or less." "What do you do when you write the test first?" "Well, you end up thinking about what you're really supposed to do, what you're supposed to accomplish, and how the code should be designed to do it. It's real helpful." "Is that all?" "Well, it also gets you in the habit of writing unit tests. That's good all around." "Hm. [uncomfortable pause] No. What you do first in TDD is that you make sure the test *fails*." "Well yes, of course." (Did I not say that to begin with?) Similar exchanges to the above happened 2-3 more times during that hour: they'd ask a question, I'd give a perfectly fine answer, they'd press for a different answer, then tell me that I was dead wrong. They visibly expressed disapproval at several points. Heads shook while I described how to handle difficult people by "doing my best to listen" and "working to understand their perspective." During a small coding exercise, a disparaging comment was made as I caught and corrected one of my own errors. The experience I've recounted was with two interviewers in managerial positions. I also met with non-management devs in two separate interviews. Those were more typical sessions and the regular team members seem like decent people.