[ryanbrunner]

I've seen the TDD one, and I hate that so much. The last time I interviewed for companies, I started asking "how do you want me to answer this? Are you looking for me to get a complete solution quickly, or write this like I was writing software I planned to maintain?", but I really shouldn't have to - putting your candidates through a guessing game of which you want is a dumb way to interview.

[flyfishnjake]

I had a recruiter suggest I do TDD during my coding interviews. When I was in the interviews, I started using TDD. It seemed like the actual interviewer was indifferent about me using TDD. He even seemed surprised, but I did it anyway because the recruiter suggested it.

Using TDD takes longer during an interview, so I didn't get as far into the problem as what I think the interviewer was expecting. I assume people that didn't use TDD performed better because they were able to get farther in the problem.

I didn't get an offer. I'm not sure if it's because of the TDD issue, but I can't think of anything else that could have contributed to the outcome. I sent my feedback to the recruiter after I was notified I didn't get an offer, and I asked for any feedback, but never heard anything.